Docs

An NTS-1 coin is a normal fungible token: a Token-2022 mint with one billion units and its own bonding curve, tradable from the first second. It is also member number N of a collection with a hard cap, because the mint carries the Token-2022 group extensions. The number, the cap, the seed and the traits live inside the mint. Nothing about identity is stored off-chain. The platform is the root collection; anyone can open a collection of their own, which is itself a numbered member of the root. (In the program, a collection is called a launchpad: a group that can host launches.)

Three Token-2022 extension pairs on the same account. Explorers that understand them show the number; our app duplicates it in plain metadata for the ones that do not.

The seed is sha256(group_mint ‖ member_number ‖ slot), computed by the program. Traits are chosen from the seed with fixed rarity tables (80 / 17 / 3 %), the same code in Rust and in TypeScript. The image is rendered from the seed on request; it is never a source of truth. The uri is deterministic: base + mint.

The number is not a counter in our program. It is the member_number Token-2022 assigns when initialize_member adds the mint to the group, and the cap is max_size, enforced by the token program. Two launches in the same slot cannot share a number: the chain serializes. Try it with a collection capped at 10.

Special numbers get a readable extra trait: #1 is “first”, repeated digits are “repdigit”, mirrors are “palindrome”, multiples of 100 are “round”. Just rarity you can read, no game logic.

One curve per monster, same formula for all: a virtual constant product. Parameters are copied from the config at launch, so a curve never changes after birth.

1 % on every buy and every sell, taken on the SOL side. The split is a config parameter the admin can change for future launches; each curve keeps the split it was born with.

A user collection is a group mint with its own cap (100 to 10,000), prefix, symbol and style, and it is a numbered member of the root. Its creator pays the rent, becomes the owner, and can transfer ownership later. The owner earns 0.30 % of every trade on members launched there.

Free launches cost rent. Every collection carries a budget of lamports: the backend pays the rent, the program reimburses it from the budget in the same transaction. No budget, no free launch (wallet launches still work). Anyone can top a budget up; expired launches give their rent back to it. The platform's exposure is exactly the budget of the root, nothing else.

A collection owner describes it in a sentence. Claude turns it into a style: a shape family (monster, dragon, robot, ghost), 34 colours and a 42-word vocabulary for the traits. The style is encoded into a compact string (under 560 bytes) and written into the group's metadata at creation, so every member renders with it, here or anywhere else that reads the chain. The rarity tables and the seed logic never change; a style only picks colours, shapes and names.

At launch the backend draws a 32-byte secret, stores its sha256 in the Launch account, and gives the secret to the browser once (and in the claim link, in the URL fragment, which never reaches a server). To claim, the wallet signs a transaction carrying the secret; the program hashes and compares. Losing the secret means losing the right to claim, which is why the site nags about copying the link. Three unclaimed numbers per browser session, ten per IP per day, a short cooldown between clicks.

No transfer hook, no graduation, no admin path into a curve. The program will be audited before any mainnet use; this is devnet.