NFTs, Tokenization, and Digital Assets Flashcards

A DeFi protocol issues fractionalized NFTs (F-NFTs) representing ownership shares in a rare digital artwork. When the underlying NFT is locked in a vault and ERC-20 fractions are distributed, which mechanism allows the original NFT to be reconstituted?

Answer: A buyout auction where a single party acquires 100% of the fractional tokens and triggers vault release

In fractionalized NFT protocols (e.g., Fractional.art / Tessera), reconstitution typically occurs via a buyout auction mechanism: any party can initiate a buyout at or above the reserve price. If successful, they acquire 100% of the fractional tokens (either through purchase or by tendering all tokens they hold), which triggers the vault smart contract to release the underlying NFT to the buyer. Governance votes and admin overrides are not standard reconstitution paths in trustless F-NFT protocols.

Under the ERC-1155 multi-token standard, what is the key architectural difference compared to ERC-721 that makes it more gas-efficient for gaming and batch asset issuance?

Answer: ERC-1155 uses a single contract to manage multiple token types (both fungible and non-fungible), enabling batch transfers in one transaction

ERC-1155 is a multi-token standard where a single smart contract manages an arbitrary number of token types — each identified by an ID — which can be fungible, non-fungible, or semi-fungible. Its `safeBatchTransferFrom` function allows transferring multiple token types and amounts in a single transaction, drastically reducing gas costs compared to issuing separate ERC-721 and ERC-20 contracts. Metadata is still typically stored via URI (not compressed on-chain), and it does not natively incorporate L2 proofs or remove approval requirements.

A tokenized real-world asset (RWA) platform issues security tokens representing fractional ownership in commercial real estate. Which legal framework in the United States most directly governs whether these tokens require SEC registration, and which exemption is most commonly used by issuers to avoid full registration?

Answer: The Securities Act of 1933, with issuers most commonly relying on Regulation D (Rule 506(b) or 506(c)) for private placement exemptions

Security tokens representing economic interests in real estate are almost certainly 'securities' under the Howey Test (investment of money in a common enterprise with expectation of profits from others' efforts). The Securities Act of 1933 governs registration requirements. Most RWA token issuers avoid full SEC registration by using Regulation D exemptions — particularly Rule 506(b) (up to 35 non-accredited investors, no general solicitation) or Rule 506(c) (unlimited accredited investors, general solicitation permitted). The Commodity Exchange Act applies to commodity derivatives; the Bank Secrecy Act governs AML compliance; and the Investment Company Act applies to investment companies, not individual token issuers.

A creator mints an NFT with a smart contract that enforces a 10% royalty on all secondary sales. A marketplace decides to bypass this royalty by not calling the royalty payment function during settlement. What technical standard was designed to help enforce on-chain royalties across marketplaces, and what is its fundamental limitation?

Answer: EIP-2981 standardizes royalty information retrieval, but compliance is voluntary — marketplaces can still ignore the payment function since enforcement is not built into ERC-721 token transfers

EIP-2981 is the NFT Royalty Standard — it provides a standardized interface (`royaltyInfo()`) that returns the royalty recipient and amount for a given sale price. However, it is purely informational: the standard only tells marketplaces *how much* to pay and *to whom*, but does not compel payment. Since ERC-721's `transferFrom` and `safeTransferFrom` functions have no built-in royalty enforcement logic, marketplaces can simply call the transfer without invoking royalty logic. ERC-721C (by Limit Break) attempts stricter enforcement via transfer validators, but is a separate, non-universal standard. EIP-4907 is for rentable NFTs and has no royalty enforcement component.

In the context of NFT provenance and metadata permanence, an artist stores their NFT's metadata JSON file on IPFS using a content-addressed hash (CIDv1). Three years later, the artist stops paying for Filecoin storage pinning and all pinning nodes drop the content. What happens to the NFT?

Answer: The NFT's tokenURI still points to the correct IPFS hash, but the metadata becomes unretrievable if no node is actively pinning or caching the content — the token persists on-chain but its associated data is effectively lost

IPFS is a content-addressed, peer-to-peer protocol — content is only available as long as at least one node is actively hosting ('pinning') it. Without pinning, content is subject to garbage collection and can disappear entirely. The NFT's `tokenURI` on-chain still returns the IPFS CID (which is immutable and correct), but resolving that CID will fail if no nodes serve it. Ethereum does not archive IPFS content; smart contracts have no awareness of off-chain storage availability; and IPFS does not guarantee persistence without incentivized pinning services (like Filecoin, Pinata, or nft.storage). This is the classic 'rug pull via IPFS depinning' risk.

A blockchain project creates a 'dynamic NFT' (dNFT) whose metadata evolves based on real-world sports statistics fed by a Chainlink oracle. During a disputed game result, the oracle reports conflicting data in sequential blocks. Which smart contract pattern best mitigates the risk of the NFT's metadata being permanently corrupted by a single erroneous oracle report?

Answer: A time-locked commit-reveal pattern combined with a multi-oracle aggregation (median or majority vote) before writing state changes to the NFT metadata

Dynamic NFTs updating from real-world data face oracle manipulation and erroneous-data risks. The most robust on-chain mitigation is multi-oracle aggregation (e.g., Chainlink's decentralized oracle networks that aggregate from multiple nodes using median values) combined with a time-lock that delays state changes — giving time for dispute detection before metadata is finalized. A commit-reveal scheme further prevents front-running of oracle updates. A single trusted oracle, even with a valid signature, is a single point of failure. Centralized admin overrides reintroduce custodial risk. ERC-4626 is a tokenized vault standard unrelated to oracle dispute resolution.