1/ Latest Stateless Implementers Call #43: team updates, t8n self-fixtures, code-chunks-in-tree, BloatNet, and post-EIP6780 self-destructs. Thread 👇 #Ethereum #StatelessEthereum

In-protocol state expiry removes most of Ethereum's stale state, but it's hard to ship without good revive UX. With real-time proving, perhaps out-of-protocol may suffice. 👇 This article compares the approaches and why it matters for Ethereum’s future: ethresear.ch/t/state-expiry…

Probably only about 0.01% of users are running full nodes — it’s just too tedious for most people. But in theory, we can already run light clients with partial state in today’s world, meaning no reliance on full nodes at all. I’d be curious if the community wants this.

We’re tackling lots of interesting problems—come join the team! 🤗

We published an article on how we’re approaching zkVM benchmarking for Ethereum: zkevm.ethereum.foundation/blog/benchmark… Hopefully it’s a useful starting point for diving deeper into the technical details of this effort.

As a contract’s storage grows, SSTORE becomes more computationally expensive. Therefore, gas pricing should scale accordingly.

🔗 ethresear.ch/t/the-future-o… Most “self-custody” wallets rent truth from a few RPC gatekeepers. When they hiccup, they die. OOPSIE flips it: snap-sync + verified slices of your state. ⚡️ A new type of Snap Sync-based wallet which showcases some of Ethereum's upcoming problems!

1/ Latest Stateless Implementers Call #44 (Oct 20, 2025): team updates and compression-based state expiry. Thread 👇 #Ethereum #StatelessEthereum

This would significantly reduce contract deployment costs without compromising the performance of EL clients. No UX tradeoffs too.

Out fourth proposal for state expiry, inspired by EIP 4444.