Skip to main content
Ethereum & smart contracts

ERC-721: The NFT Standard

Pomegra Learn

ERC-721: The NFT Standard

The ERC-721 standard is the technical foundation of non-fungible tokens (NFTs). While NFTs have become synonymous with digital art and collectibles in popular culture, the standard itself is a remarkably elegant solution to representing unique, indivisible assets on a blockchain. ERC-721 enabled everything from digital art marketplaces to game items, domain names, and real-world asset tokenization.

Unlike ERC-20 tokens, which are fungible (each token is identical and interchangeable), ERC-721 tokens are non-fungible—each one is unique and identified by a distinct token ID. You cannot divide an ERC-721 token into smaller pieces. You cannot trade one ERC-721 token for another and expect them to have equivalent value, because they're different assets with potentially very different properties.

The Concept of Non-Fungibility​

Fungibility is about interchangeability and divisibility. A dollar bill is fungible—one dollar bill is as good as any other, and you can split dollars into cents. A painting is non-fungible—the Mona Lisa is unique and cannot be divided into smaller paintings that are each worth a fraction of the whole.

Blockchain technology before ERC-721 could represent fungible assets (cryptocurrency, tokens) but lacked a standard way to represent unique, indivisible items. Early projects created custom smart contracts for each use case, leading to fragmentation and poor interoperability.

ERC-721, proposed by William Entriken, Dieter Shirley, Jacob Evans, and Nastassia Sachs in January 2018, standardized how unique items are represented and transferred on Ethereum. The proposal drew inspiration from earlier collectible projects like CryptoPunks and CryptoKitties but formalized the pattern into a reusable standard.

Core Functions and Events​

ERC-721 contracts track ownership of individual tokens identified by unique ID numbers. The standard requires several core functions:

balanceOf(owner) returns how many NFTs a specific address owns. Unlike ERC-20, which tracks the amount of tokens, ERC-721 simply counts tokens owned regardless of their IDs.

ownerOf(tokenId) returns the address that owns a specific token. This is the fundamental ownership registry—given a token ID, you learn who owns it.

safeTransferFrom(from, to, tokenId) safely transfers an NFT from one address to another. "Safe" means the function checks that the recipient can properly handle NFTs (important if the recipient is a smart contract rather than a user wallet). If the recipient is a contract without proper NFT-handling capability, the transfer fails rather than getting stuck.

transferFrom(from, to, tokenId) performs an unsafe transfer. It works even if the recipient is a contract that doesn't support NFTs, meaning tokens can be sent to contracts that lose them forever. Modern best practices recommend always using safeTransferFrom.

approve(to, tokenId) grants permission to a specific address to transfer a particular token. This mirrors ERC-20's approval but operates on individual tokens rather than fungible amounts.

setApprovalForAll(operator, approved) grants or revokes an operator's permission to transfer all tokens belonging to the caller. This allows you to authorize a marketplace to sell your entire collection without approving each item individually.

getApproved(tokenId) returns which address (if any) is approved to transfer a specific token.

isApprovedForAll(owner, operator) checks if an operator has blanket approval to manage all of an owner's tokens.

ERC-721 requires two events:

Transfer is emitted when a token changes ownership, including at minting and burning.

Approval is emitted when approval is granted for a specific token or for all tokens.

Metadata and Off-Chain Data​

Individual NFTs often need associated data—images, descriptions, attributes, provenance. ERC-721 doesn't store this data on-chain because images and detailed metadata are too expensive to store (images typically cost thousands to millions of gas to store on Ethereum).

Instead, ERC-721 contracts typically implement a tokenURI function that returns a URL pointing to metadata stored off-chain, usually on IPFS or centralized servers. The metadata is usually formatted as JSON following the ERC-721 Metadata JSON Schema:

{
  "name": "Asset Name",
  "description": "Asset Description",
  "image": "ipfs://...",
  "attributes": [
    {"trait_type": "Color", "value": "Red"},
    {"trait_type": "Rarity", "value": "Legendary"}
  ]
}

This architecture provides a balance: unique identifiers and ownership records live on-chain in the immutable blockchain, while the asset's visual and descriptive data can live anywhere, providing flexibility and cost efficiency.

Use Cases for ERC-721​

The ERC-721 standard has enabled diverse applications:

Digital Art and Collectibles dominated early adoption. Platforms like OpenSea, SuperRare, and Foundation allow artists to mint and sell unique digital works. Each artwork becomes an NFT with provenance recorded on the blockchain, creating a verifiable ownership chain.

Gaming uses ERC-721 for in-game items, characters, and land. Games like Axie Infinity feature NFT characters that players own and can trade. Because these items are NFTs, their ownership is recorded on a public blockchain, preventing the developer from arbitrarily removing or stealing player assets.

Domain Names like Ethereum Name Service (ENS) use ERC-721 to represent domain ownership. When you own an ENS domain like vitalik.eth, you're holding an ERC-721 token that maps your username to an Ethereum address.

Real-World Assets are increasingly being tokenized as NFTs. Property deeds, event tickets, certificates of authenticity, and intellectual property can be represented as ERC-721 tokens, enabling programmable ownership and transfer.

Memberships and Access Control use NFTs to grant privileges. A community might mint NFTs that grant holders access to exclusive spaces, voting rights, or benefits.

Marketplaces and Trading​

ERC-721's standardization enabled the creation of general-purpose NFT marketplaces. OpenSea, the largest NFT marketplace, works with any ERC-721 contract without requiring custom integration. Users can mint NFTs through OpenSea's interface or through custom contracts, then list and sell them.

