ETH / MURA
fee 0.30%- Swap ETH → MURAnothing taken
- Swap MURA → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0x90c5b288c53421daaa58215c41a9376096fe2c5bcee9687531269eafcac8df28
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 75 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.
3 pools over 74 days.
Measured at block 93,327,275. 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 0x90c5b288c53421daaa58215c41a9376096fe2c5bcee9687531269eafcac8df28
pool 0x91bed0b312db7eb843ffa175fcd9d24ec228219a81c0f0df08924c4ed7eb5160
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.