Royalty Bearing NFTs

The five-minute read

One action, walked through

1. Open ERC 4910 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: The proposal directly connects NFTs and royalties in a smart contract architecture extending the ERC-721 standard, with the aim of precluding central authorities from manipulating or circumventing payments to those who are legally entitled to them.
3. Name the object that changes: CRUD, NFT.
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 4910 at the status the text itself states: Final.
• The object that has to change is CRUD, NFT. A neighbouring document with a similar name is not this one.
• The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.

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

• Which function in Royalty Bearing NFTs actually moves or approves value?
• What happens on a callback, a zero amount, or a contract recipient that rejects?
• Which names does the text commit to: CRUD, NFT?

Terms

ERC 4910

The public text titled Royalty Bearing NFTs.

Final

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

The problem the paper names

A token that each contract invents from scratch does not transfer, approve, or display in any other contract. The cost of a shared interface is that the interface's holes become everyone's holes.

What the design proposes

• The proposal directly connects NFTs and royalties in a smart contract architecture extending the ERC-721 standard, with the aim of precluding central authorities from manipulating or circumventing payments to those who are legally entitled to them.
• The proposal builds upon the OpenZeppelin Smart Contract Toolbox architecture, and extends it to include royalty account management (CRUD), royalty balance and payments management, simple trading capabilities -- Listing/De-Listing/Buying -- and capabilities to trace trading on exchanges.
• The royalty management capabilities allow for hierarchical royalty structures, referred to herein as royalty trees, to be established by logically connecting a "parent" NFT to its "children", and recursively enabling NFT "children" to have more children.

How the mechanism is specified

• Taken from the specification, the next constraint is: The proposal builds upon the OpenZeppelin Smart Contract Toolbox architecture, and extends it to include royalty account management (CRUD), royalty balance and payments management, simple trading capabilities -- Listing/De-Listing/Buying -- and capabilities to trace trading on exchanges.
• Locate CRUD, NFT in ERC 4910 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

• An application standard is not consensus. A contract can ignore it and still be a valid account.
• The standard does not enforce royalties, identity, or a price. If the transfer function does not check it, the chain will not.
• 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 4910 when a pitch says 'Royalty Bearing NFTs' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.