TEST / MSFT
fee 0%- Swap TEST → MSFThook takes 1%
- Swap MSFT → TESThook takes 1%
- Add, then remove liquiditycame back whole
pool 0x84f83eb6546cf30d2c9cab08bad6268c82fac9a157a2c19f7475f21df66a025e
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
4 pools use this hook, the first one 60 d ago.
The address enables after swap returns delta. The hook is allowed to take; the next two checks measure whether it does.
It takes 1% on top of the pool fee.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0%, written in the pool key.
No owner() but it has sweep, skim.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 59 days.
Measured at block 93,268,094. A hook with an owner or a dynamic fee can behave differently later; scan again before a large trade.
A v4 hook's permissions are the last fourteen bits of its address. The PoolManager calls only what they switch on.
A small swap each way and a liquidity round trip, run through the PoolManager and this hook inside a call that is never sent. The pool fee is expected; anything else missing is the hook.
pool 0x84f83eb6546cf30d2c9cab08bad6268c82fac9a157a2c19f7475f21df66a025e
pool 0x0b5c3aec81108976c9cbe1d03e0a412de91e54991e73fd22840da5aa8f5b599d
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.