Collections — states & stages.
The collections index inside a project. A collection is your token policy boundary — supply, attributes, rarity, vendors. Populated with the add-card and status-badged collection cards, plus the empty state.
Collections.
A collection is your token policy boundary — supply, attributes, rarity, vendors.
Collections.
A collection is your token policy boundary — supply, attributes, rarity, vendors.
Your first collection.
A collection is the policy boundary for a set of tokens. It owns supply, attribute schema, rarity, vendor defaults, and the rules buyers can trust.
Project → Collections → Tokens.
Your project owns one or more collections. Each collection sets policy — supply caps, attribute schema, rarity, vendor defaults — that all its tokens inherit. Tokens are minted from generator exports or uploaded manually, and they show up under the collection forever.
Collections move through Draft → Review → Live. Live tightens what you can change so your buyers can trust the rules they bought into.
Policy at the collection level. Tokens inherit it.
Set the rules once
Supply caps, transfer/sale guards, attribute schema, rarity policy — defined once, enforced for every token in the collection.
Bring tokens in
From a generator export (with locked provenance) or manual uploads. Generator-exported collections lock to one generator source.
Go Live with confidence
Review validates everything is ready — rarity, supply, attribute values. After Live, core policy stays read-only.