$FUSE · Robinhood Chain (4663) · Uniswap v4
The law of Fuse.
Everything the contracts do, in twelve articles. Nothing here is a plan or an intention: it is either written in the code at deployment or it is not on this sheet. Every number marked set at deploy is published here before anything opens, and none of them can be changed afterwards.
Article 01What Fuse is
$FUSE 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. A cord of a fixed length in blocks is lit at full. Every block that goes by takes one segment from it, and nothing has to be called for that to happen. Any swap of a minimum size or more, a buy or a sell, sets the cord back to full in its own transaction. Every swap pays the same toll into a reserve. When the cord runs out, the whole reserve buys $FUSE on the pool and sends it to the dead address, and a new cord is lit.
That is the whole product. Every rule of this kind has the same weakness: a dead market does nothing, and the page becomes a museum. Fuse inverts it. Trading keeps the cord long, silence shortens it, and when silence wins everything accumulated burns in one go. Both states of the market produce something worth watching.
Nothing bad happens at nought. No position is closed, no balance is touched, no address is charged. The word burn here means the reserve buys the token and sends it to the dead address, which is what it means everywhere else. The urgency on the front sheet is the urgency of watching a counter, not of a deadline.
The engraved line. It burns when you stop. Nothing else can stop it.
Article 02The cord
The cord has a fixed length in blocks, set at deploy. It is lit at full length at deployment, and at full length again at the start of every round.
It burns by itself. The remaining length is a pure function of the block number: the full length minus the blocks elapsed since the last relight, never below nought. Nothing has to be called for it to shorten, and nothing can slow it. There is no stored timer to keep alive and nothing that costs gas while nobody trades: the cord is arithmetic on the block number.
Blocks, never timestamps. On this chain the block is the clock. The cord is measured in blocks, the front sheet counts in blocks, and a cord measured in seconds would be a cord measured by the sequencer.
Article 03The relight
Any swap at or above the minimum size, set at deploy, sets the remaining length back to full, in that swap's own transaction. Several swaps in a block relight it once, which is the same thing. Direction does not matter: a sell relights the cord exactly as a buy does, and the hook does not read which one it was.
A swap under the minimum pays its toll like any other and does not relight the cord. The minimum is public, so there is nothing to discover and nothing to snipe. A relight pays nothing to anyone.
The cord never exceeds full. No function lengthens it beyond its fixed length, for anyone. A relight is a reset, not an extension.
Article 04The toll
Every swap pays the same toll, a fixed share of its size in the quote asset, set at deploy, accruing to the reserve. The toll is the same for everyone at every moment, on both sides, and does not depend on how much cord is left. There is no discount for relighting and no premium for trading near the end.
The toll is the only income of the mechanism, and the dead address is its only destination. Nothing is ever paid to anyone: not to the trader who relights, not to the caller who sparks the end, not to the team.
Article 05The end
When the remaining length reaches nought, the whole reserve buys $FUSE on the pool and goes to the dead address, and a new cord is lit at full length. The burn happens on the first swap after the end, or on a call to spark(), which anyone may make and which pays its caller nothing. The site makes the call.
The order of things. A swap that arrives after the end triggers the burn of the previous round before its own toll is taken, so its toll belongs to the new cord and never to the one that just ran out. This ordering is written in the hook and proven before deployment.
If the buy fails. A burn cannot revert a swap. If the buy on the pool fails for any reason, the reserve stays where it is and the round retries on the next swap or the next spark(); nothing is lost and nothing is stuck.
Article 06Nobody sets it off
The cord runs out because nobody traded, which is not an action any address can take. spark() pays nothing and can only be called after the length is already nought, so calling it is a courtesy and never a move.
Somebody who wants the burn can stop trading, but cannot stop anybody else, and one address abstaining is not silence. The end requires the whole market to go quiet, which nobody arranges. Somebody who wants to hold the cord alive can do so, one swap at or above the minimum per cord length, and pays a toll every time; every one of those tolls grows the reserve, so holding the cord open makes the eventual burn bigger.
Article 07The reserve
One way in, the tolls. One way out, the dead address. The reserve has no owner, no withdrawal, no destination that can be set, and no function that moves it anywhere but into $FUSE bought on the pool and sent to the dead address.
A market that never sleeps never burns and accumulates a very large reserve. That is the interesting long game: the longer the token stays busy, the larger the burn that quiet will eventually produce. The front sheet shows the reserve as a drum that fills, so that a token that has been alive for weeks shows a full drum and everybody understands what quiet would do.
Article 08Invariants
Six things that are true at every block, written in the contracts and proven before anything opens.
- I1. The remaining length is a pure function of the block number and the last relight, and no function extends it beyond full.
- I2. The reserve leaves only as burned
$FUSE, and in no other form. - I3. A relight is caused by a swap at or above the minimum, in either direction, and by nothing else.
- I4. No address has any right over the reserve, and no address is paid for a relight, an end or a
spark(). - I5. The toll is the same for everyone at every moment, whatever the remaining length.
- I6. The cord length and the minimum size are fixed at deployment.
Article 09What can go wrong
It reads as a threat. The largest risk in the design is not technical. A cord and a countdown look like a liquidation clock, and if a single line of copy suggested that anybody loses something at nought, the project would be mispriced from day one. So the front sheet says what happens at nought in one sentence, above the counter, in the same size as the counter, and this page says it again in Article 01.
Long silences early. In the first days the reserve is small and quiet is common, so the cord will run out often for very little. This is fine and it is good teaching: everybody sees the mechanism work before it matters.
Somebody holds the cord alive for ever. One swap at or above the minimum per cord length is enough, at a toll every time, and every toll grows the burn that quiet will eventually produce. It is the only defence the design needs.
Rounding. The toll and the buy are rounded so that dust burns rather than accrues to anyone; proven on adversarial amounts before deployment.
Article 10The chain
Robinhood Chain (4663), Uniswap v4, one pool on the PoolManager with a hook of our own; protocol liquidity locked in a locker with no withdrawal function. The hook works in afterSwap: compare the current block against the last relight; if the cord has run out, burn the reserve and relight; then take the toll and, if the swap is at or above the minimum, relight.
Two storage words and one comparison. The work is constant whatever the size of the trade, and the cord costs nothing while nobody trades, because it is arithmetic on the block number rather than a stored timer. Direction and size come from the swap itself, not from an oracle, so there is nothing off chain to be wrong about.
Article 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 cord on the front sheet 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.
| Number | What it does | Value |
|---|---|---|
| Cord length | the full cord, in blocks, the same for every round | set at deploy |
| Minimum size | the smallest swap that relights the cord, in either direction | set at deploy |
| Toll | paid by every swap into the reserve, in the quote asset | set at deploy |
| Supply and issuance | the whole supply and how it is issued | set at deploy |
The open questions, said plainly. The cord length alone sets the character of the token: short means it runs out most nights and the burn is a routine, long means it runs out rarely and the drum gets very full; it is simulated on real block traces before deployment and published here. The minimum size for a relight: too low and one bot holds the cord open for pennies, which is survivable but dull; too high and honest trades fail to relight, which reads as unfair. Whether the cord should shorten as the reserve grows: the current answer is no, because a cord whose length depends on the reserve is a cord nobody can state in one sentence.
Article 12Addresses and risk
Contract address published here and on X at launch, nowhere else. Any address for $FUSE found anywhere else is not ours. There is no presale, no allowlist, no private round and no team allocation. The team keeps nothing, and nobody is paid for a relight, an end or a spark.
$FUSE 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 market that never sleeps never burns. Not available where prohibited by law.