How a race works
Every rule below is code you can run. The same engine decides on the server and replays in your browser, from the same readings.
The rules, in full
The launch
One Jito bundle carries, in order: the creation and dev buy on Stonks, the creation and dev buy on pump.fun, up to 3 block-0 buys from other wallets, and the tip in the last transaction. It lands whole or not at all. If it fails, nothing exists on either platform and you can retry; the slices you signed stay valid.
Your wallet is the creator on both platforms. pump.fun creator fees go to you. Stonks takes 0% on launch. The site takes nothing and has no wallet, no treasury and no vault.
The score
Each side's score is how much of its bonding curve has sold, in percent, read on-chain every 5 minutes. If a reading is late by more than a minute, the race is extended by the gap so no side loses unmeasured time.
The decision
At 24 hours the higher score wins. If the two are under 1 point apart, 1 hour of overtime follows. Still tied after overtime: the side with more holders of at least 0.01% of the supply wins. A side that completes its curve before 24 hours wins on the spot.
The burns
Before launch you choose a share of each dev buy for the race, 50% by default, and pre-sign 5 burn slices per side on durable nonces. The losing side burns all 5 at the decision. The winning side burns one slice each time its curve reaches 20, 40, 60, 80 and 100%. A slice can only burn tokens; it cannot send them anywhere.
Backing out
If you move the reserved tokens, the matching slices can no longer burn. They turn red on the coin page as cancelled, with the reason. Selling under your reserved share during the race forfeits that side.
What is never promised
A burn removes a known percentage of the supply. It says nothing about price, and nothing on this site does.
Check it yourself
Pick a race. Your browser downloads its readings and the engine, replays every event, and compares its result with the server's.
Waiting.