Variants — empty state.
The first-run state of Collection › Variants when the collection has no variants on any token. Its job is to explain what a variant is, because most creators will meet the word here first. Source: Phase2/Composition Template System/token-variant-actions-spec.md (model, Original Token, reached-from topology) and Phase1/token-system-design.md (variant data model, default-variant gate, V1 mints the default only).
Variants.
Every variant in this collection, and the optional action templates that trigger them.
No variants yet.
A variant is another version of a token — a different name and a different asset. Everything else stays exactly the same: the same token, the same copy, the same issue number, the same rarity.
One token, more than one version.
A sealed wallet that can be opened. A relic that can be forged. The holder still owns the same single copy — it just becomes a different version of itself.
Every token already has one
The token's own name and asset are its Original Token — the default version. Only the Original Token is minted, so a variant never costs extra supply.
Variants are reached, not bought
Each variant says which version it is reached from and what triggers the change. The holder runs it after mint — opening, forging, revealing.
Added on the token, listed here
Open any token and use its Variants tab to add one. This page then lists every variant in the collection, so you can review them in one place.
Variants are optional. If your tokens stay exactly as they were minted, there is nothing to do here. If you do add them, remember they lock when the token goes Live — a version you might want later has to exist before then.
Variants.
Every variant in this collection, and the optional action templates that trigger them.
No action templates.
An action template is reusable wording for the button a holder taps to change a variant — Open, Gild, Forge — plus the warning shown before it happens. Worth creating when several tokens share the same path; a one-off trigger is fine for a single token.
Variants.
Every variant in this collection, and the optional action templates that trigger them.
No variants yet.
A variant is another version of a token — a different name and a different asset. Everything else stays exactly the same: the same token, the same copy, the same issue number, the same rarity.
One token, more than one version.
Every token already has one
The token's own name and asset are its Original Token. Only that version is minted.
Variants are reached, not bought
Each one says what it is reached from and what triggers it. The holder runs it after mint.
Added on the token, listed here
Use a token's Variants tab to add one. This page lists them all.
| Slot | Copy | Why it says that |
|---|---|---|
| Hero title | No variants yet. | Plain first-run state; the word "yet" keeps it neutral rather than an error. |
| Hero sub | A variant is another version of a token — a different name and a different asset. Everything else stays exactly the same: the same token, the same copy, the same issue number, the same rarity. | A transition changes only variant, plus the name and asset the holder sees; it never touches token id, ownership, copy identity, issue number or the frozen sale policy. Score and rarity are definition-level. |
| Hero CTA | Go to tokens · How variants work | The collection page is browse-only — variants are authored on the token. A "Create variant" button here would lead nowhere. |
| Diagram caption | Same token · same copy · same issue number · same rarity — all the way across | Same rule as the hero sub, shown rather than claimed. |
| Rule 01 | The token's own name and asset are its Original Token — the default version. Only the Original Token is minted, so a variant never costs extra supply. | The Original Token is always the default_variant; V1 mints the default only, and variants share one supply cap — they never fork rarity or add units. |
| Rule 02 | Each variant says which version it is reached from and what triggers the change. The holder runs it after mint — opening, forging, revealing. | Topology is a property of the target variant: each declares its own from_variant and trigger. Holder-run, post-mint. |
| Rule 03 | Open any token and use its Variants tab to add one. This page then lists every variant in the collection. | Authoring lives on the token; this page is the read-only catalog. The Original Token is not listed here — it is the token, not a variant of it. |
| Closing note | Variants are optional… they lock when the token goes Live — a version you might want later has to exist before then. | Variant definitions lock at Live, and the full set is predeclared — nothing can be invented at runtime. |
| Actions tab | An action template is reusable wording for the button a holder taps… a one-off trigger is fine for a single token. | Templates carry button wording and warning text only; topology never lives in a project-level preset. |