Robinhood Chain (4663) · Uniswap v4
Five hooks, verified and immutable
Forged onto any pool, for a cut of its toll
Every pool forged here pays the anvil.
The bench
Pick a pattern, set its numbers, strike. The address is mined in the open until its permission bits fall right, the pool enters the registry, and from then on every swap on it pays the anvil. This runs the rule on its own numbers; the real ones are set at deploy. Here the cut is one fifth of a pool's toll, a window closes every eight seconds, and the anvil never spends more than a quarter of what it holds in one window.
One salt in about sixteen thousand lands on the right bits. The bench tries them for you.
holding 0.0 · at most a quarter per window: 0.0
Three pools are already on the wall, the first one being the anvil's own. Bots trade on them; every swap sends one fifth of its toll here. Forge yours to watch it pay.
| Pool | Address | Numbers | Volume | Cut sent |
|---|
A verified hook says nothing about the token that carries it. The anvil does not judge the pools that use it, and a hook from here is not a label.
How it works
Anvil sells the rule of the market, not a token. There is no curve, no list, no discovery page: a forge, a cut, a buyback, and a registry anyone can read.
Five hooks, all verified, all immutable, all already written: a toll, a decaying snipe tax, a tally counter, a bid wall, a tick. forge(pattern, params) deploys an instance at an address mined for its permission bits, with its numbers frozen.
Each instance carries a share of its own toll, fixed by the pattern at the forge. On every swap of a forged pool, the hook sends that share to the anvil, in the pool's quote asset. Nothing is taken at creation.
The anvil converts what it holds into $ANVIL on the $ANVIL pool, at a bounded pace: at most a share of its balance per window of blocks. What it buys goes to the dead address in the same transaction.
Every forged pool, its pattern, its numbers, the cut it has paid and the total burned are readable in the contract. No owner, no withdrawal, no team share. This site reads like that registry.
The law
Whatever the market does, whoever forges, these do not move.
A forged instance cannot be changed: not its cut, not its numbers.
The anvil's cut leaves the Anvil contract only towards the $ANVIL pool, and what is bought leaves only towards the dead address.
The buyback never exceeds the bounded pace per window of blocks.
No address has any right over the Anvil contract: no owner, no withdrawal, no destination that can be set.
The list of patterns is fixed at deployment. Adding one is a new Forge contract, not a change to this one.
A forged pool stays an ordinary pool of the PoolManager: the anvil can neither pause it, nor drain it, nor touch it.
Every number is fixed at deployment and published on the law page. The team keeps nothing.