- thd
- rewards
- tokenomics
- mechanics
A quiet day burns the supply
The rewards pot releases exactly one thousandth of itself every day for a thousand days, whatever happens. What the platform earned that day decides only who receives it — the people using the platform, or the fire. A weak quarter destroys supply instead of printing it.
Almost every token you have held released its rewards on a clock. So many per day, per block, per epoch, until the schedule ran out. Whether the product worked that day changed nothing: the tokens came out regardless, and the weeks when the platform was quietest were exactly the weeks the emission arrived with nobody wanting it. Weak revenue and heavy sell pressure show up together, which is the worst possible pairing and the most common one.
The rewards pot here — Spoils — inverts that. The amount released is fixed and cannot be moved by anyone. What the platform earned decides only who gets it.
Built, not yet live
Everything below is written into the contracts and none of it is running. There is no schedule under way, nothing has been released and nothing has been burned. This describes what the mechanism does, not something you can go and use today.
The rule, in four lines
daily amount = pot ÷ 1000 fixed, every day, whatever happens
to the wheel = 20% of the daily amount always, before anything else
to users = the other 80%, scaled by (that day's protocol fees ÷ 2 ETH)
the shortfall = half to the wheel, half BURNED
That is the entire economic rule. It is one function on one contract, and it takes no arguments beyond the day being released.
The pot is the Spoils allocation: 11% of a fixed one-billion supply, so 110,000,000 THD, and a thousandth of that is 110,000 a day for a thousand days.
The daily figure is fixed the moment the schedule starts, from whatever the vault holds at that instant — there is no setter for it afterwards. Anything that arrives later is not lost and does not extend anything: the thousandth release pays out the entire remaining balance rather than one day's share, so the last day is where the division's dust and any late arrival both leave, by the same audited path as every other day.
What each day looks like
On a 110,000 daily amount:
| That day's protocol fees | To users | To the wheel | Burned |
|---|---|---|---|
| 2.0 ETH or more | 88,000 | 22,000 | 0 |
| 1.5 ETH | 66,000 | 33,000 | 11,000 |
| 1.0 ETH | 44,000 | 44,000 | 22,000 |
| 0.5 ETH | 22,000 | 55,000 | 33,000 |
| 0.0 ETH | 0 | 66,000 | 44,000 |
The three columns always sum to the same number. That is the property worth staring at: a day on which the platform earned nothing releases exactly as much as a day at the ceiling. It simply sends none of it to users.
The schedule cannot be stretched
A quiet platform does not pause the release, slow it down, or leave an overhang hanging over the market for later. It finishes in a thousand days either way. The only thing performance changes is how much of it survives.
Underperformance destroys supply instead of dumping it
Hold a fee level for the whole thousand days and the inversion becomes the headline. Each row below is its row in the daily table above, multiplied by a thousand:
| Fees held for 1000 days | Reaching users | To the wheel | Burned | Burned, as a share of total supply |
|---|---|---|---|---|
| 2.00 ETH a day | 88,000,000 | 22,000,000 | 0 | 0.00% |
| 1.50 ETH | 66,000,000 | 33,000,000 | 11,000,000 | 1.10% |
| 1.00 ETH | 44,000,000 | 44,000,000 | 22,000,000 | 2.20% |
| 0.50 ETH | 22,000,000 | 55,000,000 | 33,000,000 | 3.30% |
| 0.00 ETH | 0 | 66,000,000 | 44,000,000 | 4.40% |
Nothing about this is a forecast. It is the same division performed a thousand times, and the only input that varies is a number the platform measured rather than chose.
A holder watching a bad quarter sees the supply fall rather than an unlock land. That is the opposite of what a holder normally gets to watch, and it is not a policy anyone administers — it is what the contract does when nobody does anything.
It is a real burn, and the contract proves it every time
There is a version of "burning" that is not burning: sending tokens to an address nobody holds the key to. The supply figure never moves, so every explorer, aggregator and market cap goes on counting tokens that can never be spent. The number on the screen is wrong for ever, which defeats the entire point of doing it in a weak quarter.
This burn calls burn(), reads totalSupply() before and after, and reverts the whole release if
the supply did not fall by exactly the amount burned. A burn that silently did nothing would look
identical to one that worked, so the contract refuses to report one it cannot prove.
Every rounding remainder in the division falls into the burn leg too, for the same reason: a wei-level bias towards destroying supply is the right direction when the supply figure is what holders are watching.
A weak day does not only burn. It buys activity
Half of each shortfall is destroyed. The other half goes to the Fortune Wheel, on top of the 20% the wheel receives every day regardless.
That is deliberately counter-cyclical. The wheel is the one thing on this platform reachable only by creating a launch or a market — so a swollen wheel is a standing incentive to produce exactly the activity the weak day was short of. The worse a day goes, the larger the prize pool sitting behind the thing that fixes it.
Nobody can change any of it
This is the part that makes the rest worth reading, because a schedule the platform can adjust is not a schedule, it is an intention.
The Spoils vault has no owner, no admin, no keeper, no pause, no upgrade path and no rescue function. There is nothing to renounce because there was never anything to hold. Every input is either fixed at deployment or read off the chain:
| Input | Where it comes from | Who can move it |
|---|---|---|
| The start | 24 hours after the liquidity pool is seeded, read from the pool's own contract | Nobody |
| The pot | The vault's own balance when the schedule starts | Nobody, once it has started |
| The daily amount | The pot divided by 1000 | Nobody |
| The day's fees | The fee contract's own daily measure, which counts verified revenue only | Nobody |
| The benchmark | Fixed at deployment | Nobody |
| Both destinations | Fixed at deployment | Nobody |
Releasing a day is permissionless. Anybody can call it, for any day that has closed, and it pays the same three amounts whoever calls — because there is no decision left to make. Days do not expire either: a day nobody released today is releasable in a year, at exactly the same three amounts, because both of its inputs were fixed the moment the day ended.
What performance cannot buy you
A strong quarter does not release the pot faster and does not release more of it. It releases the same amount, to people instead of to the fire. If you are modelling this as an emission that accelerates with success, you have it backwards.
What is still decided downstream, and what cannot be
The user share is handed to one splitter, which divides it between the battlepass, the Bands contest and the season standings. That division is settable — and it only ever takes effect from the next season, so nothing changes under a contest already running.
What that splitter can never change is how much THD entered circulation, because the burn already happened one contract upstream. Whoever operates the surfaces below, and whatever they are configured to pay, the supply consequence of a day was settled before they saw a single token.
Reading it yourself
None of this needs trusting a page. On the Spoils vault:
previewRelease(day)— what a day would pay, split three ways, without sending anything.RELEASE_DAYS,WHEEL_BASELINE_BPS,SHORTFALL_TO_WHEEL_BPS— 1000, 2000 and 5000. They are constants, so they appear on the explorer and no transaction can change them.BENCHMARK_WEI— the fee level at which the user pool reaches 100%. Read it rather than taking the 2 ETH above on trust; it is fixed per deployment.potAtStart,dailyConsumption,totalToUsers,totalToWheel,totalBurned— the running totals, which is the whole audit.
Every release emits the day, the fee figure it read, the three amounts, and the token's total supply after the burn. So the claim that supply fell is not something anyone has to assert. It is in the log, one line per day, for a thousand days.
The fees and payouts page covers where the protocol fees in the table above come from in the first place, and the risk disclosure is worth reading before any of this is a reason to hold anything.