ETH / NPSMKARB
fee 1%- Swap ETH → NPSMKARBnothing taken
- Swap NPSMKARB → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0x994fdfe1e15311519d670643c69454214225cb5baae5d7b812230cca9c7b754a
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 25 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 24 days.
Measured at block 93,420,571. 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 0x994fdfe1e15311519d670643c69454214225cb5baae5d7b812230cca9c7b754a
pool 0x7d7513c98f7d3a7bae48cfd95205c577c9782d61bcb73089279e80b5a7243baa
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.