When you list an NFT on OpenSea, you're granting the marketplace contract approval to transfer your token. The marketplace uses safeTransferFrom to execute sales when buyers purchase. This pattern has become standard across all major NFT platforms.

Marketplace fees (typically 2-5%) are taken during the sale and paid to the marketplace. Creators can also set royalties, allowing them to earn a percentage of every secondary sale in perpetuity. However, royalty enforcement has proven challenging—newer marketplaces sometimes ignore creator royalties to undercut competitors.

Ownership and Custody​

One of ERC-721's key innovations is that ownership is publicly verifiable and immutable. When you own an NFT, that ownership is recorded on the Ethereum blockchain. No company, no authority, no smart contract developer can remove or alter that record (though they could theoretically change the associated metadata off-chain).

This contrasts sharply with traditional digital ownership models where companies control access to digital items. If you buy a digital game on Steam, Valve can revoke your license. If you own an ERC-721 NFT, no one can revoke your ownership without your consent.

However, this also creates responsibility. If you lose your private keys, your NFTs are permanently inaccessible. If you send them to the wrong address, they cannot be recovered. There is no customer service department to undo your mistake.

Energy Consumption and Environmental Concerns​

Early ERC-721 projects raised environmental concerns because Ethereum used Proof of Work consensus, which requires substantial computational power and electricity. The environmental impact was significant enough that some artists publicly distanced themselves from NFTs.

Ethereum's transition to Proof of Stake in September 2022 (the Merge) reduced energy consumption by over 99%. Modern ERC-721 minting and trading on Ethereum now uses negligible electricity compared to the Proof of Work era. Layer 2 solutions further reduce energy by processing thousands of transactions with a single Ethereum settlement.

For more context, see Ethereum's Proof of Stake and The Merge explained.

Security and Common Issues​

ERC-721 has been the target of various exploits and vulnerabilities:

Unauthorized Transfers: If approval is granted incorrectly, an attacker might transfer tokens. The safeTransferFrom function adds a layer of protection, but developers must use it correctly.

Metadata Vulnerabilities: If metadata is stored on centralized servers, the server could be hacked or go offline, leading to broken or modified data for NFTs. IPFS addresses this by using content-based addressing, but IPFS requires active pinning to remain available.

Approval Attacks: Granting blanket approval to marketplace contracts poses risks if the contract is exploited. Best practices now include using marketplace-specific proxies and periodically reviewing approvals.

Floor Price Manipulation: In illiquid markets, attackers can artificially inflate floor prices through wash trading, misleading buyers about true market value.

Caution is warranted when interacting with new NFT projects. Many scams use similar names to legitimate projects or create fraudulent marketplace front-ends.

ERC-721 vs. ERC-1155​

While ERC-721 is excellent for unique assets, ERC-1155 offers advantages when you need to manage multiple token types or semi-fungible items. ERC-1155 allows a single contract to manage many different token types, each with their own supply and properties.

Games often prefer ERC-1155 because a single contract can manage both unique items (your hero character) and fungible items (potions). The efficiency gains are also significant—ERC-1155 can batch multiple transfers in one transaction, reducing gas costs.

Creating and Deploying ERC-721 Contracts​

Creating an ERC-721 contract requires implementing the standard functions and tracking token ownership. Modern developers use libraries like OpenZeppelin, which provide secure, audited implementations.

The typical deployment flow for an artist or project:

First, you write a custom contract inheriting from OpenZeppelin's ERC-721 implementation. You specify the token name, symbol, base URI for metadata, and any special logic (minting caps, royalties, etc.).

Second, you deploy the contract to Ethereum (or a Layer 2 network) and verify the code on Etherscan for transparency.

Third, you mint tokens either through your own interface or through an aggregator like OpenSea. Each mint assigns a unique token ID to a wallet and emits a Transfer event.

Finally, you can list tokens for sale on marketplaces or transfer them to others.

NFT Ownership and Transfer​

Royalties and Creator Rights​

ERC-721 includes an optional interface (EIP-2981) for specifying royalties. When set, marketplaces can automatically send a percentage of sale proceeds to the creator's wallet. This allows artists to earn from secondary sales indefinitely.

However, royalty enforcement is voluntary. Centralized marketplaces like OpenSea respect royalties, but some decentralized exchanges allow direct peer-to-peer trades that bypass royalties. This has led to tension between artists and marketplace operators about the future of creator earnings.

The Broader NFT Ecosystem​

Beyond ERC-721, the NFT ecosystem includes:

ERC-1155: Multi-token standard for mixed fungible and non-fungible items.

ERC-1167: Minimal proxy pattern for cheap contract deployment.

ERC-2981: Standard royalty interface, increasingly adopted.

Layer 2 NFTs: Marketplaces and minting platforms on Arbitrum, Optimism, and other scaling solutions with dramatically lower gas costs.

The ecosystem continues evolving rapidly, with new standards addressing use cases like dynamic NFTs, fractional ownership, and cross-chain compatibility.

Conclusion​

ERC-721 transformed Ethereum from a platform for trading fungible tokens into a platform for representing and trading unique assets. By defining a standard interface for non-fungible tokens, it enabled millions of individuals and organizations to mint, buy, and sell digital assets in a transparent, verifiable way.

The environmental improvements from the Merge and the scaling improvements from Layer 2 solutions have addressed many early criticisms. As the ecosystem matures, ERC-721 will likely remain foundational while newer standards address increasingly sophisticated use cases.

References​