NFTs, Tokenization, and Digital Assets Flashcards

A DeFi protocol implements a 'fractional NFT' (F-NFT) mechanism by locking an ERC-721 token in a vault and minting 10,000 ERC-20 tokens representing pro-rata ownership. Under the Howey Test, what is the PRIMARY regulatory risk this structure introduces compared to the original NFT?

Answer: The ERC-20 fractions are far more likely to be classified as securities because passive investors pool capital expecting profits from others' managerial efforts

Fractionalized NFTs convert a unique digital collectible into fungible ERC-20 tokens sold to passive investors who expect appreciation driven by the platform's or vault curator's efforts — squarely matching the Howey Test's four prongs (investment of money, common enterprise, expectation of profits, from others' efforts). The SEC has specifically warned that F-NFTs exhibit stronger securities characteristics than the underlying NFT. The other answers either misstate legal doctrine or describe unrelated regulatory frameworks.

An NFT collection uses a 'trait-based royalty' model where EIP-2981 royalty percentages vary dynamically based on which traits a token possesses — common traits pay 2.5% while legendary traits pay 10%. A marketplace that honors EIP-2981 calls `royaltyInfo(tokenId, salePrice)` for token #42 (legendary). What does the standard guarantee the marketplace receives?

Answer: The address to send royalties to and the exact royalty amount for that specific token and sale price

EIP-2981 defines a minimal interface: `royaltyInfo(uint256 tokenId, uint256 salePrice)` returns exactly two values — `(address receiver, uint256 royaltyAmount)`. The standard explicitly permits per-token royalty customization; the implementing contract can compute different amounts per tokenId however it wishes. It makes no guarantees about Merkle proofs, IPFS, or enforcing a fixed global rate. The marketplace receives only the receiver address and the computed amount — enforcement of payment is not guaranteed by the standard itself.

A tokenized real-world asset (RWA) platform issues tokens representing fractional ownership of commercial real estate on an EVM chain. The legal wrapper is a Delaware LLC where token holders are members. Which of the following risks is UNIQUE to on-chain tokenization compared to a traditional REIT structure?

Answer: Smart contract oracle risk, where the on-chain token price depends on off-chain property appraisals fed by potentially manipulable data sources

Oracle risk is a risk category that does not exist in traditional REIT structures: on-chain tokenized RWAs rely on external data feeds (oracles) to bring off-chain appraisal values, rent income, or NAV calculations on-chain. These feeds can be stale, manipulated, or fail entirely, creating a disconnect between token price and actual asset value. Traditional REITs use audited financials and regulated pricing without oracle dependency. The other options either misstate REIT rules (REITs need 100+ shareholders, not 100+ properties), incorrectly claim REITs avoid illiquidity, or wrongly assert stablecoin-only settlement.

An artist deploys a generative NFT collection where the artwork is rendered entirely on-chain using SVG stored in the contract's bytecode. The contract has no `tokenURI` override pointing to IPFS. Compared to an IPFS-hosted collection, what is the PRIMARY technical tradeoff the artist accepted?

Answer: Significantly higher deployment gas costs and contract size constraints (EIP-170's 24KB limit) in exchange for permanent, host-independent metadata that cannot be rug-pulled

Storing SVG artwork directly in contract bytecode or via on-chain storage (e.g., SSTORE2) dramatically increases deployment gas costs and must fit within Ethereum's contract size limit (EIP-170: 24,576 bytes). The payoff is permanence: metadata cannot be rug-pulled by an IPFS provider going offline, CID being unpinned, or a centralized server shutting down. The other options are fabrications — ERC-721 transfers are unaffected by where metadata is stored, on-chain storage has no bearing on copyright law, and ERC-4906 is a metadata notification standard that does not gate SVG rendering ability.

A blockchain game uses a 'soulbound' token (SBT) mechanic for player reputation scores, implementing EIP-5192 (Minimal Soulbound NFT). A secondary market exploits the fact that EOA private keys can be sold. To truly prevent reputation transfer, the MOST effective additional mechanism is:

Answer: Restricting token minting to wallets that have passed on-chain KYC via a decentralized identity protocol, then binding reputation updates to zero-knowledge proofs of continued identity

The fundamental weakness of EIP-5192 soulbinding is that it prevents token transfer but not private key sale — the EOA itself can be handed over. The only robust mitigation is binding the credential to a persistent, non-transferable identity rather than a key. Zero-knowledge proof systems (e.g., Semaphore, Polygon ID) allow identity to be proven without revealing it, and re-issuance can require ZK proof of the original biometric or credential, making key sale useless. The ETH balance burn is easily gamed, periodic re-signing only proves key possession (still transferable), and centralization defeats the point of on-chain reputation.

During the NFT market peak in 2021-2022, 'wash trading' was widespread. An analyst examining on-chain data wants to identify wash trades with high confidence. Which combination of heuristics provides the STRONGEST signal that a sale is a wash trade rather than a legitimate arm's-length transaction?

Answer: Funding source overlap (both buyer and seller wallets funded by the same upstream address), sale price significantly above floor with no subsequent resale profit realized, and round-trip settlement within the same block or across few blocks

The strongest wash-trade signal is a combination of (1) shared funding source — both wallets trace back to the same upstream address or the buyer immediately returns funds to the seller's wallet, (2) an inflated sale price that has no economic justification for an arm's-length buyer, and (3) near-instant round-trip settlement indicating the 'buyer' never intended to hold the asset. This triad addresses the core mechanics of wash trading: manufacturing artificial volume and price history without genuine economic exchange. Option A describes some suspicious patterns but misses the funding link. Option C describes multi-listing behavior unrelated to wash trading. Option D conflates privacy-seeking with wash trading and ignores the key funding source signal.