JERK / MSFT
fee 0%- Swap JERK → MSFThook takes 1%
- Swap MSFT → JERKhook takes 1%
- Add, then remove liquiditycame back whole
pool 0x3cef012a0ea1035fe4fc4b0721137f65c8a9bd820bc31d7ef7f1c993bbb9d7e1
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,298,642. 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 0x3cef012a0ea1035fe4fc4b0721137f65c8a9bd820bc31d7ef7f1c993bbb9d7e1
pool 0xf4a496aeb25e4c0429be0b495d455374d56c175354ae30be322b6297b5dfa1c0
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.