The law of the anvil.

01The forge

The Forge is a contract with an immutable list of hook patterns: five at launch, each one already written, verified and immutable. A toll, the plainest fee on a swap. A decaying snipe tax, high in the first blocks and fading to the toll, so the first buyers pay for their speed. A tally counter, where every buy cuts a notch and the N-th opens a pot. A bid wall, a wall of bids under the price that only ever moves up. A tick, where orders pile up for a few blocks and clear at one price.

forge(pattern, params) deploys an instance of the pattern with its parameters frozen, at an address mined for its permission bits. A Uniswap v4 hook declares what it does in the low bits of its own address, so deploying one means finding a CREATE2 salt whose result carries exactly the right bits. The Forge does that mining for you. It is the first of the three things the anvil actually sells; the others are the verified code and the registry.

Forging carries no fee and pays the anvil nothing. There is no fee on creation, no curve, no listing, no discovery page. What you pay is the gas of the deployment, and what you get is a hook address you could not have mined for free.

02The cut

Every instance carries a share of its own toll, fixed by the pattern at the forge and immutable from then on. On every swap of a forged pool, the hook sends that share to the Anvil contract, in the quote asset of the pool. The rest of the toll follows the pattern's own rule, exactly as it would without the anvil.

The cut is a scalar per swap with no address attached, which keeps it clear of the oldest trap of v4 hooks: the sender a hook sees is the router, not the buyer. Patterns that do record an address, the tally counter for one, carry their own router requirement, written in their own law.

A pool with no volume sends nothing. The anvil earns from usage, and from nothing else.

03The pool

A forged pool is an ordinary pool of the PoolManager with a hook from the forge. Its creator decides its pair, its liquidity, its lock. The anvil imposes nothing beyond the cut, and it can touch nothing: it cannot pause the pool, drain it, or change what its hook does.

A hook from the anvil is a verified rule, not a label. The anvil does not judge the tokens that use it. A pool can run a flawless toll hook and still be a bad idea, and this page says so in plain words: a verified hook says nothing about the token that carries it.

04The buyback

The Anvil contract has one job: convert what it receives into $ANVIL on the $ANVIL pool, and send what it buys to the dead address in the same transaction.

It does this at a bounded pace, set at deploy: at most a share of its balance per window of blocks. Not a wall of buys, a drip that anyone can see coming. A bot can buy just before a window closes and sell just after; what it gains is bounded by the size of the buyback, which is bounded by the pace. That is the price of a buyback nobody can accuse of painting the chart.

What the anvil buys never sits anywhere: bought and burned in one transaction, to an address nobody holds the key to.

05Nothing for anyone

The Anvil contract has no withdrawal function, no owner, no pause, and no destination other than the $ANVIL pool and the dead address. Nobody can point its balance somewhere else, and nobody can stop it. The team keeps no share of the cut, and the list of patterns cannot be edited: adding one is a new Forge contract, next to this one, not a change to it.

Nothing on Anvil is ever paid to anyone. The cut goes to a contract, the contract buys, the buy burns.

06The registry

Every forged pool, its pattern, its frozen parameters, the cut it has paid and the total the anvil has burned are readable in the contracts. This site is written to read like that registry, and the bench on the front page is a working model of it, running on its own numbers.

The first pool in the registry is the anvil's own: the $ANVIL pool is forged on the Forge itself, with the toll pattern, so the anvil's own market pays the anvil like every other.

07What the contracts enforce

• I1 · A forged instance cannot be changed: not its cut, not its parameters.
• I2 · The anvil's cut leaves the Anvil contract only towards the $ANVIL pool, and what is bought leaves only towards the dead address.
• I3 · The buyback never exceeds the bounded pace per window of blocks.
• I4 · No address has any right over the Anvil contract: no owner, no withdrawal, no destination that can be set.
• I5 · The list of patterns is fixed at deployment. Adding one is a new Forge contract, not a change to this one.
• I6 · A forged pool stays an ordinary pool of the PoolManager: the anvil can neither pause it, nor drain it, nor touch it.

08What can go wrong

The copy. The hooks are public. Nothing stops anyone from redeploying one without the cut. This is accepted: the anvil sells the mined address, the verified code and the registry, not a secret. If the cut is well calibrated, copying costs more than paying it: mining a salt, reading the code, auditing the fork, and losing the wall.

A pattern with a flaw. An error in a pattern is an error in every one of its instances, and instances are immutable. That is why the list is short, why each pattern is written in full before it is offered, and why the audit comes before the first forge. A well-known liquidity hook on v4 lost a great deal to a rounding error despite two audits; every pattern here rounds in favour of the protocol and refuses outside liquidity wherever its economics depend on it.

Front-running the window. Buy before the buyback, sell after. It is possible, it is bounded by the pace, and it is said here rather than hidden.

A forged pool that is a scam. The anvil does not judge the tokens that use it, and a hook from here is not a label. A verified hook says nothing about the token that carries it.

Volume that does not come. Without active forged pools, nothing burns. The token is worth only the use of the forge, and the site shows that number first rather than hiding it.

The legal weight. A token whose value follows the usage of a service, and that burns with it: light in appearance, strict in vocabulary. Counsel qualifies the buyback before launch, and every word of this site is chosen with that in mind.

The law is a page. The site can be wrong, or out of date. The contracts are the law, the explorer is the witness, and everything here is written to be checked against them.

09Parameters

Constants are fixed at deployment and published here. Until then, none of them has a value, and no number you may read elsewhere is ours. The bench on the front page runs on its own numbers and says so.

10Chain and venue

Anvil runs on Robinhood Chain, chain 4663, and every pool it forges lives on Uniswap v4 through the PoolManager at 0x8366a39CC670B4001A1121B8F6A443A643e40951. The $ANVIL pool is forged on the forge itself, and its protocol liquidity position is locked in a locker with no withdrawal function.

Gas is paid in ETH, at a gas price around 0.02 gwei on this chain. That is what makes the anvil's arithmetic invisible: a swap on a forged pool writes one thing more, the cut, and a drip buyback can run at every window without the gas making it ridiculous.

Explorer: robinhoodchain.blockscout.com. Contract addresses, the Forge, the Anvil contract and the $ANVIL pool, are published on this page and on X at launch, and nowhere else. Anything else is somebody else's.