Fuel is spent, not parked
One rule runs the whole economy, and it is arithmetic rather than policy: every launch costs $DONUT, and that $DONUT is split 70 / 20 / 10 the instant it is spent. Nothing on this plate is a market quote. The figures are one run of the simulator on the default fleet — the Yield Farmer preset, all-hours flying, a 30-day month against a 350.00M circulating float.
Across 445 launches flown by 9 hulls. Fuel is paid at departure, whether or not the hull comes back.
70% of the fuel bill, removed from the float and not recoverable.
One commander, one month, measured against the 350.00M opening float.
The 20% slice. It keeps circulating; only the 70% leaves for good.
FIG. 1.1The fixed fuel schedule, printed against the modelled month’s 13,868 $DONUT fuel bill. The split never varies by ship, sector, captain or session — it is the same 70 / 20 / 10 on every launch. Simulation output on design assumptions still being balanced, not a forecast.
Three destinations, one payment
Fuel is the only consumable in the game, and it leaves your hands permanently. Each launch splits the $DONUT it costs on a fixed schedule: 70% to a dead address it never returns from, 20% into the dividend pool paid to locked ships and NFT holders, 10% to the treasury that covers servers and RWA pool depth. Flying shrinks supply. That is the design premise, and the simulator shows what a month of it looks like.
Burned
Dead address 0x0000…dEaDSeventy percent of every fuel payment is transferred to a dead address and stops circulating. Nobody holds a key to it, so the transfer is irreversible by construction rather than by promise — there is no treasury vote, no multisig and no admin path that can bring those tokens back. Every launch is designed to make the float smaller than it was before the ship left.
Irreversible. Not recoverable by the team, the treasury, or anyone else.
Dividend pool
Locked ships and NFT holdersTwenty percent is routed to the dividend pool. It is claimable by commanders who keep hulls locked and by NFT holders in the fleet, distributed pro rata against locked weight rather than wallet balance, so the pool rewards fleets that stay in service instead of fleets that sit in a wallet. The simulator models your claim at parity: it assumes the rest of the field flies roughly as you do.
Claim size scales with locked hulls, not with how much $DONUT you hold.
Treasury
Servers and RWA pool depthTen percent goes to the treasury, which is specified to cover two costs: running the oracle and game servers that resolve expeditions against the US session, and holding enough depth in the RWA pool that stock fragments can actually be redeemed at the size the game issues them. It is an operating budget for an unbuilt system, not a war chest and not a marketing line.
The smallest slice, and the only one with recurring bills attached.
The end of the line
A burn is only a burn if the destination cannot spend. The 70% slice is specified to move to an address with no private key — the standard dead address, held by nobody, spendable by nobody, including us. There is no vote, no timelock and no upgrade path that reverses it, which is the only reason the deflation modelled further down this page can be treated as permanent rather than as a promise to behave.
Burn destination
No key existsNo token exists0x000000000000000000000000000000000000dEaDView on explorerExplorer for Robinhood Chain — the chain this project is targeting
70% of every fuel payment is sent here. No private key was ever generated for this address, so nothing sent to it can be spent, clawed back or voted out again. That is the point: the burn is unrecoverable by design rather than by policy, and it stays unrecoverable whatever the team later decides.
The link resolves on the Robinhood Chain explorer. Targeting a chain is a design decision and not a deployment: no token exists, no contract of ours is live, and nothing has been burned. Whatever balance the explorer shows at this address was put there by other people — none of it belongs to this project, and none of it is evidence that this design has shipped.
Robinhood Chain sits at L2BEAT Stage 0, the lowest of the three stages, and carries transaction filtering at the protocol level: an authorised party can register a transaction hash and the state transition function will force that transaction to fail, including a transaction force-included from Ethereum. Who holds that role, under what policy, and whether it has ever been used, we could not establish.
So read the guarantee precisely. Irreversible by construction describes the dead address itself — no key, no way back, whoever asks. It does not describe the operator’s powers, and it says nothing about whether a given transaction is permitted to land in the first place.
Concept in development · Nothing here is deployed and no tokens exist
What a month of flying removes
Supply pressure is a function of activity, not of announcements. The table below runs the same model across four preset fleets with every other input held at the default, so the columns are comparable; the chart then compounds the default fleet forward for twelve months, each month burning against the float the previous month left behind. Both are arithmetic on assumptions we are still changing.
| Preset fleet | Hulls | Launches / mo | Fuel / mo | Burned / mo | Of float |
|---|---|---|---|---|---|
| Starter HaulFour Harvesters in the index. Cheapest fuel bill on the board and nothing to think about. | 4 | 156 | 3.2K | 2.2K | 0.0006% |
| Yield FarmerHarvesters lifted by one Flagship, with a Cruiser working the whipsaw for $LONG. | 9 | 445 | 13.9K | 9.7K | 0.0028% |
| Void RunnerCruisers in the MSTR Void behind a Bear. Highest dispersion in the game. | 8 | 672 | 29.5K | 20.7K | 0.0059% |
| Whale FlagshipTwo Flagships and sixteen lifted hulls. Enormous fuel bill, every aura slot filled. | 18 | 1,020 | 34.7K | 24.3K | 0.0069% |
FIG. 4.1Per-fleet figures for a single commander, not protocol totals. Fuel and burn in $DONUT, one 30-day month, 350.00M circulating float, default flight window and uptime. Simulation output on design assumptions still being balanced — not a forecast.
FIG. 4.2Circulating float over twelve modelled months for ONE commander flying the default fleet: 350.00M opening, 349.88M closing (−0.033%), 116.5K $DONUT burned in total. Protocol-wide deflation would depend on how many commanders fly and how hard, which is unknowable for a game that does not exist yet — so read this as the shape of one fleet's contribution, not as a supply schedule.
One commander's fleet, compounded month over month at constant activity.
Down from 350.00M, against a 1.00B total supply.
Simulation output, not a supply schedule and not a price expectation.
The docket is the artifact
Every expedition prints a receipt. The docket lists each hull, the sector it flew, how many launches it flew and what those launches cost, then totals the fuel and applies the fixed split at the foot. It is deterministic by construction — no clock, no randomness — so the same fleet prints a byte-identical strip every time, and the eight-character check at the bottom is a real check on the lines above it.
The point of printing it is that a burn should be legible before it is trusted. Read the strip from the top: the hull codes and sector plates tell you what was flown, the launch counts tell you how hard, and the fuel column tells you what each line cost. Nothing is aggregated away — if a figure at the foot looks wrong, the line that produced it is directly above.
The BURNED stamp is overprinted across the fuel total once the split has been applied. In a built game it would be the hook for an on-chain reference: same lines, same check, plus a transaction to verify them against. This concept has no chain and no transactions, so the stamp records that the split was applied in the simulation and nothing more.
Docket figures are simulation output. No transaction has been made and no chain has been chosen.
Donut Strategy
Expedition Docket
REV 12 · Fuel Ledger
Simulation output. No transaction has been made and no chain has been chosen.
The 20% that comes back
The second slice is the only part of the fuel bill that returns to players. It is claimable by commanders who keep hulls locked and by NFT holders in the fleet, and it is distributed against locked weight rather than wallet balance — so a fleet that stays in service earns from it and a wallet that simply holds $DONUT does not.
Two things qualify a claim in the current design. A hull must be locked for the expedition month rather than idle or listed, and the claimant must hold the fleet NFT the hull belongs to. Locking is what the pool actually pays for: it is a fee on flying, redistributed to the commanders who kept flying.
The simulator models your claim at parity, and you should read that number with the assumption attached. Parity means it assumes the rest of the field flies roughly as you do — same mix of hulls, same uptime, same appetite for volatile sectors. Under that assumption your share of the pool comes back to the size of your own contribution, so the modelled claim equals the 20% you paid in.
That is an assumption, not a promise, and it is the single most load-bearing one on this page. If the field flies harder than you, the pool is larger and your share of it is smaller. If it flies less, your claim rises above what you paid. A real pool would also have to survive people gaming lock windows, which is a balance problem we have not solved. Nothing here entitles anyone to a payout.
Pool, modelled month
Parity assumptionReference price only — not a quote, not a listing, and not a claim that $DONUT trades anywhere.
The 10% with bills attached
The smallest slice is the operating budget. It is specified to cover two things and is deliberately not described as anything more: the servers and oracle that resolve expeditions against the US session, and depth in the RWA pool so stock fragments can be redeemed at the size the game issues them.
Servers are the unglamorous half. An expedition only resolves if something reads the closing tape, applies the sector and captain modifiers, and writes the result down — every session, on a schedule, whether or not anyone is watching. That is a recurring bill, and it is why the treasury slice exists at all rather than being folded into the burn.
RWA pool depth is the harder half. Fragments are only worth what they can be redeemed for, and a pool too thin to absorb a month of issuance turns a dividend into a queue. Sizing that pool against the issuance the simulator produces is open work; the number below is what the model routes to the treasury, not a budget anyone has committed to spending.
Reporting cadence is not set. We have not decided how often treasury balances and outflows would be published, in what form, or who would check them — and rather than invent a schedule for a system that does not exist, we are saying plainly that it is undecided. Tokenized equities are regulated instruments, and how this slice is held and reported will depend on rules we have not worked through.
Treasury, modelled month
Cadence undecidedOne commander’s contribution. Nothing is deployed, funded, or held.
Run it on your own fleet
Every figure on this page came from one fixed input. Change the hulls, the captains, the sectors and the uptime, and the burn moves with them — the simulator prints the same docket for whatever fleet you assemble, and shows you the month it would cost.
Donut Strategy is a game concept in development. Nothing described here is live, deployed, audited or funded, and every figure on this page is simulation output on assumptions still being balanced — not a forecast, and not a return anyone should expect.