The Launchpad, at a glance

A place to launch and mint NFT collections on Robinhood Chain whose art lives entirely on chain. When a piece mints, its image is written into the collection's own contract; when a wallet or marketplace asks for the piece, the contract builds the whole answer (name, picture, traits) from what it holds. There is no IPFS, no server, no file that could go missing. If Robinhood Chain is up, the art is there.

Collections are standard ERC-721s: they show up in wallets and trade on OpenSea. Each one is its own contract, a copy of a verified template made by a verified factory, owned by its creator. FOMO can't change a collection after it launches, and neither can the creator change its art.

Every piece can also do two things most NFTs can't: hold a wallet of its own, and be an AI agent. Both belong to whoever holds the piece, and both go with it when it's sold. More on that under “Every piece”.

Anyone with a wallet can launch one, from the Create page, in four steps. You sign in with your wallet (a free signature, nothing sent) and your draft is saved as you go.

1. Details. Name, symbol, description, links, the wallet mint money goes to, royalties on resales (0–10%) and whether to enforce them (ERC-721C: only marketplaces that pay creator fees can trade the pieces; holders can always send their own), and when pieces show their art: at mint, or after a reveal.
2. Art. Drop in your images (one a token, numbered) and their traits (a CSV or JSON). The studio compresses them in your browser, AVIF by default, to a size you set: the smaller a piece, the less gas every minter pays to write it on chain. A piece up to about 93KB mints in one transaction; bigger pieces (up to about 345KB) go up in parts first. GIFs are kept exactly as uploaded, animation and all.
3. Phases. Up to eight: public or allow list (paste wallets, or build the list from holders of other collections), a price, a limit a wallet, a cap. Phases may overlap (a free allow list beside a paid public phase). A price may slide: one price at the phase's start, another at its end, moving second by second (falling, it's a Dutch auction). The mint opens within 10 days of launch and runs 10 days at most.
4. Review and launch. The art is uploaded and sealed into a fingerprint (a Merkle root) the contract holds for good, then your wallet deploys the collection: FOMO's launch fee plus about a cent of gas.

A minter picks a phase, pays its price plus FOMO's fee, and their own transaction writes the piece's image on chain, so they pay that gas too (the mint page shows the whole cost before the wallet opens). At mint, a piece is drawn at random from what's left (reveal later: the next one in line). A big piece takes a few transactions: its parts go up first and are held for the minter for 10 minutes.

• Sliding prices. The page shows the price right now and where it's heading. A mint pays the price of its block; pay more (the page does, for a rising price, to cover the minute the wallet takes) and the difference comes straight back in the same transaction.
• Allow lists. The contract checks a proof that your wallet is on the list; the page fetches it for you. Limits a wallet and phase caps are checked on chain too, so a mint that skips this site plays by the same rules.
• Reveal later. Every piece shows the placeholder until the mint is over. Then a random shift, taken from a block hash, decides which art each token shows, so no one can pick the rares. It can only happen once.

From the Create page (your collections), while it sells you can change phases (prices, times, limits, lists) within the 10-day window, mint from your reserve, and withdraw mint money to the payout wallet at any time. You can end the mint for good, fixing the supply at what has minted.

A reveal-later collection reveals once the mint is over (sold out, ended, or its last phase done). If you haven't revealed 3 days after that, anyone can, so a collection can never be left stuck on its placeholder. Unless you ticked “let anyone start the reveal”, only you can for those first 3 days.

Each piece has a page of its own (click a piece on its collection's mint page): its art and traits, who holds it, and three things it can be.

Its wallet

Every piece has an account of its own on chain (ERC-6551, through the same Tokenbound contracts used on other chains). Its address exists from day one and anyone can send ETH to it; one transaction, about half a cent, makes it active. It can hold ETH, tokens and other NFTs. Whoever holds the piece controls the wallet, and only they can send out of it. Sell the piece and the wallet, with everything in it, goes to the buyer.

Its agent

A piece can be registered as an AI agent in the ERC-8004 registry, the shared list agent apps read to find and trust agents. The holder presses one button (about a cent of gas); the registration is made through the chain's canonical binding contract (Unruggable Labs' ERC-8004 adapter, the one OpenSea reads), which keeps the agent entry forever and lets whoever holds the piece control it: its agent file (name, description, where to reach it), its metadata, and its wallet (set by signing a message with the wallet you want). Sell the piece and the agent goes with it. The registration can't be undone or moved.

The agent file starts as FOMO's, built live from the chain (the piece's art, holder, wallet and profile), so it's never stale; the holder can point it at a file of their own.

Its profile

On a collection launched with living metadata (below), the holder writes the piece's profile on chain: a context (who the agent is, in Markdown) and endpoints (web, MCP, A2A, and x402 for an agent that takes payments). Agents read it in one call. The creator can write a brief for the whole collection, which every piece's agent file carries until its holder writes a context of their own. It never appears in the token's metadata on marketplaces, so nothing a holder writes can break or spoof the piece there.

By default a collection is its art and traits as inscribed, for good. A creator may instead launch with living metadata: a small metadata contract of the collection's own (ERC-8048), chosen at launch and fixed from then on, with either or both of:

