The collection sub-page where a creator sets the default claim rule every new vendor drawing from this collection starts with (then edits per vendor). It is tier-indexed (a default per rarity tier), auto-saves, and is required-valid before Review and frozen at Live. In V1 a rule is two things: a required cost (Free, or an accepted currency) and optional requirements (allowlist / hold / stake). Restrictions (claim limits) and Rewards (payouts) are V2. Mirrors sale-defaults-states-gallery. Source: Design Documentation/vendor-presets.md.
V1 scope: collection defaults carry only cost + requirements. Claim Restrictions (how often / how many — e.g. max per human) and Rewards (extra payout) are V2 — not yet configurable. Source: Design Documentation/vendor-presets.md.
Part A
The sale-defaults page
The sub-page itself: a per-tier table of the claim rule (cost + requirements), and the rule editor. Auto-saves; stage persistence lives on the collection bar, not here.
A1Collection defaults — setA collection with collection defaults in place. Each rarity tier has a cost plus optional requirements. This is a collection sub-page, so it auto-saves — no Save/Discard here; stage persistence (Submit to Review / Publish to Live) lives on the collection bar.
The default claim cost & requirements new vendors inherit. One default per rarity tier.
Draft
ⓘ
Collection defaults seed every new vendor that draws from this collection — vendors then edit per vendor. In V1 a rule is cost + requirements only; Restrictions (claim limits) and Rewards (payouts) are V2.
Per-tier defaults
tiered rarity · 3 tiers
◷ Locks on Live
TierClaim rule
PatronFree · On a whitelist
Keeper2 ICP
Founder4 ICP · On a whitelist
A2Rule editor — collection defaultOpened from "Edit rule" on a tier. A required cost (Free, or an accepted currency) plus optional requirements (whitelist / holds a token / has a stake), combined with AND. Restrictions (claim limits) and Rewards (payouts) are V2 and not shown here.
Claim rule · Founder
✕
Claim cost required — Free, or an accepted currency
Free
Anyone eligible can claim at no cost.
Priced
An amount in one of Toko's accepted currencies.
Requirements optional · combined with AND · none = anyone can claim
On a whitelist
Only principals on a Live whitelist may claim.
Holds a token
Must hold a token from a chosen collection.
Has a stake
Must have an active SNS / NNS stake.
Requirements gate eligibility, combined with AND. Frozen at Live. Restrictions & rewards are V2.
A4Collection defaults — not set yetA Draft collection before collection defaults are configured. Tiers exist (from the rarity system) but have no cost. The page is editable in any state, but the collection can't reach Review until every tier has a cost set (free is allowed).
Set a cost for each tier (free is allowed); requirements are optional. A cost is required before Review.
Part A note (not UI) — what isn't here
Collection defaults are the per-collection starting point for vendor claim rules — every new vendor drawing from this collection inherits them, then can edit per vendor. In V1 a rule is just cost + requirements. Restrictions (claim limits — e.g. max per human) and Rewards (extra payout on claim) are V2 — not yet configurable. Promo / redemption codes are project-level, not collection defaults.
Part B
Lifecycle & locking
Collection defaults follow the same Draft → Review → Live lifecycle as the collection's other core policy. Editable early, required-valid before Review, frozen at Live.
B1Draft — not yet valid (change required)Being set up. Founder has no cost set, so the collection can't be submitted to Review — every tier needs a cost (free is allowed). Everything is editable; each section carries a "Locks on Live" pill so the creator knows it'll freeze later.
Founder has no claim cost set — every tier needs a cost (free is allowed) before this collection can move to Review.
Per-tier defaults
◷ Locks on Live
TierClaim rule
PatronFree · On a whitelist
Keeper2 ICP
FounderNo cost set ⚠
B2Review — valid & still editableEvery tier has a cost set, so the collection reached Review. Collection defaults stay editable here — you can still adjust cost & requirements — but each section shows it will lock at Live.
Locked. Collection defaults freeze at go-live; new vendors created after Live still start from this frozen rule.
Per-tier defaults
🔒 Locked
TierClaim rule
PatronFree · On a whitelist🔒 Locked
Keeper2 ICP🔒 Locked
Founder4 ICP · On a whitelist🔒 Locked
B4Stage gates — referenceWhere collection defaults sit in the collection lifecycle. A plain reference table on grey (not UI).
Stage
Editable?
Gate
Draft
Yes — fully editable
Tiers may be unset (fall back to standing default)
Review
Yes — still editable
Required valid: every tier has a cost set (free is allowed); requirements optional
Live
No — read-only
Frozen: the collection defaults lock; new vendors still start from them
Part B note (not UI)
Collection defaults follow the same lifecycle as the collection's other core policy (Attributes, Supply, Rarity, Guards, Collection defaults): editable in Draft and Review, required-valid before Review, frozen at Live. The only go-Live gate is a cost set on every tier (free is allowed); requirements are optional. Go-Live / Review validation is surfaced on the collection's status checklist (see collection-states-gallery); this sub-page shows field-level state inline only.
Part C
Rarity modes
Collection defaults are tier-indexed, so the table shape follows the collection's rarity mode — exactly like collection defaults.
Modes
Uniform
No tiers — one default for the whole collection.
Tiered
The collection's own named tiers (Patron / Keeper / Founder).
Weighted
Fixed tier set (Common → Legendary).
C1Uniform — populatedUniform rarity has no tiers — one set of collection defaults for the whole collection. A single rule.
Collection default
uniform rarity
◷ Locks on Live
ScopeClaim rule
All tokens2 ICP
C2Tiered — populatedTiered rarity uses the collection's own named tiers. Each tier needs a cost; requirements optional. Cost can escalate per tier.
Per-tier defaults
tiered · 3 tiers
◷ Locks on Live
TierClaim rule
PatronFree · On a whitelist
Keeper2 ICP
Founder4 ICP · On a whitelist
C3Weighted — populatedWeighted rarity uses the fixed tier set (Common → Legendary). Same model — a cost per tier.
Per-tier defaults
weighted · 5 fixed tiers
◷ Locks on Live
TierClaim rule
CommonFree · On a whitelist
UncommonFree · On a whitelist
Rare2 ICP
Epic4 ICP · On a whitelist
Legendary4 ICP · On a whitelist
Part C note (not UI)
In V1, a tier carries two things: a required cost (Free, or an accepted currency) and optional requirements (on a whitelist / holds a token / has a stake — combined with AND; none = anyone can claim). The only go-Live gate is a cost set on every tier; requirements are optional. Restrictions (how often / how many — e.g. max per human) and Rewards (extra payout) are V2 — not yet configurable. Source: vendor-presets.md.