ANVIL $ANVIL ETHEREUM · UNISWAP V4 NOT DEPLOYED · NO CONTRACT ADDRESS YET
anvil$ANVIL
Document 03 — tiers

Deeper
cuts
count more.

Burning gets you weight. Burning a lot gets you a multiplier on top of it.


03.1

The rule

weight = total burned by you × multiplier of your tier Your tier is the highest one whose threshold your lifetime burn has passed. Both halves only ever rise, so your weight only ever rises.
Cumulative, not per burn

Tiers are measured against everything you have ever forged, added up. Ten burns of a hundred thousand count exactly the same as one burn of a million. There is no reason to save up and no penalty for going in stages.

Fixed before launch

The thresholds and the multipliers are written into the forge book when it is deployed and there is no function anywhere that can change them afterwards — no owner, no vote, no upgrade path. Whatever the table says on day one is what it says forever.

What the code insists on

The first tier is always zero burned at 1.00×. Every threshold above it must be strictly larger than the one before, and every multiplier strictly larger than the one before. There can be between 2 and 16 tiers. A table that breaks any of those rules is rejected and the contract will not deploy.

Minimum burn

There is a floor on the smallest amount the book will record, so it cannot be filled with dust entries. The floor itself is chosen at deployment, and the contract refuses anything below 1 $ANVIL.


03.2

A table,
for the shape of it

The real table is decided when the contracts are deployed, and they are not deployed. Everything in this section is an example, chosen to show how the shape works — treat the numbers as illustration and nothing more.

Example only — not the live table

Example tier table · illustration · the live values are not chosen yet
TierLifetime burn requiredMultiplierWeight from 1,000,000 burned
001.00×1,000,000
11,000,0001.30×1,300,000
25,000,0001.75×1,750,000
320,000,0002.50×2,500,000

The last column is the same million tokens burned, valued at each tier. The multiplier applies to your whole lifetime burn, not only to the part above the threshold — crossing a line re-rates everything behind you.

0 1M 5M 20M LIFETIME BURN → 1.00× 1.30× 1.75× 2.50×
Figure 03.2 — example tier table plotted. The line has no downward step because the contract has no code that could draw one.

03.3

Move it around

Example only — uses the example table above

1,400,000 24,000,000

Both sliders are yours to move. Neither reads anything from a chain, because there is no chain to read: nothing is deployed.

Your tier
1
Multiplier
1.30×
Your weight
1,820,000
Share of the next distribution
7.05%
To the next tier
3,600,000 more

03.4

Why it cannot
go backwards

One door in

Weight changes in exactly one function, and that function can only be called by the token contract, and the token contract only calls it immediately after it has destroyed the tokens. There is no route to weight that does not go through a burn that actually happened.

Two rising inputs

Your lifetime burn can only increase. Your tier is the highest threshold that burn has passed, so it can only increase. Weight is the product of the two, so it can only increase.

Selling does nothing to it

Your balance is not an input. Sell the lot, transfer it, hold nothing at all — your weight is untouched, and you still collect on every distribution after it.

Time does nothing to it

There is no decay, no half-life, no epoch that resets and nothing you have to keep doing to hold your position. The contract has no concept of your weight getting old.

The honest caveat

Your weight cannot fall. Your share can, and probably will. Share is your weight divided by everyone's, and the denominator grows every time anyone forges. Getting in early buys you a bigger slice of the distributions that happen while the total is still small; it buys you nothing against the total ten years from now.

Next: the token itself →