Marketplace Integration 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 Integration flashcards as text
When integrating with OpenSea's Seaport protocol, what is the primary purpose of the 'conduit' contract?
Answer: To approve and transfer tokens on behalf of users via a shared allowance
The Seaport conduit acts as a shared transfer proxy, letting users set one approval that the marketplace uses to move their tokens during fulfillment.
Which standard interface should a contract implement so marketplaces can correctly distribute creator royalties?
Answer: ERC-2981
ERC-2981 defines the royaltyInfo function that marketplaces query to determine the royalty recipient and amount.
A developer lists an NFT for sale but the marketplace cannot transfer it on completion. What is the most likely cause?
Answer: The marketplace operator was never granted approval via setApprovalForAll or approve
Without an approval granted to the marketplace contract, it lacks permission to transfer the token to the buyer.
What does a 'lazy minting' integration allow a marketplace to do?
Answer: Defer the on-chain mint until the first sale, with the buyer paying gas
Lazy minting stores a signed voucher off-chain and only executes the actual mint transaction when the item is purchased.
When fetching a collection's listings via the OpenSea API, which value is essential to filter results to a specific blockchain?
Answer: The chain identifier (e.g., ethereum, matic)
OpenSea's API is multichain, so the chain parameter is required to scope listing queries to the correct network.
In a marketplace order, what role does the 'salt' value typically play?
Answer: It ensures order hash uniqueness to prevent collisions and replay of identical orders
A random salt makes otherwise-identical orders produce distinct hashes, preventing accidental collisions and signature reuse.
Why might a marketplace integration prefer EIP-712 typed-data signatures over raw message signing for listings?
Answer: It presents human-readable structured data in the wallet, improving security and UX
EIP-712 lets wallets display the order's structured fields, so users see exactly what they are signing instead of an opaque hash.