five steps · you pay the deploy gas · nothing is stored by us
The payment reaches your wallet as each token is minted.
Just the handle. We build the link ourselves.
Must start with https://.
Both are shown on your collection page and marked unverified. Anyone clicking them from our site sees a warning first. We do not check where your links go.
What you earn every time someone resells one of your NFTs. Written into the contract in the ERC-2981 standard so marketplaces can read it. Each marketplace decides for itself whether to pay it. This sets the number, it cannot force anyone to honour it.
Defaults to the wallet that deploys the collection.
Fixed at deploy. It can never be increased.
0 means no limit.
Leave empty and minting is open to everyone.
The list is published as a single Merkle root, so it is fixed at deploy. You can drop the allowlist later and go public, but you can never quietly add a wallet to a list people have already seen. There is no function for it.
Only tokens from the official Robinhood registry. Counterfeit contracts copy these names exactly, so the address, not the symbol, is what we check.
-
Paid straight to your wallet on every mint. We never hold it. The 7% applies to the primary mint only. Resales are yours.
Upload your layers once (background, body, eyes, hat) and the contract builds every token from them. Forty pieces can dress five thousand tokens. Nothing is hosted anywhere: no file, no gateway, no link to rot. Only collections that do this get the ✓ badge.
viewBox. 1000 × 1000 is a good default. We warn you if files disagree.02-object/barrel.svg becomes
the “Barrel” trait of the “02 Object” layer. Numbers in front are stripped.font-family="A" and you get the
collection's built-in display face, embedded in every token.You wrote the art as a contract and deployed it yourself. Generative code, a pixel engine, anything. We just call it. This keeps the ✓ badge, because the art still lives on chain. For people who write Solidity; if that is not you, use the layers tab.
Must implement tokenURI(uint256 tokenId, uint256 artIndex).
Before the badge is granted we call your renderer once and read what comes back. It has to
be a self-contained data: URI. If it returns an ipfs:// or
https:// link, the art is not on chain and the badge is refused.
You host the art yourself and give us a CID. This accepts any art, including large raster images that could never fit on chain, but it does not get the ✓ badge, because we cannot promise it will still be there next year.
A folder containing 1.json … N.json. Paste the CID you already pinned.
We do not pin this. If you stop pinning it, your art goes offline and your collection shows as broken, including on OpenSea.
The banner shown above your collection on marketplaces. It is stored inside your contract, not on a server, so it cannot go offline. An SVG goes in as it is and stays sharp at any size; a photo is shrunk to fit. Leave it empty and your own first artwork is used.
Shown by every token until you reveal. Without one they show nothing at all.
Computed from your layers and written in at deploy, before the first mint, so buyers can prove the art was never swapped. Nothing for you to work out.
Priced from the chain, not typed in here.
Tick all three boxes and connect a wallet on chain 4663.
A deploy is several transactions, and any of them can be interrupted. If the collection was created but its art never made it on chain, paste the address here and the art steps run on their own. Nothing new is deployed and no second collection appears.