Arkena Docs

Submit the collection

Open /create, claim your invite, walk the six-step wizard, and sign the submission. The request lands in the admin review queue.

This is the on-chain side of launching. You bring an approved invite, the IPFS URIs from Prepare your metadata, and a connected wallet. The wizard handles the rest.

  1. Open /create

    Head to arkena.io/create. The page renders one of three states depending on where you are in the journey:

    • Access gate — you haven't claimed an invite yet (or are signing in on a new device).
    • Wizard — you've claimed and have no active request.
    • Pending review — you've submitted and the admin team is reviewing.

    Once your collection is approved, /create forwards you to /collection/{slug}/edit, the dashboard covered in Manage your live collection.

  2. Pass the access gate

    The gate has two slots side by side:

    • Invite code — paste your CR-... code (the CR prefix is fixed; you type the 4–16 character tail). Connect your wallet inside the same card, sign once, and the code consumes one creator slot bound to that wallet.
    • Wallet sign-in — for an already-approved creator on a new device. Three-step indicator: Connect → Verify → Access.

    Once either slot completes, the gate collapses to a small "Approved creator — N/M collection slots used" chip and the wizard opens below.

  3. Walk the six-step wizard

    The wizard is a sticky-footer flow with six steps. A step indicator at the top lets you jump back to any visited step; forward jumps are blocked until the current step validates.

    Live preview · type to fillarkena.io/create
    Name*
    SlugAuto-derived
    arkena.io/collection/pixel-punks
    Description
    Price*CC
    Supply*
    Royalty5.0%
    Live preview
    Pixel Punks
    1000 hand-pixelated punks living on Canton.
    Supply
    1000
    Price
    12 CC
    Royalty
    5%

    Your progress is auto-saved to the browser after every keystroke. If you refresh, a Resume draft banner offers to pick up where you left off. Logo and banner files are the only fields that do not survive a refresh — you'll be asked to re-select them.

    1. Basics — collection name (3–50 characters), URL slug (3–32 characters, lowercase kebab-case), description (up to 1000 characters). The slug is auto-derived from the name as you type and checked for availability live; type into the slug field to override.

    2. Media — logo (square display, max 5 MB) and banner (4:1 display, max 10 MB). JPG, PNG, or WebP. Both are stored by Arkena, not on IPFS.

    3. Mint configuration — pick a supply mode, then set royalty in percent (0 to 5, capped on-chain at 500 bps). Two supply modes:

      • Limited — a fixed max supply (1 to 100,000). Sells out when reached; the cap can only ever be lowered later.
      • Open edition — no supply cap. Every token gets a sequential ID as it's minted, and you can freeze the edition at a finite cap later from the dashboard.

      Royalty is immutable after deploy.

    4. Metadata strategy — what holders see at mint. A limited collection picks Instant or Reveal later; an open edition always uses one shared file.

      • Instant takes a base URI (ipfs://Qm…/, per-token JSON appended at mint).
      • Reveal later takes a single placeholder URI shown for every token until you flip the reveal from the dashboard.
      • Open edition takes one shared URI (single .json) that every token resolves to — no reveal flip, no per-token files.

      The strategy is locked at deploy. See Prepare your metadata for the file layout.

    5. Mint phases — at least one phase is required, up to ten. See the next step.

    6. Review — read-only summary; the Create Collection button at the footer opens the wallet for signing.

  4. Configure phases

    A phase is a slice of the launch with its own price, time window, eligibility, and per-wallet cap. The wizard ships with one default phase ("Public Mint"); add up to nine more for tiered drops like OG → Whitelist → Public.

    Phase configuration · 3-tier launchpadarkena.io/create/…/phases
    OG accessOG
    Ready
    Price8.00 CC
    Slice100 items
    EligibilityWhitelist · 42 wallets
    WindowT0 → T0 + 6h
    WhitelistWhitelist
    Ready
    Price10.00 CC
    Slice400 items
    EligibilityWhitelist · 380 wallets
    WindowT0 + 6h → T0 + 24h
    PublicPublic
    Draft
    Price12.00 CC
    Slice500 items
    EligibilityOpen · anyone
    WindowT0 + 24h → sold out

    Each phase carries:

    • Name — what holders see on the launchpad.
    • Price in CC — paid by minters during that phase. Set it to 0 for a free mint.
    • Start time — local time, sent as UTC.
    • End time (optional) — leave off to make the phase open-ended. Only the last phase can be open-ended.
    • Max per wallet — cap mints per address during this phase. Optional for a paid phase; required for a free phase, where the wizard turns it on and locks it so an uncapped free mint can't be configured.
    • Allowlist (optional, expandable panel) — paste party IDs into the textarea, or drag-drop a CSV / TXT file (up to 10 MB). Up to 100,000 addresses across all phases combined. The widget shows live counters for valid, duplicate, invalid, and self-reference entries (your own wallet is silently rejected). A phase with an allowlist is private — only listed wallets can mint during its window. Leave the panel collapsed to keep the phase public.

    Phases must be chronologically disjoint — overlapping windows are rejected at submit. You can rotate or update the allowlist after approval from the dashboard.

  5. Sign and submit

    Click Create Collection on the Review step. Three things happen automatically:

    1. The backend prepares the on-chain transaction and shows a summary in your wallet.
    2. You sign once with the Arkena extension — the signature stays on your device.
    3. The backend executes the transaction. If the network briefly drops the submission, the wizard transparently re-prepares and re-signs once; nothing double-fires.

    After execution the page flips to the pending review card.

  6. Wait for review

    The pending review card surfaces the full submission: banner, logo, mint schedule with per-phase pricing and allowlist counts, supply, royalty, reveal mode, and a short "~24h" review timeline.

    • Approved/create forwards you to /collection/{slug}/edit, the dashboard.
    • Rejected — the slot is restored automatically; you can re-enter the wizard with your draft intact and resubmit.
    • Cancel & edit — click the button on the pending card to withdraw the request before review. Your draft stays saved in the browser, so you can tweak any field and resubmit without retyping.

What's locked at submit time

A few decisions are permanent the moment the admin approves. Pick them carefully when you fill in the wizard.

FieldAfter approval
RoyaltyImmutable
Supply mode (limited vs open edition)Immutable
Reveal strategy (instant vs hidden)One-way: hidden → revealed
Hidden placeholder URIImmutable
Instant base URIImmutable
Open-edition shared URIImmutable
Collection name and slugImmutable
Supply cap (limited)Can only be lowered (never below minted count)
Open editionCan be frozen once at a finite cap (never reopened)
Logo, banner, description, social linksEditable anytime
Phase price, window, cap, allowlistEditable from the dashboard

What's next

Once your collection is live, head to Manage your live collection for phase management, allowlist rotation, reveals, airdrops, and the rest.