ERC-6786 NFT royalty payment registry (Registry for royalties payment for NFTs)

Draft · NFTs & multi-token · created 2023-03-27

A standard that lets anyone send royalties to a creator for any NFT, and lets anyone publicly look up the total amount of royalties paid so far.

Why it is needed

Paying royalties to creators when an NFT sells or resells is an important incentive to keep creators active. However, many trading marketplaces do not enforce royalty payments or do not provide any way to pay them at all. Some marketplaces use their own royalty system, but it only applies to NFTs minted on that platform. In addition, when trades happen on marketplaces that do not support royalties, or over the counter, there is no way for an outside observer to know whether the royalty the creator was owed was actually paid. This standard tries to close this gap by creating a public venue through which anyone can pay royalties on a creator's behalf, and by recording and exposing the cumulative amount paid per NFT.

What to implement

In depth

Interface compliance requirements

Contracts following this standard must implement the IERC6786 interface. The ERC-165 identifier for this interface is 0x253b27b0, and the supportsInterface function must return true when called with 0x253b27b0. Functions defined as view may be implemented as pure or view, and payRoyalties may be implemented as public or external.

Behavior of payRoyalties

payRoyalties(address tokenAddress, uint256 tokenId) is a payable function that, when called, sends the accompanying msg.value to that NFT's creator. If there is no on-chain information about the creator, execution is reverted. The RoyaltiesPaid event must be emitted whenever payRoyalties is called, indexed by tokenAddress and tokenId, and recording the paid amount.

Querying the cumulative amount with getPaidRoyalties

getPaidRoyalties(address tokenAddress, uint256 tokenId) returns, as a uint256, the cumulative amount of royalties paid through this registry for a given NFT. The amount accumulates with every payment and is public, so it can be used to classify NFTs from a royalty standpoint or to gauge whether unpaid royalties remain.

Method for looking up the creator's address

ERC-2981 (the NFT royalty standard) is used to retrieve the creator's on-chain information. However, other on-chain methods of obtaining the creator's address are also allowed. This standard lists ERC-165 and ERC-2981 as requirements.

Native coin payment and transparency

Payments are made in the native coin, which makes it easy to sum the total royalties paid. The intent of making this information public is to let anyone verify whether a creator received royalties even when trades occurred over the counter or on marketplaces that do not support royalties. The payment function can be called by anyone at any time, not just the NFT owner, so it can also serve as a way to sponsor creators.

The meaning of the term 'debt'

The word 'debt' in the standard's name reflects the goal of making it possible to tell whether royalties remain unpaid for trades that occurred on marketplaces without royalty support, and of opening a path to pay them if so. The spec states that there are no backwards compatibility issues with existing systems.

Proposal status

This ERC is in Draft status, created on March 27, 2023. Since the content may still change, its current status should be checked before implementation.

Original ERC · ← ERCs