The collection-level Claim defaults page — the default claim cost and rule for each rarity tier; new vendors drawing from the collection start here, then edit per vendor. This single reference combines three views: Part A — the page itself (set & unset); Part B — how it behaves across the collection lifecycle (Draft → Review → Live); Part C — how it adapts to each rarity mode (Uniform / Tiered / Weighted). Four concepts per tier: Cost (required — free / ICP / ICRC-1), Requirements, Restrictions and Rewards. Collection sub-page → auto-saves (no Save/Discard). Promo/redemption codes are project-level, not here.
Part A
The Claim defaults page.
The page itself — default cost and rule per rarity tier, shown set (valid, ready for Live) and unset (blocks go-Live), plus the rule editor. Auto-saves; stage persistence lives on the collection bar.
A1Claim defaults — setA collection with claim defaults in place. Costs and Rules are separate sections; each rarity tier has a default cost and a default rule. 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.
Default cost and rule per rarity tier for Hollow Court. New vendors drawing from this collection start here, then can edit per vendor. Every tier needs a cost and a rule before the collection can go Live.
All tiers have a cost and a rule. This collection can go Live. Defaults are a template — editing them doesn't change vendors that already exist.
Costs
5 / 5 tiers priced
Common1 ICP
Uncommon2 ICP
Rare5 ICP
Epic10 ICP
Legendary25 ckUSDC
Each tier's default cost — ICP or any ICRC-1 token. Legendary is defaulted to an ICRC-1 token (ckUSDC).
Each tier's default requirements (AND) and restrictions. Requirements gate who can claim; restrictions limit how much (e.g. max per wallet). Promo & redemption codes are not set here — they're project-level code sets (campaign access) attached to a vendor or source, not a collection default. Future addition.
A2Rule editor — collection defaultOpened from "Edit" on a tier in the Rules section. Requirement types are accordions (same pattern as the vendor editor) plus a Restrictions section. Note: no Promo code / Redemption code here — those are project-level code sets attached to a vendor/source (future). Hold Token from Collection is a disabled teaser.
Edit default rule · Hollow Court · Legendary
This is the default rule for the Legendary tier. Vendors copy it and can override per vendor. Requirements combine with AND — the more you add, the fewer collectors qualify.
ICP NeuronActive
ICP
ICRC-1 NeuronActive
$DKP
Whitelists1 selected
Court Founders210 addressesLive
Allowlist A900 addressesLive
Only the project's Live whitelists appear here.
Hold Token from CollectionComing soon
0 = unlimited
A3Claim defaults — not set yetA Draft collection before defaults are configured. Tiers exist (from the rarity system) but have no cost/rule. The page is editable in any state, but the collection can't go Live until every tier has a cost and a rule.
Default cost and rule per rarity tier for Realm Keepers. Set these before the collection can go Live.
Claim defaults aren't set. Give every tier a cost and a rule — set the base tier and apply it to all, then customise. This collection can't go Live until it's complete.
Costs
0 / 5 priced
No costs set
Set a default cost for each rarity tier — price the base tier and apply it to all, then adjust per tier. ICP or any ICRC-1 token.
Rules
0 / 5 set
No rules set
Set a default rule (requirements + restrictions) for each tier. A tier can be open (no gates), but it still needs a defined rule. Set the base and apply to all.
Part A note (not UI) — why codes aren't hereCollection claim defaults describe the durable, rarity-based way a collection's tiers are sold (cost, neuron stake, whitelist, restrictions) — sensible to reuse across every vendor drawn from the collection. Promo and redemption codes are project-level code sets (campaign access, often single-use, tied to a particular drop/partnership) attached to a vendor or source — so one code can unlock a multi-collection vendor without duplicating pools per collection. They don't belong in a collection-wide default. A future addition (backend currently rejects these requirement types). Hold-token gating is also deferred.
Part B
Across lifecycle stages.
How Claim defaults behave through the collection lifecycle: editable in Draft, required-valid before Review, still editable in Review, then locked read-only at Live. Example: Hollow Court (Weighted, 5 tiers).
Draft
Editable. Set a cost on every tier (free / ICP / ICRC-1). Incomplete defaults block the move to Review.
Review
Required-valid to get here. Still editable; every section shows a "Locks on Live" pill.
Live
Locked read-only. Issued tokens depend on these, so cost, requirements, restrictions & rewards can't change.
B1Draft — not yet valid (change required)Being set up. Legendary still has no cost, so the collection can't be submitted to Review. Everything is editable; each section carries a "Locks on Live" pill so the creator knows it'll freeze later.
Set a cost on every tier — required before this collection can move to Review.
Draft
1 change needed before Review. Every tier must select a cost (free counts). Requirements, restrictions & rewards are optional.
Cost
What you pay · required
Locks on Live
CommonFree
Uncommon2 ICP
Rare5 ICP
Epic10 ICP
LegendaryNot set
Requirements
Optional
Locks on Live
Common → LegendaryGates set per tier — optional; none means anyone can claim
Sub-pages auto-save · stage changes happen on the collection management bar
Submit to Review is disabled until Legendary has a cost. The validation lives on the collection's status checklist; this sub-page just shows the field-level state inline.
B2Review — valid & still editableEvery tier has a cost, so the collection reached Review. Claim defaults stay editable here — you can still adjust cost or rules — but each section shows it will lock at Live.
Valid and publicly reviewable. Still editable until the collection goes Live.
Review
Claim defaults are valid. Every tier has a cost — this requirement was met to enter Review. You can keep editing; it all locks when you publish to Live.
Cost
What you pay
Locks on Live
CommonFree
Uncommon2 ICP
Rare5 ICP
Epic10 ICP
Legendary25 ckUSDC
Requirements
Optional
Locks on Live
RareICP Neuron
LegendaryICP NeuronWhitelist
Sub-pages auto-save · stage changes happen on the collection management bar
B3Live — locked read-onlyOnce Live, claim defaults are frozen — issued tokens depend on them. No Edit actions; each section shows a "Locked" pill and the pages open read-only.
Locked — these were fixed when the collection went Live.
Live
Claim defaults are locked. Cost, requirements, restrictions and rewards can't change after Live — collectors are claiming against them. View only.
Cost
What you pay
Locked
CommonFree
Uncommon2 ICP
Rare5 ICP
Epic10 ICP
Legendary25 ckUSDC
Requirements
Locked
RareICP Neuron
LegendaryICP NeuronWhitelist
Live collection — core policy is locked
B4Stage gates — referenceWhere claim defaults sit in the collection lifecycle. A plain reference table on grey (not UI).
Claim defaults · lifecycle
Draft — editable
Set cost (free / ICP / ICRC-1) per tier, plus optional requirements. Auto-saves; nothing required yet.
Required before Review
Every tier must have a cost before the collection can be submitted to Review. (Invalid inputs — unresolved ledgers/canisters, non-Live whitelists — can't be entered in the first place.)
Review — still editable
Valid and publicly reviewable; you can keep adjusting cost and rules. Each section flags "Locks on Live".
Locked at Live
Frozen read-only — issued tokens depend on these values, so they can't change after Live.
Part B note (not UI)Claim defaults follow the same lifecycle as the collection's other core policy (Attributes, Supply, Rarity, Guards): editable in Draft and Review, required-valid before Review, locked at Live. The only required field is a cost on every tier (free is a valid choice); requirements / restrictions / rewards stay 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
By rarity mode.
How the page adapts to each rarity system — Uniform (one set for the whole collection), Tiered (named tiers), and Weighted (fixed Common → Legendary) — each empty and populated, plus the cost picker and rule editor. Four concepts per tier below.
Cost
What you pay · required · Free, ICP, or ICRC-1
Requirements
What you must prove/have · optional · combine with AND
Restrictions
How often/much you can claim · optional · coming soon
Rewards
Extra payout for claiming · optional · coming soon
C1Uniform — emptyUniform rarity has no tiers — one set of defaults for the whole collection. Only the cost is required; with no requirements, anyone can claim.
Winter Tales uses Uniform rarity — one cost, requirements, restrictions & rewards for the whole collection.
Set a cost to go Live. A cost is required (free is allowed). Requirements, restrictions and rewards are optional — with none, anyone can claim for the cost.
Cost
What you pay · required
Not set
No cost set
You must choose one of these claim options for each tier:
Free
ICP payment
ICRC-1 token payment
This is required before your collection can go live.
Requirements
What you must prove/have · optional
Anyone can claim
No requirements
Default — anyone can claim (paying the cost).
+
Add new rule
Gate who can claim with an ICP/ICRC-1 neuron, whitelist or token-hold requirement. Multiple requirements combine with AND.
Restrictions
How often/much · optional
None
No restrictions
Maximum claims per human
Coming soon
Rewards
Extra payout · optional
None
No reward
Default — claimants receive the token only.
ICP per claim
Coming soon
ICRC-1 token per claim
Choose ICRC-1 token type▾
Coming soon
C2Uniform — populatedCost set to 4 ICP, one whitelist requirement. Restrictions/rewards default to none (coming soon).
C3Tiered — emptyTiered rarity uses the collection's own named tiers. Each tier needs a cost; requirements/restrictions/rewards are per-tier and optional.
Every tier has a cost. This collection can go Live.
Cost
What you pay
5 / 5 priced
CommonFree
Uncommon2 ICP
Rare5 ICP
Epic10 ICP
Legendary25 ckUSDC
Requirements
Combine with AND
4 / 5 gated
CommonNo requirements · anyone can claim
UncommonWhitelist
RareICP Neuron
EpicICP Neuron+Whitelist
LegendaryICP Neuron+ICRC-1 Neuron+Whitelist
Restrictions
None
No restrictions
Maximum claims per human
Coming soon
Rewards
None
No reward
Default — claimants receive the token only.
ICP per claim
Coming soon
ICRC-1 token per claim
Choose ICRC-1 token type▾
Coming soon
C7Cost picker — one must be selectedOpened from "Set cost" / "Edit" on a tier. Exactly one of Free / ICP / ICRC-1. ICRC-1 reveals a common-token dropdown with a "Custom — add ledger…" path (validated on entry).
Cost · Hollow Court · Legendary
Free claim
No cost — claimants pay nothing.
ICP
Charge an amount in ICP.
ICRC-1 token
Charge an amount in any ICRC-1 token.
ckUSDC▾
Common tokens, or Custom — add ledger…
C8Cost picker — custom ICRC-1 ledger (validated on entry)Picking "Custom — add ledger…" reveals a canister-ID field validated the moment it's entered. An unresolved ledger can't be saved, so an invalid cost token never reaches go-Live — there's no "unresolved ledger" go-Live error because it can't be added in the first place.
Cost · Hollow Court · Legendary
Free claim
No cost — claimants pay nothing.
ICP
Charge an amount in ICP.
ICRC-1 token
Charge an amount in any ICRC-1 token.
Custom — add ledger…▾
Couldn't resolve an ICRC-1 ledger at this canister. Check the ID and try again.
C9Rule editor — Requirements · Restrictions · RewardsOpened from "Add" / "Edit" on a tier. Requirements are accordions; restrictions and rewards are present but coming soon. Promo/redemption codes are project-level, not here.
Edit rule · Hollow Court · Epic
With no requirements, anyone can claim. Add requirements to gate who qualifies — they combine with AND, so the more you add, the fewer people qualify.
ICP NeuronActive
ICP
ICRC-1 NeuronNot set
Whitelists1 selected
Court Founders210 addressesLive
Allowlist A900 addressesLive
TokoToken — hold from a collectionComing soon
Max claims per human Coming soon
Default: no restrictions. Will cap claims per verified human once available.
ICP payout Coming soon
Pay claimants an amount of ICP on top of the token.
ICRC-1 token payout Coming soon
Pay claimants an amount of a chosen ICRC-1 token.
Part C note (not UI)Four concepts per tier: Cost (what you pay — required, one of free/ICP/ICRC-1), Requirements (what you must prove/have — optional, AND-combined; none = anyone can claim), Restrictions (how often/much — optional; "max per human" coming soon), Rewards (extra payout — optional; ICP/ICRC-1 coming soon). Invalid inputs are prevented at entry, not deferred to go-Live. Only Live whitelists appear in the picker (a non-Live list can't be selected); a custom ICRC-1 cost ledger or SNS governance canister must resolve before it can be saved (frame 08), so an unresolved token/canister can never be attached. That leaves a single thing claim defaults gate — a tier with no selected cost — which is required before Review (and the whole thing locks at Live); it's surfaced on the collection's Draft→Review status checklist (see collection-states-gallery and claim-defaults-stage-states-gallery), not on this sub-page. Empty requirements/restrictions/rewards are never errors. Promo/redemption codes are project-level (future), not collection claim defaults.