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 23 d ago.
The address enables before remove liquidity. The hook is allowed to take; the next two checks measure whether it does.
No pool with liquidity to swap through yet.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0%, written in the pool key.
Owned by 0x59c233CcA646c191c9c6791Fa7D1eA9baf214b19.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 23 days.
Measured at block 93,399,062. 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 0x3c935f7d5f95359f4cd5d541619c25e6274d28cf96c3e9e2a7ba6a54c26cecd1
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.