• Holder profiles. Each piece's holder writes its profile (above).
• Living traits. The creator can set traits after mint (levels, scores, seasons), on one piece or all of them; they join the piece's attributes on OpenSea, which refreshes them. Up to 32 trait names. The mint page and piece pages say so, so buyers know, and the creator can lock traits for good at any time. The art and the inscribed traits never change either way.

Launching

0.002 ETH, plus about a cent of gas to deploy the collection.

Minting

The phase's price (to the creator) plus FOMO's fee of 0.0005 ETH a piece, plus the gas to write the piece on chain (set by its size; the page shows it).

Royalties

What the creator set, 0–10%, paid by buyers on marketplaces that honour them; enforced on chain when the creator chose that.

A piece's wallet

About half a cent of gas to create. Sending in or out: ordinary gas.

Registering an agent

About a cent of gas. Setting its file or wallet: ordinary gas.

Changing a trait or profile

Ordinary gas, a fraction of a cent a piece.

All on Robinhood Chain (chain id 4663), all verified on Sourcify so the code you read is the code that runs. A collection launched with an earlier version keeps its own contract and keeps working; its mint page links it.

Drop factory v13

OnchainDropFactory13 0x0Abb64…0C2D the current one: v12's drop with four fees by kind, minters paying or the creator prepaying at launch

Collection contract v13

OnchainDrop12 0xBEb2dd…53D8 v12's code, deployed again by the v13 factory

Drop factory v12

OnchainDropFactory12 0x390a59…34bf v11 with a migration's claim window set at launch, 90 days at most

Collection contract v12

OnchainDrop12 0xcB3867…8c0c

Drop factory v11

OnchainDropFactory11 0xD13d82…F149 v10 plus migrations (an old collection re-issued to its holders, who claim) and video pieces

Collection contract v11

OnchainDrop11 0x977b1F…8a9E

Renderer v11

DropRenderer11 0x3Fec78…c566 v12 collections use it too

Drop factory v10

OnchainDropFactory10 0x6e4F14…64CE

Collection contract v10

OnchainDrop10 0xb03B1E…A9bb

Renderer v10

DropRenderer10 0x7fe5A0…e138

Metadata contract v10

DropMetadata10 0xEb76Fa…95D7 v11 collections use it too

Agent bindings (ERC-8217)

ERC-8004 Adapter 0x000000…5E18 the chain's canonical binding contract, by Unruggable Labs; what OpenSea reads

Agent bindings, earlier

FomoAgentBindings 0xC2730F…5A1a ours; a few pieces registered through it before the canonical contract was used

ERC-8004 registry

Identity Registry 0x8004A1…a432

ERC-6551 registry

Registry 0x000000…5758

Tokenbound account

Account v3 0x41C8f3…44eC

The standards, one line each

ERC-721

The NFT standard: wallets and marketplaces know how to show and trade the pieces.

ERC-721C

Creator-fee enforcement (Limit Break's transfer validator): only approved marketplaces, which pay creator fees, can move the pieces; holders can always send their own.

ERC-2981

Tells marketplaces the creator's royalty and where to send it.

ERC-4906

Tells marketplaces a piece's metadata changed, so they refresh it (used by living traits and the reveal).

EIP-1167

Each collection is a minimal copy (a clone) of the verified implementation, so launching costs about a cent.

SSTORE2

Images are stored as the code of small contracts, about three times cheaper than ordinary storage and read back in one copy.

ERC-6551

Token-bound accounts: a wallet owned by an NFT, controlled by whoever holds the NFT.

ERC-8004

Trustless agents: a registry where each AI agent is an NFT with a file describing it, plus a reputation registry.

ERC-8217

Binds an ERC-8004 agent to another NFT so that NFT's holder controls the agent. Pieces register through the chain's canonical binding contract, which is what OpenSea shows as a piece's onchain agent binding.

ERC-8048 / ERC-721T

On-chain key-value metadata per token, and the reserved keys an agent profile uses (context, endpoints, addresses).

Everything the pages show is readable without a key, as JSON. Writes are transactions to the contracts above, from a wallet.

llms.txt

/llms.txt

OpenAPI

/openapi.json

Collections

GET /api/launchpad

A collection

GET /api/drop/<collection>

Its state now

GET /api/drop/<collection>/state

Its mints

GET /api/drop/<collection>/activity

A piece

GET /api/piece/<collection>/<tokenId>

A piece's agent file

GET /api/agent/<collection>/<tokenId>

Can the creator change my piece's art?

No. Every image and its inscribed traits are checked against a fingerprint fixed at launch and stored as contract code. Only living traits, when the creator chose them at launch, can be added or changed, and the collection says so.

Can FOMO change a collection?

No. The factory has no switch over a launched collection; the renderer that builds its metadata is copied into it at launch and can't be changed by anyone. FOMO's only powers are the fees (capped in the contracts) and which marketplaces the royalty-enforcement list allows.

What if the creator disappears before the reveal?

Three days after the mint is over, anyone can reveal.

What happens to the wallet and the agent when I sell a piece?

They go with it: control follows whoever holds the piece, read live from the chain.

Why does a mint cost more than the price?

The minter's own transaction writes the image on chain; that gas is most of the cost for a big piece. The studio's compression settings and the mint page both show it ahead of time.

Which wallets work?

Any browser wallet on Robinhood Chain (MetaMask, Rabby, Coinbase Wallet and the like); the page adds the chain for you.