Technical Notes.
Less mystery. More clarity.

In place · collection tools

The goal is 10,000 fun-loving characters, not 10,000 copies of the same idea. Standard pieces combine traits such as species, expression, outfit and props; bespoke 1/1s sit alongside them in the same collection.

For standard pieces, the studio records an ordered trait fingerprint and checks it before generation. A database uniqueness rule prevents two standard pieces in the creator’s collection from storing the same fingerprint, including when jobs run together.

What this proves: distinct recorded trait combinations. It is not a cryptographic hash of the artwork, a guarantee that images cannot look similar, or an on-chain proof. Bespoke 1/1s are exempt from the standard combination rule and are reviewed individually.

In place · collection tools

New ideas arrive as the collection develops. We don’t want the later numbers to feel like a completely different club.

The studio’s balancing tool mixes pieces from 20 creation-era groups and spaces bespoke 1/1s throughout the kept collection. Rejected drafts move to the end, leaving kept pieces with consecutive numbers. Artwork and traits stay attached to their original records; only the display number and numbered name change.

Balance is not mint randomness. This spreads creation eras and 1/1s; it does not guarantee identical species, trait frequencies or rarity odds in every block. The tool is available, but that does not mean the final numbering has been run or locked.

Proposed · not yet deployed

You’re saying it correctly: a minted NFT has a token ID. Its metadata connects that ID to a particular character’s artwork and attributes. Today’s studio numbers are working labels, not blockchain-issued tokens.

1. 01

   Curate & balance

   Finish the kept set and its numbering before minting.

2. 02

   Publish the mapping

   Prepare one metadata record per character, with its image and attributes.

3. 03

   Mint & resolve

   The chosen contract issues IDs that resolve to the agreed metadata mapping.

The intended final range is #1–#10,000. A sequential assignment is one possible design; any reveal offset or random assignment must also be specified and tested before launch. Token IDs are unique within a contract, not across every NFT project.

The blockchain, token standard, contract, mint price, launch date and assignment/reveal method have not been finalised. No deployed mint contract or final on-chain mapping is being presented here.

Proposed · not yet deployed

The proposed provenance process is a commitment to the final artwork and metadata before minting begins. Think of it as a sealed inventory: something everyone can check against what is eventually revealed.

• Freeze the final set: confirm the retained pieces, token mapping, images and metadata after curation.
• Publish a verifiable commitment: hash each final file and publish an ordered manifest with an aggregate cryptographic digest before minting. Publish the exact verification method too.
• Make the files retrievable: evaluate content-addressed storage such as IPFS, with maintained pinning, or a suitable permanent-storage service. Storage choices and funding remain to be confirmed.
• Verify the release: compare the published files and contract mapping against that commitment, and disclose whether metadata can still change.

A hash helps detect changes; it does not keep files online, prove fair randomness, or make a contract safe. An IPFS address is content-addressed, but continued availability still needs hosting or pinning.

No final provenance digest, permanent-storage commitment, metadata freeze or independent contract audit is claimed at this stage.

Before a mint opens, the aim is to publish the details that let collectors and partners make an informed decision—not ask them to take the beach vibes on trust.

These are launch-readiness goals, not completed milestones or guarantees of future utilities. This page will evolve as decisions are confirmed.