How it works
The whole mechanism fits on one page. Nothing in it is decided by a person or a model after launch: the rules below run on hourly snapshots of the chain.
A petal
A petal is a wallet that holds at least 0.01 % of the supply in 3 consecutive hourly snapshots. The dev wallet and program accounts (pools, vaults) never count. A wallet on its way there shows as a bud.
Each tree is drawn by code from these wallets, seeded by the coin's address: the same holders always give the same tree, to the pixel.
Five stages, five burns
The goal (300 petals by default, set by the creator) gives five thresholds. Reaching one sends one burn, pre-signed by the dev before launch, of a slice of the dev's reserved share.
| Stage | Reached at | Burns |
|---|
The reserved share is 25 to 100 % of the dev buy (50 % by default). The five slices add up to all of it.
Armed, burned, cancelled
- ARMED signed and waiting for its stage. Anyone can check the signed burn on the coin page.
- BURNED sent on-chain. Final.
- CANCELLED the dev used the slice's nonce or sold below the reserved share, so the burn can no longer land. It stays shown in red.
Big sells and missing hours
A sell above 0.5 % of the supply shakes petals loose for 10 minutes. It is only visual: nothing burned comes back. If an hourly snapshot is missing, that hour is marked and no stage can be reached on it.
The block-0 bundle
The creator may add up to 4 wallets that buy in the same block as the creation. It is all or nothing: either every transaction lands in block 0, or none does and nothing is created. Every bundle wallet and its share of the supply is shown on the coin page, with the result: LIVE — 5/5 in block 0 or NOT LAUNCHED — retry.
Fees and who owns what
The launcher's wallet signs the creation and the dev buy: the launcher is the creator on the venue. Hanami takes 0 % and holds nothing: no treasury, no vault, no site wallet. Trading fees are the venue's own: 1 % platform and 0.25 % pool, 0 % creator fee.
Questions
What is a petal?
A wallet that holds at least 0.01 % of the supply across 3 consecutive hourly snapshots. The dev wallet and program accounts never count. A wallet on its way there shows as a bud.
What happens at each stage?
The goal (300 holders by default) sets five thresholds: 10, 25, 50, 75 and 100 % of it. Reaching one sends the matching pre-signed burn: 10, 15, 20, 25 or 30 % of the dev's reserved share.
Can the dev take it back?
The dev can cancel an unsent burn by using its nonce or by selling below the reserved share. The coin page then shows that slice as CANCELLED, in red. A sent burn is final.
What does a big sell do?
A sell above 0.5 % of the supply shakes petals loose for 10 minutes. It is only visual: nothing burned comes back.
What if a snapshot is missed?
That hour is marked missing and no stage can be reached on it. Streaks freeze instead of resetting, so holders keep their progress.
Why launch here?
You stay the creator and sign the creation and the dev buy yourself. The site takes 0 % and holds nothing. Your burns are pre-signed and public from the first block.