BTC / cbBTC
fee dynamic, now 0%- Swap BTC → cbBTCrefused: Not allowed
- Swap cbBTC → BTCrefused: Not allowed
- Add, then remove liquiditycame back whole
pool 0x7f173eae8051e1ca9ba3a439780dd8afff97f55f6e1d7cdfce097542f77b5c98
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
6 pools use this hook, the first one 35 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: Not allowed. Only an approved router may get through.
Liquidity added and removed in the same block came back whole.
Its pools use a dynamic fee that the hook sets before every swap. It stands at 0% now and can change.
Owned by 0xe23f864E6Ae8F86B5828cad0969E62Ed0B3eFDc2. Owner-style functions: transferOwnership.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
6 pools over 35 days.
Measured at block 93,173,898. 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 0x7f173eae8051e1ca9ba3a439780dd8afff97f55f6e1d7cdfce097542f77b5c98
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.