JPT / NFS
fee 0%- Swap JPT → NFShook takes 0.75%
- Swap NFS → JPThook takes 0.75%
- Add, then remove liquiditycame back whole
pool 0x3a6e5673c9a02b89f2b93773cbb9c50e28c39a02abc48e64b0817e1127a05d30
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 29 d ago.
The address enables after swap returns delta. The hook is allowed to take; the next two checks measure whether it does.
It takes 2.75% of each swap on top of the pool fee.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0%, written in the pool key.
No owner() but it has collectProtocol, collectCreator, transferAdmin.
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,393,426. 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 0x3a6e5673c9a02b89f2b93773cbb9c50e28c39a02abc48e64b0817e1127a05d30
pool 0x238cc7faeee9fbb131f6733731d76e0a556a8822fc85e03512b0aff87aacef82
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.