Manage your live collection

Once your collection is approved, Arkena forwards you to the creator dashboard at /collection/{slug}/edit. Everything you do after launch — schedule phases, rotate allowlists, edit the marketing copy, airdrop to your own wallet, reveal, cut supply — happens here.

The dashboard

The dashboard is a single page with a sticky tab bar:

• Overview — live drop progress and recent activity.
• Phases — schedule, edit, or remove mint phases and rotate allowlists.
• Details — off-chain marketing copy, logo, banner, social links.
• Airdrop — send NFTs from your collection to your own wallet before or during the public mint.
• Settings — one-way actions (reveal, reduce supply).

The hero strip across the top shows your collection logo, name, slug, royalty percentage, and status badges (LIVE, PAUSED, SOLD OUT, VERIFIED, HIDDEN). The dashboard subscribes to a live event stream, so progress numbers, recent activity, and phase rotation update in real time without a refresh.

Overview

The landing tab. Five cards stack into a "mission control" layout:

• Drop progress — minted vs cap, with a live progress bar. The subtitle names the active phase, or counts down to the next one (next in 1h 24m). An open edition has no cap, so this card shows a running mint count with no bar and no percentage.
• Holders — unique wallets holding any NFT in the collection.
• Trading status — secondary-market trading is on or off. This is platform-controlled; you do not toggle it from the dashboard.
• Royalty and Current price — quick stats. The price shown is whatever the active phase charges, or the headline price if no phase is active.
• Recent activity — the latest mints, listings, sales, transfers, and offers across the collection. Click View all to jump to the full activity feed on the public collection page.

A row of Quick actions at the bottom links into the other four tabs.

Phases

Phases are slices of the launch with their own price, window, allowlist, and per-wallet cap. They rotate automatically by wall-clock — when one phase's endTime passes (or the next phase's startTime hits), the active marker advances on its own. You do not "open" or "close" phases manually.

Add or edit a phase

Click + New phase to open the phase modal. For an existing phase, click the row to open the same modal in edit mode.

The phase modal asks for:

• Phase ID — a short kebab-case key (e.g. og-mint). Locked after creation; this is the on-chain dedup key.
• Display name — what holders see.
• Price in CC.
• Max per wallet — 0 means unlimited.
• Public phase toggle — public phases accept any wallet; private phases require an allowlist (managed on the same tab, see below).
• Start time and End time — local time, sent as UTC. End time is optional.

Each save is a single wallet signature.

Remove a phase

Click the trash icon on a phase row. The confirm dialog asks you to type the phase ID before archiving — a guard against stray clicks. Wallets that have not minted under the phase lose access; existing mints stay valid.

Allowlists

The Phases tab also hosts allowlist management, just below the phase list. If at least one phase is private (the toggle is off), the section shows:

• A tab strip if multiple private phases exist, so you can switch between them.
• A status banner — Public or Private + a truncated merkle root.
• A paste textarea for party IDs (one per line or comma-separated), or drag-drop a CSV / TXT file (up to 10 MB). Up to 100,000 addresses per phase.
• Live counters as you paste — valid, duplicates, invalid, self-reference (your own wallet is silently rejected).
• Upload N addresses — submits the list. The backend derives the merkle root and writes it on-chain; you sign once.
• Clear whitelist (dashed underline, red) — wipes the list and makes the phase public again.

When allowlist rotation locks

Once a phase's end time passes, or the collection sells out, allowlist rotation locks for that phase. This is by design — it prevents retroactive list rewrites after holders have already minted. The paster shows a small lock banner explaining which condition triggered the lock.

You can also configure the initial allowlist during the create wizard so the phase starts private from minute one. See Submit the collection.

Details

Off-chain marketing copy. None of these need a wallet signature — they write to Arkena's projection directly.

• Description — up to 1000 characters. Markdown is not rendered; whatever you type is what holders see.
• Logo and banner — drag-and-drop a new file, or paste an https:// / ipfs:// URI. Upload mode and URI mode are mutually exclusive per slot.
• Social links — Website, X / Twitter, Discord, Telegram. Leave a field empty to clear it.

The same tab also surfaces a read-only block with your on-chain configuration (max supply with minted count, royalty, platform status) and the reveal-mode banner with the URIs that were locked at deploy.

A sticky bar at the bottom tracks dirty state. Hit Save changes to push, or Discard to revert.

Airdrop

Send NFTs from your own collection to your own wallet before or during the public mint. Useful for marketing seeds, team allocations, or partner drops.

The flow:

1. Open the Airdrop tab. The panel shows your remaining capacity (maxSupply − mintCount) and an input field.
2. Enter a quantity between 1 and remaining. Confirm in the panel's typed-confirm dialog.
3. Sign once with your wallet. The backend stages the airdrop intent and a worker settles it in batches of 50 NFTs per Canton transaction.
4. The panel switches to a live progress view. Each batch lands and the counter ticks up; when the final batch settles, the panel flips to a done state.

You can cancel an in-flight airdrop from the panel — any quota that hasn't settled yet is released back into the supply pool. Airdrops draw from a fixed cap, so they're not available on an open edition; the panel surfaces a locked state in that case.

Settings — Danger zone

One-way, irreversible actions live in their own tab so they don't sit next to everyday edits. Each row requires a typed confirmation before firing.

Reveal the collection

Shown only if you launched in Reveal later mode and have not yet revealed. The dialog displays the current placeholder URI and asks for the new base URI (ipfs://Qm…/). On submit, every NFT in the collection switches from the placeholder to its individual <tokenId>.json under the base URI.

Reveal is one-way. You cannot un-reveal.

Reduce max supply

Shown for a limited collection that has not sold out. Lower the cap to a new value — it must be at least the current minted count (you cannot orphan minted tokens) and strictly less than the current cap. The on-chain ensure rejects anything else.

One-way; the cap can only ever shrink.

Freeze an open edition

Shown for an open edition. Lock the edition at a finite cap so it can sell out instead of minting forever. Type the cap you want — it must be at or above the count already minted. Once frozen the collection behaves like a limited drop: the cap can only be lowered further from here, and it can never be reopened.

One-way; an open edition that's been frozen cannot return to unbounded supply.

What's locked

A few decisions are permanent. They were set when you submitted the collection or are reserved for platform operators.

What's next

• Fees and pricing — what holders see at mint time.
• Security best practices — your creator wallet is now load-bearing; treat it accordingly.