Glossary · Tokens
Published 28 Apr 2025 · Updated 2 Nov 2026 · 14 min read
ERC-721 is the Ethereum standard interface for non-fungible tokens, where one smart contract tracks distinct tokens, each with its own ID and owner. Wallets, marketplaces, and apps read and move them through shared calls. EIP-721 reached Final status in June 2018. Minting and burning are outside its scope, and metadata is optional.
An NFT ownership record maps each token ID to one owner inside a smart contract. On one chain, the contract address and ID identify that asset together. Each uint256 ID stays fixed, with no required numbering pattern. The token's owner, an approved address, or an operator can move it. The Transfer event records changes, including creation from the zero address and destruction to it. These ERC-721 event directions distinguish minting from burning.
Pick a sender, a call, a token and a recipient, then send the transaction.
Alice starts with two tokens. Each creation emitted a Transfer event from the zero address.
The marketplace may move this one token. The owner's other tokens remain outside this permission.
The new operator can move every token the sender owns in this contract, not just the selected ID.
Ownership moved to the recipient, and the token's individual permission cleared without a separate Approval event.
The receiving contract returned 0x150b7a02 from onERC721Received, so the compatibility check passed and ownership changed.
transferFrom succeeded, but this contract cannot move the received NFT, leaving it stuck at that address.
The call failed with an OpenZeppelin error, such as ERC721InsufficientApproval. Ownership and permissions remain unchanged.
Rules, errors, and gas use OpenZeppelin Contracts 5.7.0, run by the page team on a local test chain.
The approve function names one address that may move a particular token. setApprovalForAll gives an operator access to all the owner's tokens in that contract. Every transfer clears the single-token approval. An authorized operator can also assign that permission to another address. Unlike an ERC-20 allowance, this permission has no spendable quantity. ERC-721 authorizes none or one for each token.
The transferFrom function leaves recipient compatibility to the caller, so an NFT can become permanently inaccessible. safeTransferFrom instead calls onERC721Received when the destination has code. Acceptance requires the magic value 0x150b7a02, not merely true, which older contracts could return without implementing the function. OpenZeppelin performs this callback after changing ownership state. The receiver can therefore call back before the surrounding application finishes. A missing function or wrong return value raises ERC721InvalidReceiver in this implementation. A receiver's own revert reason passes through.
The Ethereum Request for Comments category includes application standards such as ERC-721. This interface requires nine functions and three events, alongside ERC-165 support. The two safeTransferFrom forms count separately, with one accepting extra data for the recipient. The ERC-165 check must use less than 30,000 gas.
| Function or event | What it does | A rule from EIP-721 |
|---|---|---|
| balanceOf | What it doesCounts the NFTs held by a specified owner address | A rule from EIP-721Queries for the zero address must throw rather than return a balance |
| ownerOf | What it doesReturns the current owner address for a specified token ID | A rule from EIP-721Queries for an NFT that does not exist must throw |
| transferFrom | What it doesMoves one NFT without checking the recipient contract's receiving interface | A rule from EIP-721The caller must be the owner, approved address, or authorized operator |
| safeTransferFrom | What it doesMoves one NFT and checks acceptance when the recipient has code | A rule from EIP-721A receiving contract must return 0x150b7a02 from onERC721Received |
| approve | What it doesSets the single address authorized to move a particular token | A rule from EIP-721Only the owner or an authorized operator may set this permission |
| setApprovalForAll | What it doesEnables or disables an operator's control over all the caller's holdings | A rule from EIP-721The contract must support several operators for each owner |
| getApproved and isApprovedForAll | What it doesReads the authorized address for one token or an owner's operator permission | A rule from EIP-721getApproved must throw when the queried NFT does not exist |
| Transfer event | What it doesRecords changes of ownership, including creation and destruction of NFTs | A rule from EIP-721All three parameters are indexed, giving each log four topics |
| Approval and ApprovalForAll events | What it doesRecords permissions for individual tokens and operators across an owner's holdings | A rule from EIP-721Successful approve and setApprovalForAll calls must emit their respective events |
ERC-721 applications can ask which set of calls a token contract claims to support before interacting with it. ERC-165 provides this check through supportsInterface. Each function signature produces a four-byte selector, taken from the start of its keccak-256 hash. Combining those selectors with XOR gives the interface ID for that set of functions. Applications check core support and optional extensions separately, rather than treating them as one combined interface.
All nine core functions combine to 0x80ac58cd. Both overloaded safeTransferFrom signatures contribute their own selectors.
The name, symbol, and tokenURI functions combine to 0x5b5e139f, identifying the optional token metadata interface rather than core ownership.
The totalSupply, tokenByIndex, and tokenOfOwnerByIndex functions combine to 0x780e9d63, identifying the optional interface for listing token IDs on chain.
The onERC721Received function produces 0x150b7a02, which also serves as the exact value required to accept a safe delivery.
The supportsInterface function alone produces 0x01ffc9a7. That value identifies ERC-165 itself, rather than any particular asset standard.
This selection matches no listed interface. Omitting safeTransferFrom(address,address,uint256) produces 0xc22876c3 instead of the core ID.
The page team computed selectors with keccak-256 and checked them against the IDs printed in EIP-721 and ERC-165.
The core ERC-721 ID is 0x80ac58cd. Its metadata extension is 0x5b5e139f, and its enumerable extension is 0x780e9d63. The receiver uses 0x150b7a02, while ERC-165 itself uses 0x01ffc9a7. A compliant response must be false for 0xffffffff. ERC-4906 differs because it defines events rather than functions. It uses the fixed interface ID 0x49064906 instead of a selector XOR.
Artwork and descriptive data are not part of the required token ownership interface. The optional metadata extension adds name, symbol, and tokenURI. EIP-721's JSON schema defines only name, description, and image. Fields such as attributes and animation_url follow marketplace conventions instead.
| Where it lives | What tokenURI returns | Who keeps the data | What can go wrong |
|---|---|---|---|
| HTTPS server | What tokenURI returnsHTTPS JSON file address | Who keeps the dataThe server operator hosts the referenced JSON and linked files | What can go wrongFiles can change or disappear without changing the token's ownership record |
| IPFS | What tokenURI returnsipfs:// followed by a CID | Who keeps the dataParticipants retain copies through the IPFS storage network, including pinned data | What can go wrongUnpinned copies eventually disappear, and individual gateways can go offline |
| Arweave | What tokenURI returnsar:// followed by an identifier | Who keeps the dataArweave stores the content referenced by the returned URI | What can go wrongStorage location alone establishes neither authenticity nor rights to content |
| On-chain data URI | What tokenURI returnsBase64 JSON data URI | Who keeps the dataThe contract returns Base64 JSON directly through its data URI | What can go wrongPutting all descriptive data on chain increases transaction gas costs |
EIP-721 allows a mutable URI, so an NFT's description can change after creation. ERC-4906 provides update events for indexers, not a freeze mechanism. Storing a 66-character IPFS URI through ERC721URIStorage adds about 92,000 gas per token minted in the page team's test. In August 2026, IPFS reports rate limits for hotlinked and backend traffic on two public gateways. Keeping data available and keeping its contents fixed are separate concerns.
Asset models determine which questions an application can ask. The ERC-20 token standard tracks interchangeable quantities, ERC-721 tracks distinct token owners, and ERC-1155 tracks balances for each ID. Similar-looking actions can therefore involve different data, permissions, and transaction counts.
| ERC-20 | ERC-721 | ERC-1155 | |
|---|---|---|---|
| What one contract holds | ERC-20One fungible token with interchangeable units | ERC-721One collection of distinct tokens | ERC-1155Multiple token types with separate supplies |
| Ownership lookup | ERC-20Balances rather than individual owners | ERC-721ownerOf for each individual token ID | ERC-1155balanceOf(owner, id) and balanceOfBatch |
| Approvals | ERC-20An allowance spent across multiple calls | ERC-721One token or all owner holdings | ERC-1155All holdings through setApprovalForAll only |
| Batch transfers | ERC-20One call moves a fungible amount | ERC-721No batch transfer in the standard | ERC-1155Built-in safeBatchTransferFrom for multiple IDs |
| Receiver check | ERC-20No standard receiver check | ERC-721Only when using safeTransferFrom | ERC-1155Required for contract recipients, including batches |
| Typical use | ERC-20Interchangeable units of one asset | ERC-721Collectibles with individual token ownership records | ERC-1155Mixed fungible and non-fungible items |
Ten plain ERC-721 mints cost 277,043 gas, compared with 73,688 for an ERC-721A batch in this test.
Sending ten distinct IDs costs 427,320 gas across ten ERC-721 transactions, versus 272,903 for one ERC-1155 batch.
Marketplace approval costs 46,678 gas for ERC-20, compared with 46,184 for both ERC-721 and ERC-1155.
The page team measured gas with OpenZeppelin 5.7.0 and ERC721A 4.3.0 on a local chain, including the 21,000 base cost.
The transaction gas costs reflect what each standard stores and how many transactions a task needs. The ERC-20 mint creates 100 units. Per-token storage makes ERC721Enumerable's existing-holder mint cost 146,038, against 51,659 for plain ERC-721. ERC-721A batches reduce mint writes, but the first transfer of a middle token from a fresh batch costs 90,345. ERC-1155 batches distinguish ten IDs from ten units of one ID. Those mints cost 264,642 and 33,352 respectively.
In November 2026, OpenZeppelin Contracts 5.7.0 is the newest GitHub release, while npm tags 5.6.1 as latest. Its ERC721 implementation uses custom errors and the _update hook. The options below add indexing, rentals, royalties, and other behavior. ERC-721A is an implementation, not an EIP.
| Extension | What it adds | Status | Trade-off or limit |
|---|---|---|---|
| ERC721Enumerable | What it addsLists every token ID and each owner's holdings directly on chain | StatusOptional EIP-721 extension, 2018 | Trade-off or limitAdds substantial gas overhead and forbids batch minting in OpenZeppelin |
| ERC-2309 | What it addsSignals a consecutive token ID range through one ConsecutiveTransfer event | StatusFinal, created 2019 | Trade-off or limitTransfer must not also be emitted for the same operation |
| ERC-721A | What it addsReduces batch mint storage writes to three regardless of quantity | StatusImplementation, v4.3.0 March 2024 | Trade-off or limitStill emits an individual Transfer event for every minted token |
| ERC-2981 | What it addsReturns a royalty recipient and amount through royaltyInfo | StatusFinal, created 2020 | Trade-off or limitPayment remains voluntary and depends on the marketplace handling the sale |
| ERC-4906 | What it addsSignals changed metadata through MetadataUpdate and BatchMetadataUpdate events | StatusFinal, created 2022 | Trade-off or limitNotifies indexers of metadata changes but does not prevent those changes |
| ERC-4907 | What it addsSeparates a temporary user role from ownership with an expiry | StatusFinal, created 2022 | Trade-off or limitThe user may use the NFT but cannot transfer it |
| ERC-5192 | What it addsDefines minimal soulbound token behavior through the locked status | StatusFinal, created 2022 | Trade-off or limitEvery transfer function must throw whenever locked(tokenId) returns true |
| ERC-6551 | What it addsGives each NFT a smart contract account through a registry | StatusReview, not final, created 2023 | Trade-off or limitSending an NFT to its own token bound account locks its assets |
Shared interfaces make integrations possible, not transactions safe. ERC-721 does not prevent front-running, where searchers can reach a popular NFT drop or mispriced listing first. That behavior falls under maximal extractable value. The following limits concern permissions, execution, and off-chain claims.
setApprovalForAll exposes all of an owner's tokens in that contract to an operator. Scam Sniffer reports $494 million in drainer losses during 2024 across all asset types, not just NFTs.
Fake marketplace emails can solicit harmful listing signatures. A 20 February 2022 incident affected 28 accounts. SlowMist notes that stolen signatures cannot be revoked through sites such as Revoke.
onERC721Received can reenter unfinished application logic. Omni Protocol lost about $1.4 million on 10 July 2022 through functions lacking reentrancy locks. Omni reported that only internal testing funds were affected.
A transferFrom call to a contract with neither onERC721Received nor a function to move the token succeeds, and the token stays there. OpenZeppelin's safeTransferFrom would revert with ERC721InvalidReceiver.
An unchanged token owner record cannot guarantee an unchanged image. OpenZeppelin's guide warns that a game developer could change the underlying metadata and, with it, the rules of the game.
Names and symbols can be copied. Holding an NFT grants no automatic asset rights or copyright. ERC-2981 payments remain voluntary, including transactions through an NFT aggregator.
The Ethereum Improvement Proposal records a shared interface, while libraries and later ERCs extend its behavior. This timeline separates the original standard's development from changes in implementation, so later features are not mistaken for core requirements.
Dieter Shirley opens GitHub issue #721, titled "ERC: Non-fungible Token Standard". The proposal concerns assets that need separate ownership records.
Axiom Zen launches CryptoKitties on 28 November 2017. EIP-721 later lists the project as compatible with an earlier version of the standard.
ERC-165 is created on 23 January 2018. EIP-721 follows on 24 January 2018, authored by William Entriken, Dieter Shirley, Jacob Evans, and Nastassia Sachs.
The standard reaches Final status on 21 June 2018. ERC-1155 is created on 17 June 2018, introducing a separate interface for multiple asset types.
ERC-2309 is created on 8 October 2019. It defines a range event for consecutive IDs, rather than requiring an individual event for every item.
Azuki uses ERC-721A for its 12 January 2022 sale of 8,700 tokens. The implementation reduces storage writes while retaining individual ownership-change logs.
OpenZeppelin Contracts 5.0 arrives on 5 October 2023. It replaces revert strings with custom errors and replaces two movement hooks with the internal _update function.
OpenZeppelin Contracts 5.7.0 is released on 29 July 2026. The release adds bridge contracts for cross-chain ERC-721 transfers, extending the library beyond its existing ownership implementation.
We build NFT contracts around product rules, not just an ERC-721 interface label. Our NFT smart contract development covers ERC-721 and ERC-1155, minting controls, royalty logic, proxy upgrades, and decentralized storage integration. The choices below define how the product behaves beyond basic compatibility. They also identify what marketplaces and indexers need to observe.
PixelPlex was founded in 2007 and has worked in blockchain since 2013. In our Savage marketplace project from 2021, we built a Polygon marketplace for high-resolution video. Its ERC-721 token contract uses OpenZeppelin Contracts. Files and data were published to the blockchain and IPFS through Pinata.
Discuss the requirements behind your NFT product
We can discuss the contract behavior, storage choices, and marketplace integration your project needs to define.
Discuss your requirementsGet updates about blockchain, technologies and our company
We will process the personal data you provide in accordance with our Privacy policy. You can unsubscribe or change your preferences at any time by clicking the link in any email.Services
Blockchain
Blockchain consultingStrategy, architecture, feasibility
Crypto wallet developmentSelf-custody, MPC, cards on top
Cryptocurrency exchange developmentTrading venues, liquidity and protocols
Tokenization servicesRWA, funds, collateral
Crypto payments developmentAccept, settle and pay out in crypto
Smart contracts developmentDesign, build, audit
Blockchain integration dApp development DeFi development NFTs Tokens Web3 development All blockchain services All servicesNetworks
Canton developmentDaml apps, wallets, settlement, validators
Official Partner
Ethereum developmentSmart contracts, L2s and dApps
Solana developmentHigh-throughput programs and dApps
TON developmentMini apps, wallets, Telegram ecosystem
Official Partner
Hedera developmentHashgraph apps and token services
Exclusive Partner
Hyperledger developmentPermissioned networks for enterprises
Certified Partner
Cardano Algorand Stellar Avalanche Bitcoin Polygon All networks All servicesAI & ML
AI agents developmentConnect tools and automate multi-step workflows
RAG developmentFind answers across your company’s documents and systems
AI copilot developmentAdd useful assistance to your product or internal tools
LLM developmentCustom and fine-tuned models for your domain
Private AI deploymentRun models in your own environment
AI consultingUse cases, feasibility and a roadmap
Generative AI development Machine learning development Computer vision Chatbot development ChatGPT integration Deep learning development All AI services All servicesData & analytics
Data engineeringPipelines that keep your data reliable
Data platform developmentOne source of truth for analytics
Analytics & dashboards developmentBI your teams actually use
Predictive analyticsForecasts built on your own history
Data strategyWhere data can pay off first
Data visualizationDashboards and visual stories from your data
Data science development Development of data marts All data services All servicesSoftware
Product discoveryValidate scope and cost before you build
MVP developmentA launch-ready first release
Web application developmentPlatforms, portals and internal tools
Mobile app developmentiOS, Android and cross-platform
SaaS developmentMulti-tenant products that scale
Software integrationConnect the systems you already run
Infrastructure & cloud cost UI/UX design IT consulting QA & software testing R&D Serverless development All software services All servicesSecurity & compliance
Smart contract auditsFind vulnerabilities before launch
Transaction monitoring developmentIntercepta inside your systems and processes
Security assessmentsTest apps, infrastructure and processes
Data security servicesProtect sensitive data across its lifecycle
Cloud security servicesSecure cloud workloads and configurations
DAML smart contract auditReview DAML contracts before they go live
All security services All servicesSolutions
Products, APIs and platforms
New
Products and engineering to build and operate on Canton.
In production 55M API requests served in 8 months
Crypto APIBlockchain data for your applications.
Power in numbers 6 TB Data storage. 500K Tokens indexed
RWA platformA foundation for your asset tokenization platform.
Time to launch 2–4 weeks Branding & setup. 90% more cost-efficient
DocFlowBlockchain-based document management.
Use case & value 100% Secure workflows. Zero third-party risks.
OTC Hawk Arbitrage Bot Book a solution consultWork
450+ projects. 250+ clients. 3 unicorns in portfolio
The first non-custodial wallet built natively for Canton
TON ecosystemA series of improvements for The Open Network
Mining platformEnvironmentally friendly web platform for Bitcoin pool mining
Mantra DAOCommunity-governed DeFi: 60+ staking pools, $23M TVL
Canton TON Web3 & DeFi Digital Assets & Tokenization AI & Data Intelligence IoT & Edge Computing Consulting See all projectsIndustries
Trusted by startups, small businesses, and enterprises
Banking, payments, lending, insurance, capital markets
Real estate software developmentInvestment, property operations, tokenization
Retail & commerce software developmentCommerce, loyalty and fulfillment
Supply chain software developmentTraceability and connected operations
Healthcare software developmentPatient services, data and connected systems
Banking software developmentCore banking, digital channels, payments
Fitness Education Oil & Gas Insurance Construction TravelCompany
From R&D to launch, we bring any of your ideas to life
Engineering partner. Product builder. Since 2007.
Technical experience 19+ years All competencies on board. Scalable team.
AchievementsIndustry recognition & awards.
Delivering real value 4.9 Clutch ratings. 150+ awards
Contact usDiscuss your project.
Quick response 30 min Average reply time. Offices in 6 countries
BlogDive into the latest software trends.
Fresh insights 500+ Articles in blockchain, AI, big data, AR/VR
Team Careers Social responsibility Glossary