NFT Marketplace Royalty Standards (EIP-2981) 2

Question 1

What does the royaltyInfo function in EIP-2981 return?

Accepted Answer

The receiver address and the royalty amount

Answer

Only the royalty percentage

Answer

The token owner and creator

Answer

A boolean indicating royalty support

Question 2

Which parameters does royaltyInfo accept?

Accepted Answer

_tokenId and _salePrice

Answer

_owner and _amount

Answer

_buyer and _seller

Answer

_contract and _value

Question 3

EIP-2981 specifies royalty information but does NOT do what?

Accepted Answer

Enforce or transfer the royalty payment

Answer

Return a receiver address

Answer

Calculate a royalty amount

Answer

Use ERC-165 detection

Question 4

How is EIP-2981 support advertised to other contracts?

Accepted Answer

Via ERC-165 supportsInterface

Answer

Via an emitted RoyaltySet event

Answer

Via a public bytes32 constant

Answer

Via the contract name

Question 5

In what unit is royaltyAmount denominated?

Accepted Answer

The same unit of exchange as _salePrice

Answer

Always in wei of ETH

Answer

Always a basis-point percentage

Answer

Always in USD stablecoin

Question 6

A marketplace calls royaltyInfo with a salePrice of 0. What is the expected royaltyAmount?

Accepted Answer

0

Answer

A default minimum fee

Answer

The full creator royalty

Answer

Reverts the transaction

Question 7

Why was EIP-2981 created?

Accepted Answer

To provide a standard, marketplace-agnostic way to signal royalties

Answer

To force every marketplace to charge fees

Answer

To replace ERC-721 entirely

Answer

To store royalties on a centralized server