ERC-721 NFT Standard

⬢ TIER 1Tech

High

Salary impact

1 months

Time to learn

Medium

Difficulty

—

Careers

At a glance

ERC-721 is Ethereum's standard for non-fungible tokens (NFTs), unique, indivisible digital assets. Each token ID represents one-of-a-kind item (artwork, deed, collectible). Unlike ERC-20 (one token = another), ERC-721 tokens are distinct (token 1 ≠ token 2). Every major NFT project (CryptoPunks, Bored Apes, ENS) uses ERC-721. Learning takes 2-3 weeks for Solidity devs; mastery (metadata, enumeration, gas optimization) takes 2 months. Senior NFT engineers earn $150K+ because the NFT market is $10B+.

What is ERC-721 NFT Standard

ERC-721 is Ethereum's standard for non-fungible tokens (NFTs), unique, one-of-a-kind digital assets. Each token ID represents a distinct item: a specific artwork, a domain name (ENS), a deed, a game character. Unlike ERC-20 tokens where one equals another, ERC-721 tokens are individually tracked and valued. A single ERC-721 contract can mint 1M+ unique tokens. Each has a tokenId, an owner (wallet address), and metadata (name, image, attributes). The metadata typically lives on IPFS (decentralized storage); the contract stores only the URI pointing to it. Wallets and marketplaces query tokenURI(id) to display the token.

🔧 TOOLS & ECOSYSTEM

SolidityOpenZeppelin contractsHardhat or TruffleIPFS for metadataWeb3.js or Ethers.jsOpenSea API

💰 Salary by region

Region	Junior	Mid	Senior
USA	$90k	$150k	$230k
UK	$55k	$92k	$140k
EU	$60k	$100k	$150k
CANADA	$95k	$160k	$250k

🎓 Certifications

ERC-721 Specification OpenZeppelin ERC-721 Solidity by Example, ERC-721

❓ FAQ

What's the difference between ERC-721 and ERC-1155?

ERC-721: Each token ID is unique. Token 1 ≠ token 2. Use for art, collectibles, deeds. ERC-1155: Supports both unique and fungible tokens. Use when you have multiple asset types (game: weapons + currency). 721 is simpler, 1155 is more flexible.

How does metadata work in ERC-721?

Each token has a URI (like ipfs://xyz.json) pointing to metadata (name, image, attributes). Contract stores URI, metadata stored off-chain (IPFS). Metadata is JSON: {name: 'Punk #123', image: 'ipfs://...', attributes: []}. Marketplaces fetch metadata via tokenURI(id).

What's enumeration and why do I need it?

Enumeration = ability to list all tokens (totalSupply) and iterate through them. Needed for: portfolio views (show all my NFTs), market stats (top 10 collections). Standard ERC-721 doesn't include enumeration; add via ERC721Enumerable.

How do I prevent someone from minting a million NFTs?

Add access control: only owner/whitelisted addresses can mint. Or use payment: require 0.5 ETH per mint. Or supply cap: maxSupply = 10,000; revert if minted > maxSupply. Combine multiple restrictions.

Can I change metadata after minting?

If URI points to mutable server, yes. But then it's not really a permanent digital asset. Better: use immutable IPFS URIs (hash-based). If you need updates, use token-specific URIs and store hash on-chain to prove immutability.