Toko · Consistency reference
Vendors — Creation.
The create-a-vendor wizard for Market vendors — Type → Storefront → Lifecycle → Inventory → Costs & rules → Revenue → Summary — plus its modals, empty states, and the Draft → Review → Live stage transitions. The running/management side (vendor list, detail, lifecycle controls, runtime states) lives in vendor-management-states-gallery; gacha-only states live in gacha-vendor-states-gallery.
03Create — vendor typeStep 1 of the create stepper — the sale mechanism. Market is the only type available at launch and is collection-agnostic: it can sell tokens from one or several of your collections (no single/multi toggle — its inventory just spans whatever collections you stage). The price-override types — Gacha and Tombola — are single-collection (one draw price + one weighted pool only make sense within one rarity system) and stay disabled for now. Whatever collections a vendor is created with become its fixed set — it can only ever hold tokens from those. Cards use the gallery's own selection convention (strong border + hairline ring). The stepper rail replaces a redundant page header on working steps (style-guide rule).
Project · New vendor
1Type
2Storefront
3Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Choose a vendor type
This sets how the vendor distributes tokens and can't be changed later — the rest of setup adapts to your choice.
🎁
Gacha Coming later
Randomised draw from a weighted prize pool with computable odds and a reveal moment. Single collection.
🎟️
Tombola Coming later
Raffle-style draw where every ticket wins from a graded pool. Single collection.
🏛️
Market RWA Coming later
Fixed-price market for real-world assets. The vendor type set is open-ended — more may be added over time.
04Create — storefrontStep 2: the public presentation a collector sees on Launchpad — name, blurb, media, and the claim CTA label.
Project · New vendor
✓Type
2Storefront
3Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Customise your storefront
Editable on LiveHow buyers see this vendor on its public page and in Launchpad.
Square thumbnail (min 512×512) and a wide banner — same as the collection storefront.
05Create — lifecycle policyStep 3: how the vendor starts and ends. Activation (open immediately / start manually / schedule), control mode (autonomous vs admin-controlled with an earliest-stop), and what happens to unclaimed inventory when it stops.
Project · New vendor
✓Type
✓Storefront
3Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Lifecycle policy
Locks on Live1Activation — how it opens
Start manually
You press Start once it's Live and stocked.
Open immediately
Runs as soon as it's Live and has inventory.
Schedule
Starts automatically at a set date/time.
2Control mode — how it runs
Autonomous
Runs until sold out or you stop it.
Admin controlled
Supports an earliest-stop time — set a date the vendor can't be stopped before. The date field appears here when this option is selected.
3When it stops — unclaimed inventory…
Returns to the collection
Unclaimed copies go back to held inventory.
Is burned
Unclaimed copies are permanently destroyed.
06Create — inventoryStep 4: choose how stock can change (locked / additive / flexible) and allocate minted copies from the collection's held inventory into the vendor. Inventory is backed by minted tokens, never draft definitions.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Inventory policy
Locks on LiveAdditive — You can add new inventory while the vendor is running.
Add inventory
Editable on Live · additiveMove minted tokens from Spring Foxes, Night Market + Winter Tales into this vendor. Browse, filter and bulk-pick in the inventory manager — built for 10,000+ tokens with pagination. Rarity is shown by the card border.
184 tokens staged
🏮
🎭
🧧
×6🎆
🏮
🦊
🍜
🦊
×3🏮
🎐
🐉
🥮
🏮
🏮
×4🎏
🪭
🎇
🧨
For a Gacha vendor this step is the prize pool instead — same cards, plus weight & odds per prize.
Staging moves these copies into the vendor's inventory account — they leave the collection-held lists until claimed or returned. A vendor can mix tokens from any of the project's collections.
Un-staging a token uses the same per-card ✕ and the same confirm modal as the running vendor's Inventory tab — see vendor-management-states-gallery, frames 12 and 12 ·. A staged token is never removed on the click itself, here or there.
06 ·Inventory — locked policy (stock final on Live)How a Locked inventory vendor is set up. Unlike additive/flexible, a Locked policy means the staged quantity is final once the vendor goes Live — no top-ups or pull-backs afterwards. The Add inventory card therefore reads "Locks on Live" (not "Editable on Live"), and a warning makes clear you must stage the exact stock now.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Inventory policy
Locks on LiveLocked — The vendor's inventory cannot be adjusted once it starts running.
Add inventory
Stock locks on LiveThis vendor's stock is final once it goes Live. With a Locked policy you can't add or remove copies after launch — stage the exact quantity you want to sell now. Change the policy to Additive or Flexible if you need to top up later.
120 tokens staged
🏮
🎭
🧧
×6🎆
🦊
🦊
×306 ·Inventory policy — three statesThe compact policy control in each of its three selections. The segmented control sets the policy and the caption beneath swaps to describe the active choice, keeping the alternatives visible in muted text.
Inventory policy
Additive — You can add new inventory while the vendor is running.
Inventory policy
Flexible — You can add and remove items from the vendor's inventory while it is running.
Inventory policy
Locked — The vendor's inventory cannot be adjusted once it starts running.
06 ·Inventory — first load (no tokens staged)What the step looks like before anything is added. Policy can still be chosen, but the Add inventory section shows a compact, no-hero empty (matching the rarity gallery's "No tokens to assign" pattern) — a dashed panel, one line of guidance, and the primary "+ Add tokens" action that opens the picker modal. No pagination bar until there's stock to page through.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
Inventory policy
Locks on LiveAdditive — You can add new inventory while the vendor is running.
Add inventory
Editable on Live · additiveMove minted tokens that a collection holds into this vendor. Nothing's staged yet.
No inventory staged yet
Pick minted copies from any of the project's collections to stock this vendor. Only minted tokens a collection currently holds can be staged — if a collection has none, mint copies first.
Staging moves copies into the vendor's inventory account — they leave the collection-held lists until claimed or returned. A vendor can mix tokens from any of the project's collections.
06 ·Add tokens modal — minted tokens availableOpened from "+ Add tokens". Pick a source collection, then multi-select from the minted copies the collection holds — select-all on the page, per-card checkboxes, and pagination for large collections. Only minted, collection-held tokens appear; unminted definitions and externally-held copies can't be staged. The primary button counts the selection.
Add tokens to Spring Launch
Move minted tokens held by a collection in Vault One into this vendor. Only minted copies the collection currently holds can be added — unminted definitions and externally-held tokens can't.
3 of 620
🎭
🏮
🎭
🎆
🎆
🏮
🏮
🏮
🧧
×4🏮
🎭
🎆
🥮
🏮
🪭
🎭
🎇
🧨
Showing 1–18 of 620 held
06 ·Add tokens modal — no minted tokensSame modal when the chosen collection holds no minted tokens to stage — reuses the "no minted tokens" empty from Minted token management. The action stays disabled until a collection with held inventory is chosen or more copies are minted.
Add tokens to Spring Launch
Move minted tokens held by a collection in Vault One into this vendor. Only minted copies the collection currently holds can be added — unminted definitions and externally-held tokens can't.
0 of 0
No minted tokens to add
Only minted copies the collection holds can be staged into a vendor. Winter Tales holds no minted tokens yet — mint some, or pick another collection.
07Create — costs & rules · as loaded (all from defaults)Step 5, on first load. Costs & rules are organised per collection in a concertina — each shows that collection's own tiers: Weighted (fixed set), Tiered (custom names), or a single row for Uniform. Every tier is pre-filled from that collection's Collection defaults (the "From collection defaults" tag) — cost + requirements copied in (Restrictions and Rewards are V2) — so nothing is empty. Editing a tier here overrides the copied default for this vendor only. Each row only offers "Edit" here — "Reset to default" appears once a tier has been overridden (next frame). "Edit" opens the requirements editor (modals, shown below).
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
5Costs & rules
6Revenue
7Summary
Market requires a cost on every tier. Every tier must select a cost — free, or one of Toko's accepted currencies (ICP · ckBTC · ckETH · ckUSDC · ckUSDT · ckSOL · $TOKO · $DKP) — or the vendor can't go Live ("free" is an explicit choice, copied from the collection defaults). Costs & rules are set per collection — each collection brings its own tiers (even two Tiered collections can differ), and a Uniform collection has a single cost for the whole collection.
Every requirement narrows your audience. Requirements on a tier are additive (AND) — the more you add, the fewer collectors qualify to claim it. A tier with no requirements is open to everyone.
Costs & rules lock on Live
Spring FoxesWeightedFrom collection defaults
CommonFreeNone
Uncommon3 ICPWhitelist
Rare8 ICPWhitelist+Whitelist
Night MarketTieredFrom collection defaults
Patron2 ICPNone
Merchant5 ICPWhitelist
Founder25 ckUSDCWhitelist
Custom tier names come from this collection's Tiered rarity — they won't match another collection's tiers. Each tier sets its own cost token — here Founder is priced in ckUSDC rather than ICP.
Winter TalesUniformFrom collection defaults
All tokens4 ICPNone
Uniform collections have no tiers — set one cost & rule for the whole collection. Costs stay per collection so you can add tokens from a non-uniform collection later, each with its own tiers.
07 ·Costs & rules — some overriddenAfter editing a few tiers away from their defaults. Overridden tiers show an Edited badge and gain a "Reset to default" action; untouched tiers still only offer "Edit". A collection's head tag flips from "From collection defaults" to "Edited" when any of its tiers differ. Here Spring Foxes (Rare) and Winter Tales are edited; Night Market is untouched.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
5Costs & rules
6Revenue
7Summary
Spring FoxesWeightedEdited
CommonFreeNone
Uncommon3 ICPWhitelist
Rare12 ICPWhitelist+WhitelistEdited
Night MarketTieredFrom collection defaults
Patron2 ICPNone
Merchant5 ICPWhitelist
Founder25 ckUSDCWhitelist
Winter TalesUniformEdited
All tokens6 ICPWhitelistEdited
07 ·Costs & rules — no inventory yetWhen the vendor has no inventory, there are no collections to price, so this step has nothing to configure. You can still continue setting up — but a warning makes clear that inventory must be added before the vendor can go Live, or there'll be nothing to sell. Continue stays enabled; the go-Live gate is enforced later at Review.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
4Inventory
5Costs & rules
6Revenue
7Summary
No inventory yet — nothing to sell. Costs & rules are set per collection, drawn from the tokens you stage in Inventory. You can finish setting up and save as a draft, but the vendor can't go Live until you add inventory — without it there's nothing for collectors to claim.
Costs & rules
No collections
Add inventory to set costs & rules
This vendor has no inventory, so there are no collections to price here yet. Stage some minted tokens in the Inventory step and each of their collections will appear here, ready to price.
07 ·Requirement editor — accordionsOpened from "Edit" on a tier — the same editor concepts as the collection defaults (Cost · Requirements · Restrictions · Rewards), pre-filled with the copied default. Claim cost sits at the top (free, or an accepted currency); each requirement type is its own accordion. Requirements combine with AND — more gates means fewer eligible collectors, and when the stake gates ship a tier can carry an NNS and an SNS gate (ANDed, one of each). Whitelists are one gate, not many: selecting several lists merges them into a single de-duplicated eligible list — a collector needs to appear on any one of them, never all. Authorable in V1: whitelists + the two stake gates (ratified 2026-07-22 — full editor states in the stake-gates gallery; the SNS editor caps at one row). Holds-tokens-from-a-collection remains a disabled teaser — front-end V2, backend schema ships in V1 — as are Restrictions and Rewards. Promo / redemption codes aren't here — they're project-level code sets (future).
Edit · Spring Foxes · Rare
Pick Free or one of Toko's accepted currencies — ICP, ckBTC, ckETH, ckUSDC, ckUSDT, ckSOL, $TOKO, $DKP. No custom canisters.
Requirements combine with AND. A collector must satisfy every active requirement below — the more you add, the fewer people can claim this tier. Whitelists count as a single requirement: selected lists merge into one eligible list, so a collector only needs to appear on one of them.
Whitelists2 selected
Spring OG420 addressesLive
Allowlist 21,200 addressesLive
Founders88 addressesLive
Only the project's Live whitelists appear here — Draft and Review lists aren't shown. Add as many as you need — they merge into one eligible list, so a collector only needs to appear on one; manage them in Project Studio.
Has a stake — NNS (ICP neuron)None
Has a stake — SNS (ICRC-1 neuron)None
Holds tokens from a collectionComing soon
Maximum claims per humanComing soon
Accepted-currency payoutComing soon
07 ·Requirement editor — default open / closedThe same editor when only some requirements are set. An accordion with a selection opens on load (Whitelists); the stake gates are active but unset here (“None”); Holds tokens from a collection, Restrictions and Rewards stay disabled (coming soon).
Edit · Spring Foxes · Uncommon
Pick from Toko's accepted currencies — no canister IDs.
Whitelists1 selected
Spring OG420 addressesLive
Allowlist 21,200 addressesLive
Founders88 addressesLive
Has a stake — NNS (ICP neuron)None
Has a stake — SNS (ICRC-1 neuron)None
Holds tokens from a collectionComing soon
Maximum claims per humanComing soon
Accepted-currency payoutComing soon
Design note (not UI) — explore: project-level SNS DAOsThe SNS stake gate (front-end V2) takes a custom SNS governance canister by ID, entered at the point of use and cached in this vendor's dropdown. Worth exploring before build: persist SNS DAOs at the project level — validated once, then reusable across every vendor and tier. (Claim cost is no longer a place for custom canisters — costs use Toko's fixed accepted currencies only: ICP, ckBTC, ckETH, ckUSDC, ckUSDT, ckSOL, $TOKO, $DKP.) SNS governance canisters resolve to a DAO name, so resolved entries + labels can be stored on the project and refreshed. Flagged on the grey per the style guide.
07 ·Cost picker — three statesThe claim-cost control. A cost type must be chosen from Toko's accepted currencies — Free claim (no amount), or an amount priced in ICP, ckBTC, ckETH, ckUSDC, ckUSDT, ckSOL, $TOKO or $DKP. There are no custom / arbitrary tokens in V1.
One of Toko's accepted currencies — ICP, ckBTC, ckETH, ckUSDC, ckUSDT, ckSOL, $TOKO, $DKP. No custom tokens.
Free is an explicit choice — no amount or currency shown.
07 ·SNS stake gate — custom canister states (front-end V2 reference)V2 reference — this gate is a disabled teaser in V1 (backend schema ships in V1). How the SNS stake accordion behaves once it ships, when "Custom — add governance canister…" is chosen. Resolved: a valid governance canister ID resolves to the DAO name and is added to the vendor's list. Error: an ID that doesn't resolve is flagged inline and blocks save. (Picking a common SNS DAO from the list — e.g. Dragginz — needs no canister ID.)
SNS stake gate · custom · resolved
V2 referenceResolved · Catalyze SNS — added to this vendor's list
CAT
SNS stake gate · custom · error
Won't saveNo SNS found at this canister ID.
The tier can't be saved while the canister ID is unresolved — fix or remove it.
08Create — revenue (select two presets: Claim + Sale)Step 6: revenue is set by project-level revenue presets — a vendor must select two, one of each kind, and there's no free-style split editing here. The Claim preset splits the primary claim proceeds; the Sale preset is the secondary resale split (royalties ≤ 3% total, no Toko burn, no referral) that gets stamped onto every copy at claim as its immutable locked_sale_split. Both are copied onto the vendor and shown read-only, and both lock on Live — the vendor locks the price and the royalties that apply. (The claim split includes the preset's Toko burn — a min-1% share of each claim, converted to $TOKO and burned to build the project's reputation; it's authored in the preset, shown read-only here.) Presets aren't created from this step — they're created and edited in Project · Revenue presets (Claim · Sale tabs). Selecting both is required to continue. The project's default preset of each kind is pre-selected (the creator can change either). Two Sale-side behaviours the UI only implies: a fixed-period royalty's taper clock runs per copy from that copy's own claim timestamp (not the vendor's start), so copies of the same token distributed by different vendors can carry different resale splits; and the seller's 1–10% referral fee is set per listing on the marketplace, never in a preset.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
✓Costs & rules
6Revenue
7Summary
Claim revenue preset
requiredPrimary · claimsHow claim proceeds are split.
Creator · 83.5%
Royalties · 14%
Toko burn · 2.5%
From the preset Read-onlyLocks on Live
Toko burn2.5%
Community Treasury8% · forever
Ocean Cleanup charity6% · taper to 0 · 90 days
Royalties total14% / 20% max
To change fees or royalties, edit the preset in Project · Revenue presets.
Sale revenue preset
requiredSecondary · resalesHow resale proceeds are split. Fixed onto each copy at claim — it can't be changed for that copy afterwards.
Seller · 97%
Royalties · 3%
From the preset Read-onlyLocks on Live
Aviary Labs creator2% · forever
Community Treasury1% · taper to 0 · 12 months
Royalties total3% / 3% max
To change these royalties, edit the preset in Project · Revenue presets.
08 ·Revenue — presets not selected (required)A vendor must use both a Claim preset and a Sale preset. Until each is selected its split is empty and Continue is disabled — the blocking reason sits on the card that owns it, matching the inventory step (no helper text in the footer). You select existing Live presets — presets are created in Project · Revenue presets (Claim · Sale tabs) and must be Live before they appear here, not from this step. Shown here with neither chosen; the same treatment applies when only one is missing. There is deliberately no implicit fallback for a vendored copy — the platform standing default (1% to the project treasury) covers never-vendored copies only, so royalty-free resale has to be chosen explicitly via a 0% preset.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
✓Costs & rules
6Revenue
7Summary
Claim revenue preset
requiredPrimary · claims
Select a Claim preset
How claim proceeds are split. Defined by a project-level preset and copied onto this vendor. Choose a Live Claim preset to continue.
A Claim preset is required. The vendor can't continue until one is selected. No Live Claim presets yet? Create one in Project · Revenue presets — it must reach Live before it appears here.
Sale revenue preset
requiredSecondary · resales
Select a Sale preset
The resale split frozen onto every copy claimed from this vendor. Royalties only, ≤ 3% total. Choose a Live Sale preset to continue.
A Sale preset is required. The vendor can't continue until one is selected — for royalty-free resales, select a 0% Sale preset. No Live Sale presets yet? Create one on the Sale tab of Project · Revenue presets — it must reach Live before it appears here.
09SummaryStep 7: a summary of every section with a validation check. From here you Save as Draft or Submit to Review — Submit to Review is the required step before a vendor can go Live (you Set Live from the Review stage, not here). Submitting requires all required fields to validate; the tokens themselves are checked individually at their own go-live.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
✓Costs & rules
✓Revenue
7Summary
Spring Launch · summary
Ready to go LiveTypeMarket
StorefrontSpring Launch · "Claim a Fox"
ActivationStart manually
Control modeAdmin controlled · earliest stop 12 Jul 2026
When it stopsReturn unclaimed to collection
Inventory policyAdditive · locks on Live
Inventory420 copies · 3 collections
Costs & rulesSet per collection (3)
Revenue · claimPreset · Standard Claim
Revenue · salePreset · Standard Sale · 3% royalties
All required fields valid. Submit to Review to lock the config for a final check — you then Set Live from the Review stage (Draft → Review → Live; you can return to Draft to edit). Inventory policy locks on Live; the inventory quantity can still change afterwards (additive allows top-ups).
09 ·Summary — validation errorsThe summary when things don't validate. Every blocking issue is listed with a jump-to-fix link, and Submit to Review is disabled until all clear; Save as Draft stays available. This shows the full set of things that can block progressing toward go-Live. Note costs & rules can't appear as a blocker here — a cost is required to save every tier (pre-filled from the collection defaults) and custom ledgers / SNS canisters are validated on entry, so those failures are caught before this step.
Project · New vendor
✓Type
✓Storefront
✓Lifecycle
✓Inventory
✓Costs & rules
✓Revenue
7Summary
Spring Launch · summary
Can't submit · 3 issuesFix these before this vendor can go Live. Each issue links to the step that owns it. You can still save everything as a Draft.
Storefront — vendor name is required
A public vendor must have a name before it can publish to Launchpad.
Lifecycle — earliest-stop date is in the past
Admin-controlled vendors need an earliest-stop date in the future.
Inventory — no tokens staged
A vendor can't go Live with nothing to sell. Stage minted tokens first.
Costs & rules — valid
Costs & rules can't fail here — a cost is required to save each tier (pre-filled from collection defaults), and custom ledgers/SNS canisters are validated on entry, so an unresolved one can't be added.
Revenue — valid
A Live Claim preset and a Live Sale preset are both selected and copied onto the vendor (no free-style edits). A vendor can't be submitted to Review while either is missing — the Sale preset is what each claimed copy is stamped with as its resale split.
Type & storefront media — valid
Market type set; thumbnail and banner present.
09 ·Stage: Review — read-only, then go LiveA vendor that's been submitted to Review. The config is locked and read-only — only aesthetic storefront fields stay editable (name, tagline, media, claim label). From here you Set Live to publish to Launchpad, or Return to Draft to unlock and edit. (Draft → Review → Live; there's no separate approval gate.)
Project · Vendor
Spring Launch.
Market vendor · in Review. Configuration is locked for a final check — edit the storefront if needed, then set it Live.
State
ReviewSetup
Locked for review. Costs & rules, lifecycle, inventory policy and revenue are read-only at this stage. Only the storefront (aesthetic) fields can still be edited. Return to Draft to change anything else.
Configuration
Locked at ReviewStorefrontSpring Launch · "Claim a Fox" Editable
ActivationStart manually
Control modeAdmin controlled · earliest stop 12 Jul 2026
When it stopsReturn unclaimed to collection
Inventory policyAdditive
Inventory420 copies · 3 collections
Costs & rulesSet per collection (3)
Revenue · claimPreset · Standard Claim · 14% royalties
Revenue · salePreset · Standard Sale · 3% royalties
Stage
10Storefront media · cycle check (balance OK)Saving a vendor thumbnail or banner (Create · storefront, step 2) stores it in blob storage, funded from project cycles. Before it saves, Toko estimates the cost and checks the balance — the same guard used for every upload (see the Cycles & uploads gallery). With headroom, it saves normally.
Upload assets
spring-launch-banner.png staged · 2.8 MB · uploaded & held
Estimated cost
~0.03 T cycles
Project balance
2.040 T
After upload
~2.01 T
Enough cycles to store this image and keep your reserve. Toko moves project cycles into blob storage automatically.
11Storefront media · low balanceThe estimate exceeds the balance. The image stays staged — nothing is discarded — and the primary action becomes Top up & upload.
Upload assets
spring-launch-banner.png staged · 2.8 MB · uploaded & held
Estimated cost
~0.03 T cycles
Project balance
0.010 T
Shortfall
~0.02 T + reserve
Not quite enough cycles to store this image. It stays staged — top up and it saves straight away. Nothing is lost if you top up now.
12Top up to continue · image stagedThe inline top-up. The staged image is shown at the top so it's clear nothing was cancelled; once cycles land in blob storage, it saves automatically.
Top up to continue upload
spring-launch-banner.png staged · 2.8 MB · ready to save
This upload (est.)~0.03 T
Project balance0.010 T
Recommended top-up (cost + reserve)1.000 T
Top up amount
T cycles · ≈ 0.30 ICP
from your wallet to the project canister
Cycles are sent to the project canister; Toko moves what's needed into blob storage. After it lands, the staged image saves automatically.