Export and release

The sale is on the marketplace; the mint is a command on this PC

The studio assembles the files and has no mint button. The sale is on the marketplace website. A Solana Core mint and the reveal are series mint and series reveal on your computer, signed with your own wallet. The private key is never sent to Lab or to the server.

Build the archive

1. On Export, run the checklist: the preset and archive are there, DNA has no duplicates, image count matches the series, some items are marked Keep, and prompts do not contain blocked brands.
2. Build the ZIP. For the release, include only items marked Keep.
3. Inside: images, metadata JSON for the network you chose, a CSV table, a short release guide and a collection summary. Solana includes a Core Candy Machine draft. EVM includes a Thirdweb config. Ordinals is a pack aimed at an inscription.

Which network

LaunchMyNFT numbers files from zero. The other profiles start at one. Changing the network clears a ZIP and guide you already built — build them again. Sugar in the Solana list is the legacy path, not for a new collection.

Arweave via Irys

A Solana release is uploaded from your PC. The key stays in a file on that computer:

node bin/series.mjs upload <set-folder> --keypair deployer.json

• The image goes up first, its link is written into the metadata, then the JSON is uploaded.
• Progress is written to cache.json. If you stop, run the same command again: finished items are skipped.
• You see an estimate in SOL before anything is paid.

The Arweave button on Export publishes the set images and fills an ar:// prefix. Review notes sitting next to the pictures are not part of that upload. The button appears only when the server has its own wallet with a small balance, and it is hidden when that key is not set. For a collection release it does not replace upload.

From the deploy kit to mint and reveal

1. Build the deploy kit. The default is Solana (Core Candy Machine), devnet first. On Solana you can paste allowlist addresses, one per line. The kit then includes allowlist.json.
2. series release-init writes the release file. Guards, verify and mint read it. Put the same allowlist wallets into release.json. The studio does not build this file and does not take a key.
3. Upload the bundle with series upload and --keypair. The key stays in a file on this PC.
4. Upload hidden.json on its own, take the link, and run series hidden. Until this step the hash in the kit is empty.
5. Rules: series guards. You create the machine with mplx cm create, using that config and the hidden settings, without per-item lines. The studio does not deploy the program. series mint builds Core only, not Sugar.
6. When the machine exists, write its addresses into release.json (the deployed field). Then series verify only reads the chain and signs nothing.
7. Mint with series mint and --keypair. A wallet on the allowlist uses the wl group, and the proof is already inside the transaction. The open phase is --public. --dry-run sends nothing. After a mint, mints.json appears on this PC.
8. Solana reveal: series reveal with --keypair of the collection update key, not the machine key. Without a key the command only writes the list. EVM reveal stays a Thirdweb dashboard step; the password is not written to a file.

node bin/series.mjs release-init out/<archive>.json -o release.json --creator <public address> --price <price in SOL>
node bin/series.mjs upload <set-folder> --keypair <file>
node bin/series.mjs hidden <set-folder> --uri <link to hidden.json>
node bin/series.mjs guards release.json
node bin/series.mjs verify release.json
node bin/series.mjs mint release.json --keypair <wallet.json>
node bin/series.mjs reveal <set-folder> --keypair <collection-update-key.json>

PNG layers are optional, earlier, on Generate: Compose layers. That does not replace prompts and does not charge credits. series mint builds payment, a date, the allowlist and the per-wallet limit. Any other rule stops the command. Do not hand in the allowlist proof yourself.

Marketplace

Build the marketplace kit for listing copy and the banner, avatar and cover sizes. You publish from your own account: Solana — Magic Eden and Tensor, EVM — OpenSea, Bitcoin — Ordinals.

Useful before the drop

• The provenance hash in the ZIP is a fingerprint of every image, so the set cannot change quietly before the sale.
• The showcase is a single HTML file with rarity and ranks. Open it locally and look through the collection.
• Separately, if you want to train a model: a LoRA dataset ZIP of image-and-caption pairs. That is not a release step.