ETH / CUM
fee 0.30%- Swap ETH → CUMnothing taken
- Swap CUM → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0x82ca7776b2dd91d47c27f38a709946ba4a495a2f234f571ae54ab3f7b0d842c1
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 34 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 0.30%, written in the pool key.
Owned by 0x77cB92c232137739452446c5712Fb0055a344c3D. Owner-style functions: setFactory, transferOwnership.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 34 days.
Measured at block 93,295,358. 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 0x82ca7776b2dd91d47c27f38a709946ba4a495a2f234f571ae54ab3f7b0d842c1
pool 0x4f1876f38c36398d8adeda8332258442d5d87fc84f7e4fe300bf02e299912328
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.