EIP-721 Metadata Update Extension

The five-minute read

One action, walked through

1. Open ERC 4906 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Many EIP-721 contracts emit an event when one of its tokens' metadata are changed.
3. Name the object that changes: NFT, MUST, NOT.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing ERC 4906 at the status the text itself states: Final.
• The object that has to change is NFT, MUST, NOT. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is covered by the signed bytes in EIP-721 Metadata Update Extension?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: NFT, MUST, NOT?

Terms

ERC 4906

The public text titled EIP-721 Metadata Update Extension.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• Many EIP-721 contracts emit an event when one of its tokens' metadata are changed.
• While tracking changes based on these different events is possible, it is an extra effort for third-party platforms, such as an NFT marketplace, to build individualized solutions for each NFT collection.
• Having a standard MetadataUpdate event will make it easy for third-party platforms to timely update the metadata of many NFTs.

How the mechanism is specified

• Taken from the specification, the next constraint is: While tracking changes based on these different events is possible, it is an extra effort for third-party platforms, such as an NFT marketplace, to build individualized solutions for each NFT collection.
• Locate NFT, MUST, NOT in ERC 4906 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use ERC 4906 when a pitch says 'EIP-721 Metadata Update Extension' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.