protocol rust dev, prev @nethermind, @ethereum protocol fellow @sigp_io, backend @madebyinvisible. looking for a role
🚀
Joined February 2014
- Tweets5.3K
- Following1.5K
- Followers2.1K
- Likes15K
Pinned Tweet
Privacy is shipping everywhere on @ethereum.
On one side, there's private reads. anon-rpc is live, which runs a hash-pinned worker in a sandbox, so the RPC never sees your IP, your address. Kohaku is the wallet piece, Railgun first, and it sends through the 4337 mempool instead of a trusted relayer. Privacy has stopped being a separate part and is getting integrated into the parts of the ecosystem where it previously leaked.
On the write side, a private withdrawal still has to land in a block, and today the relayer submits it. They pay the gas, see the proof, and the chain sees their signature on your exit. Frames (EIP-8141) are the proposed fix so a pool pays it's own gas against it's proof. FOCIL (EIP-7805) is the other half, a validator committee that can force eligible transactions in so a builder cannot skip them.
Frame transactions and FOCIL are both SFI'd for Hegotá. FOCIL is the consensus headliner, frames are the execution one. Together that is part of the private write.
So privacy is getting shipped and worked on considerably. Ethereum write path is still being worked on while the PIR is next in the read side after anon-rpc. And I am extremely bullish on all the upgrades happening around it!
Can't wait to go to @web3privacy cypherpunk congress tomorrow and have actual sessions and people addressing the privacy space and talk to devs working on this space!
Loved meeting @adiiHQ in person at IBW '26
And thank you for the book by @EliBenSasson as well 😋
@ishitaaaaw
Poulav retweeted
sadly 7702 is never beating the allegations now
for anyone who can still think, i'll explain this: the source of the exploit has nothing to do with 7702, it's a compromised pk; the fact the attacker signed with different nonces proves this; 7702 was simply the better way to send a tx
(this is almost akin to saying eip-1559 was used because the attacker used txn type 0x02 over 0x01
New details on how the $6.3 billion Binance hack likely occurred:
According to initial reports, hackers compromised a Binance engineer's laptop, gaining access to internal systems used to authorize withdrawals.
The attackers then:
1. Hijacked a Binance hot wallet using Ethereum's EIP-7702 mechanism
2. Redirected wallet transactions to a malicious smart contract
3. Transferred billions in crypto attacker-controlled wallets
4. Spread the stolen funds across multiple wallets and converted some assets into ETH to avoid freezes
The attack unfolded across multiple blockchains, with most funds drained in ~20 minutes.
~$3 billion of these funds have now been frozen, and Binance says it will cover all unrecovered hacking losses.
The full investigation remains ongoing.
Poulav retweeted
it's an overexaggeration. eip 7702 did help them throw in a number of guesses and one matched, but without it, they would still race nonces and might have been able to carry on the hack slowerm since they'd have to issue individual transfers. the root issue was still the signing access.
Poulav retweeted
-Hyperliquid: Today they dropped the biggest headline in crypto history.
-CZ: Hold my beer.
