Skip to main content
Collections are launched from Xpectrum Creators: contract deployment, artwork generation, allowlists, phases, reveal, and the manage screen you run the drop from. Under the hood it is the same engine as xpress, so anything launched through it is independently reproducible.
Creators is its own app at creators.xpectrum.xyz. The marketplace at app.xpectrum.xyz is for collecting and trading. Old /launch and /launch-guide links on the marketplace redirect across.The step-by-step walkthrough, with live widgets for the cap arithmetic and the phase timeline, is the launch guide in the app itself. This page is the reference.

​
Creating a collection

1

Configure collection details

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

Prepare artwork

Composite from trait layers in the Lab, or upload prerendered art. The generator produces exact quotas, so “10 legendaries” means exactly 10, and computes the provenance hash locally.
3

Set up minting phases

Three windows, time-gated by epoch ranges.The maximum is about 31 days for Guaranteed and First come. Public has no upper bound. Windows may not overlap, and a shorter window is rejected on chain rather than by the form. Price is in OCT and 0 is legal: a price of 0 is a free mint, not a disabled phase.
4

Set the allowlist

Add addresses in the Creators dashboard. Before deployment they cost nothing and are held off-chain. After deployment each update is written on-chain through Xlist, which is the authoritative record, batched twenty at a time.Guaranteed and First come keep separate lists. A wallet on both mints its guaranteed allocation first and can mint again in First come, subject to that window’s wallet cap.
5

Deploy

One transaction provisions your Xcollection, a bound Xlist, and the collection’s Circle. You sign from your own wallet and you own all three. The current factory charges a 1 OCT launch fee, plus about 0.2 OCT of network fee.

​
Caps share one budget

The three phase caps are not independent ceilings. The contract adds them together with the Xholder reserve and anything already airdropped, and the total has to fit inside max supply:
Leaving the Public cap at 0 is usually right. Public then takes whatever is left, including any Xholder reserve that goes unclaimed, so nothing strands.
A cap of 0 does not mean the same thing in every window. On Public it means take the remainder. On Guaranteed it means no allowlist allocation at all, so only the Xholder reserve mints in that window.

​
The Xholder reserve

Every deployment reserves an allocation for Xpectra holders, set by the factory at creation and not editable afterwards:
It is its own pool, additive on top of your Guaranteed allowlist allocation, and it never erodes it. An Xpectra holder mints during Guaranteed by presenting an Xpectra token ID they own, which the contract verifies against the Xpectra collection at mint time.
One claim per wallet, not one per Xpectra held. A wallet holding ten Xpectra gets one reserved mint on your collection, the same as a wallet holding one. The claim is tracked per wallet in xholder_claimed and is decoupled from the Guaranteed per-wallet cap and the Guaranteed minted counter, so it does not consume an allowlist spot.
Unclaimed reserve slots return to the public pool after Guaranteed ends, through trigger_sweep(), which anyone may call. See Xcollection.

​
Anti-snipe reveal

Collections launch commit-first with a 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. Rarity-revealing per-token metadata stays dark during the mint, so buyers cannot read which IDs are rare.
  3. When you are ready, reveal() sets the base URI and the collection flips to revealed.
Because the hash is committed before mint and the reveal is published on-chain, anyone can prove afterwards that the collection was not altered. See Provenance.
Keep the backup Creators gives you at deploy time. Your metadata is generated in your browser, and the backup is what you re-import to reveal later.

​
Phase overrides

The manage screen can override the schedule during a live mint: follow the windows automatically, or force Guaranteed, First come, Public or Closed regardless of the clock. Useful for opening or closing immediately. Overrides are on-chain transactions. Forcing a phase back to Closed does not undo anything that already happened.

​
Airdrops

Airdrop up to 20 addresses per transaction, free, bypassing phase, price and allowlist logic. Owner only.
Airdropped tokens count toward max_supply and against the shared cap budget, but they do not reduce phase caps automatically. Plan the allocation before setting caps.

​
Burning

Collections launched through the current factory expose burn(token_id), callable only by the token’s current holder. Not the collection owner, not an admin, not the factory. Burning never lowers max_supply and never reopens a mint slot: total_minted stays monotonic and is the id source, and live supply is derived as total_minted - burned. Ids are never reused. There is no batch burn. Holders burn from the Incinerator tab on their profile in the marketplace. Creators burn from the Ownership section of the manage screen.

​
Collecting proceeds

Mint proceeds are pull-based. Platform (2.5%) and creator (97.5%) shares accrue on-chain and are claimed separately, in their own transaction. The manage screen shows the unclaimed balance and claims it.