c00k Exchangec00k

Station 03 · Split

Hand it over.
Let the chain say so.

Every launch says the team tokens are for the community, and saying it is free. A round is a contract that takes the tokens, names the second it pays out, and cannot give them back. Until that second the countdown runs and every holder can see whether they are inside the cut. When it lands, the burn share buys the token back and burns what it bought, the rest arrives in the largest holders wallets without anyone claiming anything, and a tenth of the round becomes $c00k. Each step leaves a receipt, and this is the ledger of all of them.

Commit a round

0rounds committed
0tokens, none of them ours to choose
0holders paid, without claiming
0rounds counting down

A round proves the transfer, the burn and the split. It does not prove the dev has no other wallet. The list is computed by the engine and its hash is written on the chain, so anyone can recompute it.

Ledger · newest first

read from the chain at block 0

The contract is written, tested in a call against the live chain, and not on the chain yet. The engine verifies it on every start once it has an address, and the first round appears here the block it lands. Until then this ledger is honestly empty.

What a round is

  1. 01The dev commits: the token whose holders receive, what they hand over, the amount, the burn share and what it buys, how many of the largest holders are paid, a floor, the moment it happens, a bounty for whoever executes it, anyone to leave out, and a note.
  2. 02The pool holds it. The site counts down, and the engine keeps the token’s balances live so any address can check its standing until the moment comes.
  3. 03At the moment, the engine executes it, or anyone after a day. A tenth of the round is bought into $c00k for the $c00k dev wallet, the burn share is bought into the burn token and delivered to the dead address, the executor takes the bounty, and the block becomes the snapshot.
  4. 04The engine ranks the balances at that block, leaves out pools, contracts of any kind (a wallet that only delegated its code under EIP-7702 still counts), the dead address, the token, the dev and whoever the dev listed, and sends each of the largest holders their share. Nobody claims. The hash of the list is written on the chain with the last batch.

What it proves, and what it cannot

Nothing in the contract can send anything back to the dev. It has no owner, no pause, no upgrade and no withdraw. What is committed goes to the dead address, to the listed wallets, to the executor as the bounty, and one tenth to the $c00k dev wallet. That tenth is a fee. It is written here and on every row so nobody reads the rest as free.

The one trusted step is the list, which the engine computes. Its hash is on the chain, the list is served beside the script that recomputes it from public data, and anyone can show whether the two agree. That is a reputation bond, not a proof, and it is written here so nobody reads it as more.

A round proves what was handed over. It does not prove what was kept in another wallet.