Big congratulations to the @zksync airbender team for this milestone. At this point, I consider the battle for speed to be definitively won, and the top priority for zkEVMs should shift fully to security. To me that means formally verifying (i) equivalence of the arithmetization to the ethereum spec (ii) a hard maximum bound on (prover cost) / (amount of gas in block) (iii) security of the proof system itself

8130 is already the strong choice for native AA for validation only partial statelessness (VOPS). Validating an 8130 transaction reads only the Keystore (+world state). In contrast frames execute against the account storage (+world state) and require add on EIPs like 8369 to help manage. That gap matters for FOCIL + zkEVM verifier nodes + validation performance. 8130 goes further with fully stateless accounts! A transaction-scoped account combined with 8130's nonceless transactions means no storage writes outside of its interactions. Stateless, ephemeral accounts are an essential building block for private, uncensorable, no intermediary transactions on L1!

Let's go over what happens when you swap some ETH for USDC today: Your transaction gets picked up and packed into a block alongside a few hundred others. That block goes out to every node on Ethereum, which is thousands of machines scattered across the world. Every one of them executes your swap from scratch, start to finish, exactly as you did. Then they compare answers. Your one swap, run thousands of times over, so that nobody has to trust whoever ran it first. That redundancy is where the security comes from, but It's also the ceiling. The network can never do more work in a block than every single validator is able to redo on its own. Ethereum's roadmap changes this arrangement. Under the L1-zkEVM plan, a block arrives carrying a zero-knowledge proof that it executed correctly, and validators check the proof rather than re-running the contents. ⚙️ today → every node re-runs your swap ⚡ the plan → every node checks one proof Checking costs roughly the same whether the block held ten swaps or ten thousand. One thing had to become true before any of that was realistic. Your swap was confirmed in a single block, and blocks arrive every 12 seconds, so a proof of that block has to be ready inside the same window. The bar for real-time sits under 10 seconds. Pico Prism 2.1 proves 99.9% of Ethereum mainnet blocks in under 10 seconds, averaging 4.87. Learn more 👇

Ethereum Foundation Grades 62 Hegotá EIPs, Targets Quantum-Resistant L1 by 2029 The Ethereum Foundation’s Protocol Cluster published its Hegotá upgrade assessment and roadmap, grading 62 proposed EIPs. EIP-7805 (FOCIL, an anti-censorship proposal) and EIP-8141 (Frame Transactions, a core account abstraction proposal) were placed in the S tier as “must ship,” while 15 proposals were rated A tier as “expected to ship” and 28 were rejected. The Protocol Cluster also outlined research priorities through 2029, targeting quantum resistance across Ethereum L1’s execution, consensus, and data layers by December 2029, with fast finality, post-quantum security, privacy, state, and zkEVM identified as five cross-upgrade research areas.

For its entire history, Ethereum has stayed secure the hard way. Every validator re-runs every transaction in every block, and they all have to agree on the result. Luckily, the planned roadmap changes that. Under the L1-zkEVM plan, a block ships with a zero-knowledge proof that it was executed correctly, and validators check the proof instead of redoing the work themselves. ▶️today: every validator re-executes every block ▶️next: a proof is generated once, everyone verifies it ▶️unlocks: lighter nodes, faster validation, room to scale There's one hard requirement underneath all of it. The proof has to be ready before the chain moves on. Ethereum runs on 12-second slots, so proving a block has to finish in seconds, every single time, or validation falls behind the network. That's the exact problem we've spent years on. Pico Prism 2.1 now proves 99.9% of mainnet blocks in under 10 seconds, on consumer GPUs. Ethereum is moving toward verifying instead of re-executing. Real-time proving is what makes that future possible, and it's what we build. Learn more 👇

lowercase snarks Words like laser, scuba, radar began uppercase. LASER — Light Amplification by Stimulated Emission of Radiation SCUBA — Self-Contained Underwater Breathing Apparatus RADAR — RAdio Detection And Ranging When a technology matures and becomes reliable, trusted, commoditised, it earns the lowercase. Lean Ethereum is a bet on snarks, not Succinct Non-interactive ARguments of Knowledge. Post-quantum security. Provable soundness. End-to-end formal verification. Deep cryptanalysis. Real-time proving. zkVM programmability. Simplicity and elegance. All essential for the lowercase. All inevitable. Ethereum L1 has 10y uptime and $1T secured with hashes and signatures, our cryptographic workhorses. I believe in 100y uptime and $1Q secured with snarks, our cryptographic jet engines. * L1 scale — 10K TPS gigagas scale with real-time zkEVMs * L1 security — post-quantum security with snarked signatures * L1 privacy — Zcash-grade stealth with wormholes (eg EIP-7503) Shipping snarks is a cryptographic Manhattan Project, one the EF is investing tens of millions into: * verified-zkevm[.]org — formal verification * poseidon-initiative[.]info — deep cryptanalysis * ethproofs[.]org — real-time proving * proximityprize[.]org — provable soundness * zkevm.ethereum[.]foundation — enshrinement * pse[.]dev — privacy Step by step, the EF is evolving into a snark-first org: * cryptography team — driving soundness and cryptanalysis * snarkification team — driving formal verification * zkEVM team — driving protocol integration * Ethproofs team — driving real-time proving * PSE team — driving privacy * PQ consensus team — soon™ Believe in something magical. Believe in lowercase snarks.

It's been 210 days since Fusaka activated, and we're getting closer to the next fork: Glamsterdam. Since the Merge, Ethereum has shipped a fork every ~294 days on average. Shapella: 210 days Dencun: 336 days Pectra (pls don't remind me): 420 days Fusaka: 210 days Glamsterdam is shaping up to be one of the bigger forks. ePBS revamps the block validation pipeline while reducing trust assumptions. BALs bring parallelization to Ethereum, and repricing EIPs make sure we can keep scaling safely. On top of the headline features, we're also getting ETH transfers emitting logs, a SLOTNUM opcode, a deterministic deployment factory, larger contract code size, and more. Glamsterdam will scale Ethereum by around 5x, and with Hegota and a few more repricing EIPs, another 2–3x is within reach. At the same time, work on Hegota is already ramping up. Inclusion Lists (FOCIL) + Frame Transactions will be a great combo, and there are already 20+ EIPs proposed alongside the two headline features. Further out, zkEVMs are the next big theme. PQ Ethereum is also on the horizon, and there's already work underway to get the protocol ready for it. Before we get there, there are still things to do: revamp state and sync, improve RPCs, ship faster finality, shorten slots, add native privacy, and more. Lots of stuff ahead, but it's good to see Ethereum's roadmap starting to come together.