NFT On-Chain Royalties (EIP-2981) 4

Question 1

Why might a developer prefer a payment-splitter contract as the EIP-2981 receiver?

Accepted Answer

To automatically distribute royalties among multiple collaborators

Answer

Setting the receiver to a splitter contract lets a single royalty payment be divided among several beneficiaries.

Question 2

What is a key limitation of EIP-2981 regarding peer-to-peer transfers?

Accepted Answer

Direct wallet-to-wallet transfers can avoid royalties entirely

Answer

Because EIP-2981 is not enforced at transfer, users can move NFTs directly without triggering any royalty.

Question 3

Which approach attempts stronger royalty enforcement than EIP-2981 alone?

Accepted Answer

Transfer-restricting allowlists like operator filters

Answer

Operator filter registries and transfer restrictions try to block non-royalty-honoring marketplaces, going beyond EIP-2981's signaling.

Question 4

If royaltyInfo is called with a salePrice of 0, what royaltyAmount results with a percentage-based implementation?

Accepted Answer

0

Answer

A percentage of zero is zero, so a zero sale price yields a zero royalty amount.

Question 5

Why should royaltyInfo be a view function?

Accepted Answer

So marketplaces can query royalties without sending a transaction

Answer

As a view function it can be called off-chain or in calls without gas cost, letting marketplaces read royalties freely.

NFT Development Practice Test