I bet many of the experts talking have never used EIP7702. You need signed authorization bro, can鈥檛 delegate if you don鈥檛 know the privKey or at least have access to it
skill issue. good for us tho
genuinely feel bad for the binance hacker. man spent months planning this. pulled off one of the biggest heists in crypto history. clean exit through tornado cash. probably already picked out the lambo
then some guy at tether pressed one button and now he's sitting on $1.5 billion he can't withdraw
welcome to being a binance user bro
For an attack this big, he could have code/delegated to a contract with the full flow to drain/launder the funds in 1 tx. Instead he delegated and only used a sweep function, allowing countermeasures to freeze them. So yeah, the attacker was a vibe coder or very lazy.
Replying to @0xQuit
On further inspection this may just be laziness on the attacker's part. Since they were also able to steal Bitcoin and Tron using normal transactions, it would seem logical that they do have enough access to Binance infrastructure to steal private keys directly or at least sign transactions. So the use of 7702 was strictly for convenience and the 50 sequential nonces just a fail-safe.
My LP positions made $600 in swap fees so far with this volume spike. How much liquidity? $0
All thanks to my hooks 馃獫
Uniswap V4 hooks are very innovative, but IMO they are still incomplete.
They only need a few changes to preserve composability across the ecosystem.
The biggest missing piece, IMO, is asset custody.
This creates a weird situation:
A pool can have real liquidity and still look like it has none to external agents.
Its price can also appear static because the PoolManager's internal liquidity and price state don't reflect what is actually available for execution.










