PACK / WOLF
fee 1%- Swap PACK → WOLFhook takes 1%
- Swap WOLF → PACKhook takes 1%
- Add, then remove liquiditycame back whole
pool 0xbc3d62543bd4b28c15338cc9ec99fa3687f54a4778465d3ac62a62f477068131
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
3 pools use this hook, the first one 65 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 1%, written in the pool key.
Owned by 0x49365aB6cA08b38191fBD31F409C3AFfc59121F2. Owner-style functions: transferOwnership, setRegistrar.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
3 pools over 65 days.
Measured at block 93,363,063. 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 0xbc3d62543bd4b28c15338cc9ec99fa3687f54a4778465d3ac62a62f477068131
pool 0x5d9e230411a7e98b6f6cb943932017cdc82a80f33c341f783a984946911eb528
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.