Marketplace Royalty Standards (EIP-2981) Flashcards
7 cards from real NFT practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Marketplace Royalty Standards (EIP-2981) flashcards as text
What does the royaltyInfo function in EIP-2981 return?
Answer: The receiver address and the royalty amount
royaltyInfo(tokenId, salePrice) returns a tuple of the receiver address and the royaltyAmount to pay.
Which parameters does royaltyInfo accept?
Answer: _tokenId and _salePrice
royaltyInfo takes the token ID and the sale price, then computes the royalty owed.
EIP-2981 specifies royalty information but does NOT do what?
Answer: Enforce or transfer the royalty payment
EIP-2981 only signals the amount and receiver; actual payment enforcement is left to the marketplace.
How is EIP-2981 support advertised to other contracts?
Answer: Via ERC-165 supportsInterface
Contracts implement ERC-165 so marketplaces can detect the IERC2981 interface ID.
In what unit is royaltyAmount denominated?
Answer: The same unit of exchange as _salePrice
royaltyAmount is expressed in the same currency/unit as the salePrice passed in.
A marketplace calls royaltyInfo with a salePrice of 0. What is the expected royaltyAmount?
Answer: 0
Royalty is calculated as a fraction of salePrice, so a zero salePrice yields a zero royalty.
Why was EIP-2981 created?
Answer: To provide a standard, marketplace-agnostic way to signal royalties
It standardizes royalty signaling so any compliant marketplace can read the same data.