Onboarding a collection

Updated 6 October 2026. For collection teams and community members proposing a collection.

Eligibility

A collection can use the standard helper if:

• its mint has finished. The record covers the tokens that exist when the manifest is built; tokens minted later are not covered.
• each token’s art is 32 MB or smaller. Files up to 512 KB are inscribed in a single transaction. Larger files go through a multi-transaction route (see below).
• its contract has a plain holder-authorised transfer and a read-only owner lookup, and nothing can move a token out of the helper without the helper’s signature.
• the art can still be fetched, from the original host or a verifiable backup.

Collections whose contract has its own market (list-in-ustx / buy-in-ustx) use the G2 template, which refuses to take a listed token, so holders must unlist before swapping. Collections with plain transfers use G1. Collections that fit neither need an adapter and are handled case by case.

What we need from you

• The contract address and a link to the collection.
• Where the art and metadata are hosted today.
• Any original art files or backups your team holds.
• A community contact for announcements and questions.

Message @XtrataLayers on X to start.

What happens

1. Screening. We check the contract and confirm its group (G1 or G2).
2. Manifest. We fetch every token’s art, record its fingerprint, file type and size, and publish the manifest. The manifest records the chain height it was built at.
3. Deploy and seed. The helper is deployed and the record is loaded into it in batches of 100 tokens.
4. Check. The manifest is public so the community can check it against the original collection and against the helper before it is locked.
5. Finalise. The record is locked for good. Nothing can be inscribed before this.
6. Launch. The collection is added to the registry and gets a page.

Large files

Art over 512 KB cannot use the single-transaction route. Helpers can be deployed in one of two ways:

• Pre-inscribed. The owner inscribes each large file through the core’s multi-transaction upload and binds it to its token before the record is finalised.
• Large-on-demand. The record is finalised with large files still unbound, and any visitor can create the twin later through the collection page’s guided route (temporary wallet, resumable uploads, leftover STX returned). Bitcoin Monkeys uses this because 283 of its 2,500 files are over 512 KB.

After launch

• Holders create twins and swap whenever they like. Nothing expires.
• The fee is shown on the collection page and in the contract (get-fee).
• Please share the “never send your NFT directly to the helper” warning with your community.

For developers

The helper template, renderer, manifest builder, tests and deployment notes are in the ft-harness folder of the repository. This is an unaudited prototype. Each deployed helper is pinned to the exact source we tested: see Verify it yourself.