Warren NFT - On-Chain NFT Collection Deployment
Deploy complete NFT collections with permanent on-chain image storage on MegaETH mainnet.
Network: MegaETH Mainnet (Chain ID: 4326)
RPC: https://mainnet.megaeth.com/rpc
Explorer: https://megaeth.blockscout.com
How It Works
Your Images → SSTORE2 (on-chain) → WarrenContainer → WarrenLaunchedNFT
/images/1.png tokenURI renders
/images/2.png images on-chain
...
- Each image is deployed as a Page contract (fractal tree for larger files).
- All images are stored in a WarrenContainer NFT at
/images/1.png,/images/2.png, etc. - A WarrenLaunchedNFT contract is deployed referencing the container.
- Collection is registered for management and mint pages.
Setup (One Time)
cd {baseDir}
bash setup.sh
Prerequisites
1. Wallet + MegaETH ETH
Bridge ETH from Ethereum to MegaETH mainnet for gas.
Approximate cost:
- ~0.03 ETH for a small collection (around 10 images)
2. Genesis Access Requirement
The script checks in this order:
- Human Genesis Key (0xRabbitNeo)
- 0xRabbit.agent Key
- Auto-mint 0xRabbit.agent Key (free)
Default RABBIT_AGENT_ADDRESS: 0x3f0CAbd6AB0a318f67aAA7af5F774750ec2461f2 (override via env).
If you override or unset it, mint a human key:
Contract Addresses (Mainnet)
| Contract | Address |
|---|---|
| Genesis Key NFT (0xRabbitNeo) | 0x0d7BB250fc06f0073F0882E3Bf56728A948C5a88 |
| 0xRabbit.agent Key NFT | 0x3f0CAbd6AB0a318f67aAA7af5F774750ec2461f2 |
| WarrenContainer | 0x65179A9473865b55af0274348d39E87c1D3d5964 |
| WarrenContainerRenderer | 0xdC0c76832a6fF9F9db64686C7f04D7c0669366BB |
| Treasury/Relayer | 0xcea9d92ddb052e914ab665c6aaf1ff598d18c550 |
Environment Variables
| Variable | Required | Default | Purpose |
|---|---|---|---|
PRIVATE_KEY | Yes | — | Wallet private key for signing transactions |
RPC_URL | No | https://mainnet.megaeth.com/rpc | MegaETH RPC endpoint |
CHAIN_ID | No | 4326 | MegaETH mainnet chain ID |
GENESIS_KEY_ADDRESS | No | 0x0d7B...5a88 | Genesis Key NFT contract |
RABBIT_AGENT_ADDRESS | No | 0x3f0C...61f2 | 0xRabbit.agent NFT contract |
CONTAINER_ADDRESS | No | 0x6517...5964 | WarrenContainer contract |
RENDERER_ADDRESS | No | 0xdC0c...6BB | WarrenContainerRenderer contract |
TREASURY_ADDRESS | No | 0xcea9...8c550 | Treasury/relayer address |
REGISTER_API | No | https://thewarren.app/api/container-nfts | Collection registration endpoint (see Security) |
CHUNK_SIZE | No | 15000 | Bytes per chunk (15KB) |
GROUP_SIZE | No | 500 | Max addresses per tree node |
Deploy NFT Collection
Option 1: From Image Folder
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
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
| Option | Required | Default | Description |
|---|---|---|---|
--images-folder <path> | * | - | Folder with image files |
--generate-svg <count> | * | - | Generate random SVG art (1-256) |
--name <string> | Yes | - | Collection name |
--symbol <string> | Yes | - | Collection symbol (3-5 chars) |
--description <text> | No | Auto | Collection description |
--max-supply <number> | No | Image count | Maximum mintable NFTs |
--whitelist-price <eth> | No | 0 | Whitelist mint price in ETH |
--public-price <eth> | No | 0 | Public mint price in ETH |
--max-per-wallet <number> | No | 10 | Mint limit per wallet |
--royalty-bps <number> | No | 500 | Royalty (500 = 5%, max 1000 = 10%) |
* Either --images-folder or --generate-svg is required.
Output
NFT Collection Deployed!
NFT Contract: 0xABC...
Container ID: 15
Image Count: 10
Max Supply: 100
Public Price: 0 ETH (Free)
Management: https://thewarren.app/launchpad/0xABC.../
Mint Page: https://thewarren.app/launchpad/0xABC.../mint
Image Requirements
- Formats: PNG, JPG, JPEG, SVG, GIF, WebP
- Size: up to 500KB per image
- Count: 1-256 images per collection
- Naming: sequential or alphabetical
Example 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 Collection (100 SVGs)
cd {baseDir}
PRIVATE_KEY=0x... node deploy-nft.js --generate-svg 100 --name "Century" --symbol "C100" --max-per-wallet 3
Troubleshooting
"No ETH balance"
- Bridge ETH to MegaETH mainnet.
"No Genesis Key found and RABBIT_AGENT_ADDRESS is not configured"
- Set
RABBIT_AGENT_ADDRESS=0x3f0CAbd6AB0a318f67aAA7af5F774750ec2461f2, or mint human key athttps://thewarren.app/mint.
"Image exceeds 500KB"
- Resize or compress images.
"Too many images"
- Maximum 256 images per container.
DB registration warning
- Non-critical. Collection is still deployed on-chain.
Notes
- Mainnet content is permanent and immutable.
- You pay gas from your own wallet.
Security & Privacy
- No data exfiltration: Images are sent only as blockchain transactions to the configured RPC endpoint.
- PRIVATE_KEY handling: Used solely to sign transactions. Never logged, stored on disk, or transmitted to third parties.
- Network endpoints: Only the configured
RPC_URL(default:mainnet.megaeth.com/rpc) andREGISTER_API. - REGISTER_API: After on-chain deployment is complete, the script POSTs collection metadata (name, symbol, maxSupply, prices, NFT contract address, container ID) to
thewarren.app/api/container-nftsfor management page registration. This is optional and non-critical — the on-chain collection works without it. No images or private keys are sent. Override withREGISTER_APIenv var or set to empty to disable. - File access: Reads only files in the specified
--images-folder. No access outside that directory. - No telemetry: No analytics, tracking, or usage reporting.