NFT On-Chain Royalties (EIP-2981) 5

Question 1

Before EIP-2981, why were royalties inconsistent across marketplaces?

Accepted Answer

Each marketplace used its own proprietary, off-chain royalty configuration

Answer

Without a standard, every marketplace stored and applied royalties differently, so they didn't carry across platforms.

Question 2

What is the primary benefit of storing royalty info on-chain via EIP-2981?

Accepted Answer

Any marketplace can read the same royalty data interoperably

Answer

On-chain, standardized royalty data lets all platforms query the same source, improving interoperability.

Question 3

Which gas consideration favors a default royalty over per-token royalties?

Accepted Answer

A default avoids writing storage for every token

Answer

Using a single default avoids the storage write cost of recording a royalty for each individual token.

Question 4

Can the royalty receiver address differ from the contract owner or NFT creator?

Accepted Answer

Yes, the receiver is set independently and can be any address

Answer

The royalty receiver is configured separately and can point to any address, such as a treasury or splitter.

Question 5

What does it imply if a contract's supportsInterface returns false for 0x2a55205a?

Accepted Answer

The contract does not advertise EIP-2981 royalty support

Answer

A false return for the EIP-2981 interface ID means the contract does not declare royalty support under the standard.

NFT Development Practice Test