Launchpad
A token, a picture, a market
Tokens on baklava-testnet-5, what each one committed its logo to, and how much of its liquidity can never be taken out again.
There is no mint. A token's supply is fixed when it is created and the transition to make more was never written — not a restricted one, none. The most common way a launchpad token goes to zero is unavailable here, and that is not something this page adds: it is a rule of the chain, and you can check it by looking for the transition that is not there.
What has been made
Newest first, from the index, as of height …. The index says which ids exist and proves nothing; everything shown about each one comes from the node.
Make one
Four transactions, none of them signed here. This page never asks for a key or a recovery phrase, and you should not give one to a page that does — it composes the commands and you run them.
1 — create it
baklava token <symbol> <supply>
Ten BKLV to the treasury, and it does not come back. The id is derived from your address and the nonce that made it, so nobody picks it — including this page. The command prints it.
2 — upload the picture
curl -X POST --data-binary @<file> \ https://launch.baklava.network/l1/asset/token/<id>
Accepted only because the bytes hash to what the token already committed to. There is no account and no key: the ten BKLV was the filter, and it was spent in step 1.
3 — give it a market
baklava pool -a BKLV -b <id> baklava deposit -pool <pool id> -a <bklv krumb> -max-b <token amount>
A constant-product pool seeded from one side is a bonding curve — the price rises as the token side empties. There is no separate curve to graduate from; the AMM was always the thing.
4 — burn the shares, if you mean it
baklava burn -pool <pool id> -all
This is the only step that is a promise rather than an intention, and it cannot be undone. The shares move to an address nobody has a key for and the pool's total is left alone, so the liquidity behind them stays in the pool for ever. This page shows the result on every token above; it does not ask anybody to do it.
A token made before rule version 4 has no picture to have. The commitment is a field that arrived with that version, so a token sealed under an earlier one says before v4 rather than pretending its creator chose nothing. A chain reaches a version when ninety percent of its frozen set signals it and four epochs pass — and since there are no empty blocks, a chain nobody is using does not get there, because an epoch closes at a height and heights need transactions.
What is proved here and what is not. A token's symbol, supply, creator and logo commitment come from the node and carry a Merkle path to a signed header. The list of which tokens exist comes from an index, which proves nothing and can hide a row — it can never invent one, because every id on it is then asked of the chain. The pictures come from the launchpad and are hashed in your browser against the commitment before they are shown, so a store serving the wrong bytes says wrong bytes instead of a picture. A symbol is a label and not an identity: symbols are not unique and the id is what a token is.