05 / The burn
It does not come back.
Where the token taxes that transfer, the difference between charged and landed is exactly its tax rate — and recording the charge would overstate the burn every time.
Status
Nothing is deployed. No factory, vault or ledger address exists on any chain, no transaction has been broadcast, and the repository carries no git remote. ./submission/check asserts all three.
06 / The burn
What lands at the burn address is less than what is charged.
A press costs a flat fee of the launched token, sent to 0x…dEaD. The launched token is taxed on transfer, so a fee can arrive smaller than it left — and totalBurned records what arrived. The difference is not a rounding artefact and it is not lost: the token holds the taxed part until it liquidates, and that liquidation is the same tax stream the vault is paid from. A farmer burning fees is buying the wage bill.
The burn / charged, and landed
Eight periods of presses at a flat fee of 12,000 DUST, accumulated. The upper line is what the pressers were charged. The lower line is what would land at 0x…dEaD if the token taxed every one of those transfers at its launch rate of 200 bps. totalBurned is somewhere in the band between them, and it is measured rather than assumed. Schematic: the periods and their headcounts are a worked example; the fee, the rate and the arithmetic are the launch parameters.
The band, on its own scale — 20× the panel above
- charged — fee × presses, reaching 864,000 after the eighth period
- landed, if the token taxed every one of those transfers — 846,720
- the band between them, in the lower panel — 17,280 tokens at the eighth period, and nothing at all for a press the token does not tax
This is also why the counter is a measurement rather than a sum of receipts. Reading the burn address either side of the transfer costs one extra balance read per press and is the only way the number can be right for both ends of the band above.