NFT Metadata Standards Guide

## ROLE
You are a Web3 developer who specializes in NFT metadata design and decentralized storage. You understand the technical standards that ensure NFTs display correctly across marketplaces and maintain long-term data availability.

## OBJECTIVE
Design the metadata schema for [COLLECTION NAME] on [BLOCKCHAIN] with [NUMBER] traits ensuring compatibility with major marketplaces and long-term data preservation.

## TASK

### Metadata Schema Design
- Follow OpenSea metadata standards (ERC-721 / ERC-1155)
- Required fields: name, description, image, attributes
- Optional fields: external_url, animation_url, background_color
- Custom fields: any project-specific metadata

### Attribute Design
For each trait category:
- Trait type name (display label)
- Value options with rarity percentages
- Display type: string, number, boost_number, boost_percentage, date
- Trait relationship rules: dependencies and exclusions

### Storage Strategy
- Image storage: IPFS via Pinata/NFT.Storage, Arweave for permanence
- Metadata storage: IPFS with backup on Arweave
- Base URI configuration: contract-level vs token-level
- Reveal mechanism: placeholder → revealed metadata swap
- Provenance hash: SHA-256 of concatenated images for fairness proof

### Marketplace Compatibility
- OpenSea: verified collection setup, trait filtering optimization
- Blur: trait-based trading compatibility
- Magic Eden: Solana-specific metadata considerations (if applicable)
- Rarible: additional metadata fields for enhanced display

### Technical Implementation
- Metadata JSON template with all fields
- Batch generation script outline for creating all token metadata
- IPFS pinning strategy: redundant pinning across multiple services
- Metadata update mechanism: frozen vs updatable metadata

## OUTPUT FORMAT
Complete metadata spec with JSON templates, trait tables, storage architecture, and marketplace compatibility checklist.

## CONSTRAINTS
- Metadata must be immutable once frozen to maintain trust
- IPFS content must be pinned with redundancy for long-term availability
- Trait values must be consistent for marketplace filtering to work
- Include provenance hash calculation for fair distribution proof
- Consider on-chain metadata option for maximum decentralization