Marketplace Royalty Standards (EIP-2981) Flashcards

Why are on-chain EIP-2981 royalties NOT guaranteed to be paid?

Answer: Enforcement depends on the marketplace honoring royaltyInfo

EIP-2981 only reports royalties; a marketplace can ignore the data and skip payment.

What approach did some projects adopt to ENFORCE royalties beyond EIP-2981?

Answer: Transfer-blocking allowlists/operator filters that restrict non-compliant marketplaces

Operator filter registries blocklist marketplaces that bypass royalties by restricting approved transfer operators.

A peer-to-peer wallet transfer (no marketplace) of an EIP-2981 NFT pays what royalty?

Answer: None, because no sale price or marketplace is involved

Direct transfers have no salePrice and don't call royaltyInfo, so no royalty is collected.

What is a key limitation of EIP-2981's single-receiver design?

Answer: It returns only one receiver, so multi-party splits need an external splitter

royaltyInfo returns a single receiver, so distributing to multiple creators requires a separate splitter contract.

How should a well-designed marketplace handle a token that does NOT implement EIP-2981?

Answer: Detect via supportsInterface and skip royalty logic gracefully

The marketplace should check ERC-165 support and proceed without royalties when unsupported.

Marketplace royalty enforcement debates in 2022-2023 centered mainly on what tension?

Answer: Creator revenue versus zero-fee/optional-royalty marketplaces

Zero-fee marketplaces made royalties optional, pitting trader savings against creator earnings.

EIP-2981 can be implemented on which token standards?

Answer: Both ERC-721 and ERC-1155

EIP-2981 is token-standard agnostic and works with both ERC-721 and ERC-1155 NFTs.