VG / SNDK
fee 1%- Swap VG → SNDKnothing taken
- Swap SNDK → VGnothing taken
- Add, then remove liquiditycame back whole
pool 0xf59a52f51c263e100f4ba699c2e3e224609fab322d43922f573f3d9747393dba
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
8 pools use this hook, the first one 31 d ago.
None of the permissions that let a hook take from swaps or from LPs are switched on.
A swap through it pays the pool fee and nothing else.
Liquidity added and removed in the same block came back whole.
A fixed fee of 1%, written in the pool key.
No owner() but it has ChangedUserData, settleAdapter.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
8 pools over 31 days.
Measured at block 93,113,374. 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 0xf59a52f51c263e100f4ba699c2e3e224609fab322d43922f573f3d9747393dba
pool 0xa9fc79535496cb369bcb83ba475b2a2d993b9dd23e21febdc504582ee52f2780
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.