WRAPPED / oSPOT
fee 0%- Swap WRAPPED → oSPOThook takes 1%
- Swap oSPOT → WRAPPEDhook takes 1.00%
- Add, then remove liquiditycame back whole
pool 0x1f026574db6d9076059f6b086f821b113b37d650e50aba7a54c1e0c01f4e766e
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
25 pools use this hook, the first one 43 d ago.
The address enables before swap returns delta, 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 setStrategy.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
25 pools over 43 days.
Measured at block 92,949,801. 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 0x1f026574db6d9076059f6b086f821b113b37d650e50aba7a54c1e0c01f4e766e
pool 0xc60bcca854e9b5742963ed937dacc6a72535be33ddd4dfb409db9dc7057ade6b
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.