ETH / OPTIMUS
fee 0.05%- Swap ETH → OPTIMUSrefused: error 0xcdb38c1b
- Swap OPTIMUS → ETHrefused: error 0xcdb38c1b
- Add, then remove liquiditycame back whole
pool 0x926f8eb0a5c6ed510f830bc17c581ad061a2ea1ab0198f87509cb5590285f39d
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
17 pools use this hook, the first one 51 d ago.
None of the permissions that let a hook take from swaps or from LPs are switched on.
Every swap through it was refused: error 0xcdb38c1b. Only an approved router may get through.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0.05%, written in the pool key.
Owned by 0xc366eE60E964d7F03FdC2496F88eD71B935d6CCf. Owner-style functions: setAllowed, transferOwnership.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
17 pools over 51 days.
Measured at block 92,997,980. 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 0x926f8eb0a5c6ed510f830bc17c581ad061a2ea1ab0198f87509cb5590285f39d
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.