NFT Capabilities

ERC-721 defines non-fungible tokens (NFTs). Unlike ERC-20 where every token is identical, each ERC-721 token has a unique ID. This enables digital art, collectibles, game items, membership passes, and anything where each item is distinct. It specifies ownership, transfers, approvals, and an optional metadata extension — the foundation of the NFT ecosystem.

Stages: Asset Discovery & Display, Approving & Permissioning +1

ERC-1155 defines balances by account and token ID, allowing one contract to represent fungible quantities and unique items. Its batch transfer moves multiple IDs and amounts to one recipient in a transaction. Clients still need receiver handling, metadata and indexing support; actual fees depend on the transaction and network.

Stages: Asset Discovery & Display, Executing Transactions

Batch minting/transfer events — efficiently create or move thousands of consecutive tokens in one transaction.

Stages: Executing Transactions, Status & Confirmation

ERC-2981 standardizes an NFT royalty query. An implementing contract can return a percentage-based amount and royalty recipient through royaltyInfo(); a sale venue may query and honor that information, but marketplace adoption and payment enforcement vary.

Stages: Asset Management

ERC-4906 is an optional metadata update extension. Its MetadataUpdate and BatchMetadataUpdate events signal JSON metadata changes so indexers can refresh, while collections without the extension still need a fallback refresh policy.

Stages: Asset Discovery & Display

ERC-4907 adds rental functionality to NFTs. The owner can rent out their NFT to a "user" for a set time period. The renter gets usage rights without ownership. When the rental expires, usage rights automatically revert. Perfect for game items, virtual land, or any NFT with utility that can be temporarily shared.

Stages: Approving & Permissioning, Asset Management

ERC-4910 connects NFTs to royalty accounts and subaccounts, supporting hierarchical splits, direct payment processing, listings, and payouts. It does not define a separate royalty bearer token or a general transferable-rights interface; any such asset is an implementation extension.

Stages: Asset Management

ERC-5006 defines ERC-1155 user records with an owner, user, tokenId, amount, and expiry, plus usable and frozen balance views. It does not by itself specify escrow, custody movement, expiry cleanup, rental pricing, or a marketplace; those behaviors must be checked against the target implementation. The pinned reference implementation uses escrow and an authorized deleteUserRecord path, which is implementation-specific.

Stages: Approving & Permissioning, Asset Management

ERC-5007 adds start and end timestamp fields to NFTs. Consuming contracts can use those fields for subscriptions, season passes, or time-limited memberships; enforcement, boundary rules, and renewal remain implementation-specific.

Stages: Asset Management

NFTs have authorized hyperlink slots — owners grant addresses permission to set links on their tokens.

Stages: Asset Discovery & Display, Specialized Interactions

NFTs can reference other NFTs — creating a directed graph of relationships (remixes, derivatives, citations).

Stages: Asset Discovery & Display, Asset Management

NFTs have multiple assets (files) — different outputs based on context (PDF for readers, 3D for games, image for marketplaces).

Stages: Asset Discovery & Display

ERC-6105 defines a direct NFT listing and purchase path through listItem, delistItem, and buyItem. A deployment may avoid relying on an intermediary trading platform, but the standard does not guarantee zero contract, application, royalty, gas, or other fees; show the target implementation's actual terms.

Stages: Asset Management

Filesystem-like hierarchical NFTs — tokens have parent/child relationships like folders and files.

Stages: Asset Discovery & Display, Asset Management

ERC-6220 standardizes on-chain equipment for NFTs through slots, Catalog compatibility, and fixed or equippable part metadata. A compatible renderer may compose the parts, but visual changes, composed-image generation, marketplace support, and cross-platform display remain collection and client policy.

Stages: Asset Management

Tokens can be non-transferable (soulbound) or have transfer restrictions — verifiable on-chain.

Stages: Asset Management

Streamlined multi-token with granular per-token-type approvals and no mandatory callbacks — simpler than ERC-1155.

Stages: Asset Discovery & Display, Approving & Permissioning +1

NFTs can be locked in the owner's wallet. While locked, ERC-721 approval and transfer are restricted, with an exception when the caller is both the approved address and the locker; other application utility is implementation-specific.

Stages: Asset Management

ERC-7401 is the Final successor to ERC-6059 for parent-governed NFT nesting. It preserves the nesting model while correcting the interface identifier; compatible collections can expose accepted and pending children, and products should verify the target implementation before promising transfer or extraction behavior.

Stages: Asset Discovery & Display, Executing Transactions +1

ERC-7432 defines NFT role records with recipients, expiration, revocation policy, custom data, approval, and lock/unlock behavior. It does not define a role marketplace, price, purchase flow, or escrow; those are optional application layers over a verified role policy.

Stages: Approving & Permissioning, Asset Management

ERC-7631 links an ERC-20 base and ERC-721 mirror pair and standardizes how the relationship is queried. Synchronization, minting, ratios, and transfer policy remain implementation-specific; optional skip-NFT methods may be unavailable.

Stages: Asset Discovery & Display

NFTs can have a maximum count for native ERC-721 transfers. After the cap is reached, the implementation chooses the resulting state; locking, burning, or another action is not mandated by ERC-7634.

Stages: Executing Transactions, Asset Management

ERC-7858 reports block-based or time-based expiration for NFTs and SBTs. Utility consumers must enforce the reported expiry; ownership and ordinary transfer behavior remain governed by the token implementation.

Stages: Asset Management

ERC-6551 defines a registry that computes deterministic token-bound account addresses for NFTs and can deploy them as smart-contract accounts. A deployed or counterfactual account can hold assets, but each NFT may have multiple accounts across implementations, registries, chains, and salts; sale contents must be rechecked at settlement.

Stages: Asset Discovery & Display, Executing Transactions +1