ETH / RESERVE
fee 0.01%- Swap ETH → RESERVErefused: error 0xcdb38c1b
- Swap RESERVE → ETHrefused: error 0xcdb38c1b
- Add, then remove liquiditycame back whole
pool 0xb0e4f77a5bc0b3f90a9980654f36be4b7a791d4dc2711ffa6b9f2c96a1e98af5
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 64 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.01%, written in the pool key.
Owned by 0xdA1E40A237eEa3c4ACf97071Ae51E9a86cfc50A1. 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 63 days.
Measured at block 92,972,539. 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 0xb0e4f77a5bc0b3f90a9980654f36be4b7a791d4dc2711ffa6b9f2c96a1e98af5
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.