3.1.0 & 3.1.1 #51
Merged
3.1.0 & 3.1.1 #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. `initOwner` used in event logs during initialization rather than `tx.origin` 2. ERC-7160 compliant contracts now have a setting where they can change the behavior of the returned metadata when unpinned
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3.1.0
initOwnerin events emitted. This avoids usingtx.originwhich can break with account abstraction. While it does open the door to imitation onchain, there are ways to prove this onchain with no negative ramifications really asinitOwnerstill has control of the contract after the fact.tokenURIcan point to the original minted metadata or "float" with each new piece of metadata added.3.1.1
BatchMetadataUpdatefrom ERC-4906 when toggling the unpinned behavior flag