An Ethereum interface standard for non-fungible token contracts. A token is uniquely identified within its contract, but the standard does not establish authenticity, legal title, metadata permanence, or value.
Supports: Defines token identifiers, ownership, transfers, approvals, optional metadata, optional enumeration, and the scope of the interface.
Supports: Explains the ERC-721 token standard and its use for non-fungible token contracts on Ethereum.
ERC-721 standardizes tracking and transfer of non-fungible token identifiers on Ethereum
The contract address and token ID together identify an ERC-721 token on a particular chain
Metadata and enumeration extensions are optional and may use external resources
The standard does not prove title, authenticity, copyright, scarcity, or investment value
Before approving a marketplace, a holder confirms the chain, contract address, token ID, and exact operator permission. They check whether metadata is on-chain or points to an external URI and revoke any broad operator permission they no longer need. The ERC-721 interface can show on-chain control of that token ID; it does not independently verify the collection's claims.
An application that combines a user interface with smart contracts or other decentralized-network components. Its interface, data services, wallet connection, and operations may still have centralized dependencies.
An Ethereum token-interface standard for fungible token contracts. It specifies common methods and events, but it does not certify a token, its issuer, its economics, or its safety.
A protocol action that creates or assigns token units under a contract or network's issuance rules. What is minted, who can mint, supply limits, backing, transferability, and holder rights are implementation-specific.
A program and its state deployed at a blockchain address, which runs its defined functions when transactions call it.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles