Ponzi / MSTR
fee 0%- Swap Ponzi → MSTRno liquidity below the price
- Swap MSTR → Ponzihook takes 1%
- Add, then remove liquiditycame back whole
pool 0x2fa4dc99f5df9895742573df11c0d6c9181861479f337c05f8878628ed668e4b
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
4 pools use this hook, the first one 51 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 1% 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 claim.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 50 days.
Measured at block 93,269,769. 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 0x2fa4dc99f5df9895742573df11c0d6c9181861479f337c05f8878628ed668e4b
pool 0x2217b3f897a71032c3a950164b5c558ec02c97f56c4615702987eb65be007fdc
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.