Warren NFT - On-Chain NFT Collection Deployment

Deploy complete NFT collections with permanent on-chain image storage on MegaETH testnet.

All images are stored using SSTORE2 bytecode storage in a WarrenContainer, and each collection gets its own NFT contract with minting support.

Network: MegaETH Testnet (Chain ID: 6343)

RPC: https://carrot.megaeth.com/rpc

Explorer: https://megaeth-testnet-v2.blockscout.com

How It Works

Your Images → SSTORE2 (on-chain) → WarrenContainer → WarrenLaunchedNFT
                                     /images/1.png     tokenURI renders
                                     /images/2.png     images on-chain
                                     ...

1. Each image is deployed as a Page contract (fractal tree for >15KB images)
2. All images are stored in a WarrenContainer NFT at /images/1.png, /images/2.png, etc.
3. A WarrenLaunchedNFT contract is deployed referencing the container
4. Minting is enabled and the collection is registered on megawarren.xyz

Setup (One Time)

cd {baseDir}
bash setup.sh

Get testnet ETH: https://docs.megaeth.com/faucet

Genesis Key NFT auto-mints during first deployment (free on testnet).

Deploy NFT Collection

Option 1: From Image Folder

Prepare a folder with numbered images:

my-art/
├── 1.png
├── 2.png
├── 3.png
└── ...

Deploy:

cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js \
  --images-folder ./my-art/ \
  --name "Cool Robots" \
  --symbol "ROBOT" \
  --description "100 unique robot NFTs on-chain" \
  --max-supply 100

Option 2: Auto-Generate SVG Art

Generate unique SVG art programmatically:

cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js \
  --generate-svg 10 \
  --name "Generative Art" \
  --symbol "GART" \
  --description "AI-generated on-chain art"

Full Configuration

PRIVATE_KEY=0x... node deploy-nft.js \
  --images-folder ./collection/ \
  --name "Cyber Punks" \
  --symbol "CPUNK" \
  --description "On-chain cyberpunk collection" \
  --max-supply 1000 \
  --whitelist-price 0.01 \
  --public-price 0.02 \
  --max-per-wallet 5 \
  --royalty-bps 500

CLI Options

\* Either --images-folder or --generate-svg is required.

Output

After deployment, you'll receive:

🎉 NFT Collection Deployed!
============================================================
NFT Contract:  0xABC...
Container ID:  15
Image Count:   10
Max Supply:    100
Public Price:  0 ETH (Free)

📋 Management: https://megawarren.xyz/launchpad/0xABC.../
🎨 Mint Page:  https://megawarren.xyz/launchpad/0xABC.../mint
============================================================

• Management Page: Change mint state, prices, airdrop, withdraw funds
• Mint Page: Public-facing page for minting your NFTs

Image Requirements

• Formats: PNG, JPG, JPEG, SVG, GIF, WebP
• Size: Up to 500KB per image
• Count: 1-256 images per collection
• Naming: Sequential (1.png, 2.png) or alphabetical (auto-numbered)
• Images >15KB are automatically split using fractal tree architecture

Gas Costs (Testnet)

Stress Test Workflows

Quick Test (3 SVGs)

cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js --generate-svg 3 --name "Quick Test" --symbol "QT"

Medium Test (20 SVGs)

cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js --generate-svg 20 --name "Art Collection" --symbol "ART" --public-price 0.001

Full Test (100 SVGs)

cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js --generate-svg 100 --name "Century" --symbol "C100" --max-per-wallet 3

Contract Addresses (Testnet)

Troubleshooting

"No ETH" → Get testnet ETH from https://docs.megaeth.com/faucet

"GenesisKeyRequired" → Genesis Key auto-mints. If failing, check balance > 0.001 ETH

"Image exceeds 500KB" → Resize or compress images before deployment

"Too many images" → Maximum 256 images per container (TypeRegistry limit)

"TooManyFiles" → Same as above, reduce image count

DB registration warning → Non-critical. Collection still works on-chain. Management/mint pages will load from on-chain data.