ETH / ROBOT
fee 1%- Swap ETH → ROBOTnothing taken
- Swap ROBOT → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0x78c43e7cf8f3fdcf6e82f5a45eb8ac1b28307093b8c89343507f79d1f2f977d4
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 28 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 1%, 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 28 days.
Measured at block 93,392,805. 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 0x78c43e7cf8f3fdcf6e82f5a45eb8ac1b28307093b8c89343507f79d1f2f977d4
pool 0xfa2e19891ae276863ad08d59a34fc39a2d111c8ac6d6e5928d8f9ac41abb5086
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.