Skip to main content
The Xpectrum Launchpad is the creator-facing tool for deploying and managing NFT collections. Contract deployment, artwork generation, whitelist management, phase configuration, and reveal, all through a no-code interface. Under the hood it runs the same engine as xpress, so anything you launch is independently verifiable.

Creating a collection

1

Configure collection details

Set name, symbol, max supply, mint price, and royalty. Royalties are capped at 10% and enforced on-chain by Xmarket on every secondary sale.
2

Prepare artwork

Upload pre-rendered art, or define trait layers and rarity quotas and let the generator build the collection. The generator produces exact quotas (“10 legendaries” means exactly 10) and a provenance hash computed locally.
3

Set up minting phases

Configure the three-phase sequence, each time-gated by epoch ranges.Durations are set in epochs against the live chain rate. GTD and public need a valid window; FCFS is optional. A cap of 0 closes a phase even if it has a window; set the cap to the supply to leave it fully open.
4

Manage your whitelist

Add addresses through the dashboard. Before deployment these are stored off-chain at no cost. After deployment, each update is written on-chain via Xlist, which is the authoritative record.
5

Deploy

Deploying provisions your Xcollection, a bound Xlist, and the collection’s Circle. You sign from your own wallet and you own all of it. Minting opens according to your phase schedule.

Anti-snipe reveal

Xpectrum collections launch with a commit-first, delayed reveal so nobody can snipe rare tokens during the mint:
  1. Before mint opens, the provenance hash is committed on-chain from your wallet. The token-to-trait assignment is locked from that moment.
  2. The rarity-revealing per-token metadata is held back during the mint, so buyers cannot read which IDs are rare.
  3. When you are ready, you reveal: the held-back metadata is published to your Circle and the collection flips to revealed.
Because the hash is committed before mint and the reveal is published on-chain, anyone can later prove the collection was not altered after the fact. See Provenance.
Keep the backup the Launchpad gives you at deploy time. Your generated metadata is created in your browser; the backup is what you re-import to reveal later.

Genesis injection

Every deployment reserves an allocation for Xpectra holders: min(floor(supply * 0.2), 222), additive on top of your GTD whitelist allocation. An Xpectra holder mints during GTD by presenting an Xpectra token ID they own. Each Xpectra token ID can be used once per collection, and the holder is still bound by the GTD per-wallet cap and the collection’s global per-wallet cap. Unclaimed injection slots are released after GTD via a permissionless sweep. See Xcollection.

Phase overrides

The dashboard exposes Force Phase controls during a live mint, so you can advance or hold a phase without waiting for the epoch timer:
  • Extend GTD if your community needs more time
  • Skip FCFS and go straight to public
  • Pause minting while investigating an issue
Overrides are on-chain transactions. Remove the override to return to epoch-based resolution.

Airdrops

Airdrop up to 20 tokens per transaction directly from the collection. Airdrops bypass phase, price, and whitelist logic.
Airdropped tokens count toward max_supply but do not reduce phase caps. Plan allocation before configuring caps to avoid overselling.

Collecting proceeds

Mint proceeds are pull-based. Platform (2.5%) and creator (97.5%) shares accumulate on-chain and are collected separately. The dashboard surfaces your unclaimed balance and claims it in one click.