Mutable metadata, on-chain state, and the problems that appear the moment an NFT stops being static.
Metadata is the information that defines an NFT 's characteristics, including its name, description, image, and attributes. It's the data that makes each NFT unique and can be stored on-chain or off-chain .
Standard Fields
Name : NFT title
Description : Text description
Image : Visual representation
External URL : Project website
Attributes : Traits and properties
{
"name": "Bored Ape #1234",
"description": "A unique Bored Ape",
"image": "ipfs://Qm.../1234.png",
"attributes": [
{
"trait_type": "Background",
"value": "Blue"
},
{
"trait_type": "Fur",
"value": "Golden"
}
]
}
Copy link
Storage Methods
Stored directly on blockchain
Permanent and immutable
Higher minting cost
Limited size
Examples: Autoglyphs, Blitmap
Stored externally (IPFS, Arweave, centralized servers)
Referenced via URI in smart contract
Lower cost
Can be larger files
Most NFTs use this
Centralized vs Decentralized
Storage Pros Cons IPFS Decentralized Can be slow Arweave Permanent Higher cost AWS/S3 Fast, reliable Centralized risk
{
"name": "...",
"description": "...",
"image": "...",
"attributes": [...]
}
Copy link
Similar to ERC-721 but supports:
Multiple copies
Different token types
Batch transfers
Create : Artist creates metadata JSON
Upload : Store on IPFS/Arweave/server
Mint : Smart contract points to metadata URI
Display : Marketplaces fetch and show metadata
Verify : Users can check metadata authenticity
Attributes and Traits
Trait Types
Visual: Background, clothing, accessories
Stats: Power, speed, intelligence
Rarity: Common, rare, legendary
Special: Edition number, artist signature
Rarity Calculation
Rarity Score = 1 / (Number with trait / Total supply)
Copy link
Metadata stored on centralized server
Project abandons, deletes files
NFT shows broken image
Always check storage method
Frozen vs Changeable
Frozen: Can't be changed (good)
Changeable: Team can update (risky)
Check contract for mutability
IPFS Pinning
IPFS content needs pinning
If unpinned, can become unavailable
Use pinning services (Pinata, Infura)
Click "Details" tab
Find "Token ID"
View contract on Etherscan
Check tokenURI function
Verify IPFS hash matches
IPFS : Check hash directly
Etherscan : View contract metadata
Rarity.tools : Analyze traits
Traitsniper : Real-time rarity
Best Practices
For Creators
Use IPFS or Arweave (decentralized)
Freeze metadata after mint
Include all relevant attributes
Test on testnet first
Document metadata structure
For Buyers
Check where metadata stored
Prefer on-chain or IPFS
Verify immutability
Check backup on Arweave
Research project reputation
Dynamic NFTs
Metadata can change based on conditions
Game items that level up
Art that evolves over time
Requires oracle or external trigger
Revealed after mint
Prevents sniping rare traits
Common in blind mint
Revealed via metadata update
NFTs containing other NFTs
Loot bags with items
Requires special handling