The law of Combo.

1What Combo is

$COMBO is a token with one pool on Uniswap v4, on Robinhood Chain, and one rule attached to that pool by a hook of our own. Every block that carries at least one trade extends the streak, and the longer the streak the larger the share of each toll that burns on the spot. One empty block ends it, and when a streak ends the whole reserve burns at once.

That is the whole product. There is no staking, no lock, no vote, no queue and no prize. Nothing is ever paid to anyone. The board is the oldest trick in the arcade, made honest: the number is a count, the lamps are a block, and the reserve is exactly what an empty block would burn right now.

2A block counts

A block counts if at least one trade of at least a minimum size, set at deploy, settled in it. Several trades in one block count once. The block, not the second, is the unit, because on this chain the block is the clock; a streak measured in seconds would be a streak measured by the sequencer.

3The streak

The streak is the number of consecutive counting blocks. A block that does not count sets it to zero. It is two words of storage, read by anyone at any block, and no function sets it to anything else.

4The share

Every trade pays the same toll, a fixed share of its size in the quote asset, set at deploy, the same for everyone at every moment. The share of that toll which burns on the spot is a step function of the streak: a base share at zero, one step higher at each published streak length, up to a cap; the steps, the base and the cap are set at deploy. What burns buys $COMBO on the pool and goes to the dead address in the same transaction. What does not burn accrues to the reserve.

5The break

The first trade after one or more empty blocks closes the streak: the whole reserve buys $COMBO and goes to the dead address, in that transaction, before its own toll is taken. Then the streak restarts at one and the share returns to base. Anyone may also call settle() to burn a closed streak's reserve before the next trade; it pays its caller nothing, and the site makes that call at the end of every empty block, so the burn on the board happens the moment the block goes by.

6Nobody breaks it

A streak ends because a block went by with no trade. No address can be pointed at, no address is paid, and the trade that happens to close it pays the same toll as any other. There is nothing to race, in either direction: extending pays nothing, and closing cannot be bought, because it requires everybody to stop.

7The reserve

One way in, the tolls. One way out, the dead address. No owner, no withdrawal, no destination that can be set. If nobody trades for a long time the reserve simply waits, and burns on the next trade or the next call, whenever that is. A long streak burns a lot on the fly and leaves a small reserve, so a great run ends quietly; a stop-start market leaves a big reserve and ends loudly. Both burn everything, on different schedules, which is why neither pattern can be farmed.

8The invariants

• I1 · The streak is exactly the number of consecutive counting blocks, and no function sets it to anything else.
• I2 · The reserve leaves only as burned $COMBO, and in no other form.
• I3 · The burning share is a published function of the streak alone, the same for every address.
• I4 · No address has any right over the reserve, and no address is paid for extending or for closing a streak.
• I5 · The toll is the same for everyone at every moment.
• I6 · The minimum size, the steps, the cap and the base share are fixed at deployment.

9What can go wrong

• Somebody keeps the streak alive with dust. They can, at the minimum size, once per block, and each of those trades pays a toll that burns. The cost of holding a streak open is a running burn, which is the mechanism working, not a leak.
• Somebody wants the break. They cannot buy it. It requires everybody to stop, which no single address can arrange.
• A gap in block production. If the chain itself skips, the streak dies through no fault of the market. Said here. The alternative, counting in seconds, would import the sequencer's clock into the rule, which is worse.
• The reserve grows large in a choppy market. That is the design, and the board shows the number rather than burying it, because a large pending burn is the reason to keep watching.
• Rounding on the share and on the buy. The first gate before anything opens, proven on adversarial amounts, with dust burned rather than kept.

10The chain and the pool

Robinhood Chain, chain id 4663, an Arbitrum Orbit chain settling on Ethereum, with the Uniswap v4 PoolManager and a hook of our own. $COMBO has its own pool on that PoolManager, and the protocol's liquidity position is locked in a locker with no withdrawal function.

The hook works in afterSwap: it compares the current block against the last counting block, either extends the streak or closes it and burns the reserve, then takes the toll and burns its share. The streak is two storage words and the share is a lookup on a fixed table, so the work is constant and a hot pool costs the same as a cold one. Sub-second blocks are what make this playable at all: on a chain with twelve second blocks a streak would be a calendar, not a game.

11The numbers

Every value below is written in the contracts at deployment and published here before anything opens. None of them can be changed afterwards, by anyone. The board on the front page runs the rule on its own numbers, chosen to make the rule legible in a minute, and its blocks slower than the chain's; the real ones are these.

12Addresses and risk

Contract address published here and on X at launch, nowhere else. Any address for $COMBO found anywhere else is not ours. There is no presale, no allowlist, no private round and no team allocation. The team keeps nothing, and settle() pays nobody.

$COMBO is not an offer of anything and may lose all of its value. Burning supply on its own sets no price, and nothing here promises one. A quiet market burns nothing. Not available where prohibited by law.