WETH / YAKQA
fee 0.30%- Swap WETH → YAKQAnothing taken
- Swap YAKQA → WETHnothing taken
- Add, then remove liquiditycame back whole
pool 0xb9229b3bbbbb1225da95573208b59585a58f07c67bcc2a4ed60cca97e3dca617
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 20 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.
No owner and no admin functions found.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 19 days.
Measured at block 93,329,049. 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 0xb9229b3bbbbb1225da95573208b59585a58f07c67bcc2a4ed60cca97e3dca617
pool 0xa8e05665e0e21b4e603b376dde28cfad06cca768c192e66b790f8154e16f9684
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.