RT @ladislaus0x: 🧵This week’s EF Protocol research update covers new posts on. * Modelling delayed execution & ePBS in the context of short….

RT @SiLaDu: @yorickdowne @HyperledgerBesu already has parallel execution 😉 And enabled by default since 25.7.0. BA….

Let me hype you for Ethereum block space. We are just getting started, and this will be delivered with home nodes viable, all the way. 24 Gig gas. By 2030? I’ll not be shocked if it slips - and, it can be done. Ship forks with discipline every 6-9 months, and this happens.

Tentative Ethereum Fusaka timeline, summarized by @christine_dkim in her ACDE writeup for this week. “Client public testnet releases ~> Week of Aug 25.First public testnet upgrade ~> Sep 22 - Oct 3.Second testnet upgrade ~> Oct 6-10.Mainnet upgrade ~> Nov 5-12”.

RT @ViktorBunin: Yes, ETH's price action has been great, and will continue to be, but don't forget we have a network to fix. L1 is still t….

RT @philngo_: Today, @lodestar_eth posted its thoughts on the Glamsterdam headliner. We believe that EPBS gives the protocol an optimized p….

RT @potuz_eth: As promised, this is my reminder that ePBS is real now, well studied, implemented, and now supported by the majority of clie….

Check out the gas discussion ethstaker had with core devs. Great insights into the roadmap as well as takes on “why scale L1”. 3/3.

100M gas post Fusaka, and that’s just the beginning. Goal is 300M in 2026. Ethereum does the hard work, then steps on the accelerator. Without becoming a “data center chain”. Scaling L1 while keeping home nodes viable through smart design choices. 2/3.

Stoked for ePBS in Glamsterdam. This is huge for home stakers: 9s to get things done means moderate upload bandwidth remains enough. As well, it lays the foundations for zkEVM and proving. BAL means parallel execution becomes possible and cores get used. 1/3.

RT @rhadiARK: Yesterday, the Ethereum Foundation (EF) published a blog announcing intent to go all-in on integrating zero-knowledge (zk) in….

RT @rudolf6_: ERCs to significantly improve ethereum UX in next few months (simplified). - 5792: batch multiple clicks into one.- 7811: app….

RT @tcoratger: 1/ 🧵 Ethereum is moving toward integrating zkEVM proofs directly into L1 consensus. A 3-phase roadmap was presented during….

RT @lodestar_eth: Our next chapter: Transitioning from a pure JS client focused on browser compatibility to a performance-first, hybrid @Ja….

RT @stakesaurus: The first of the series is abstracted from a presentation by @yorickdowne, a professional node operator in the Lido Curate….

RT @potuz_eth: I know many affected parties have dismissed this topic for the most, but during Berlinterop it became fairly clear that clie….

RT @fockgeorgieboy: this is a huge misconception that needs to be addressed properly. let me explain why. i know most people don’t read my….

This stuff is a game changer. L2 wouldn’t feel like fifty chains any more, it’d behave like “one Ethereum” - you can know which L2 your counterparty is on, but don’t need to know.

This is based. But also - the entrepreneur who cleans my house *also* sells me her Cheesy Bites. I know this means nothing to you, and those are *chef kiss*. I couldn’t possibly fire her. Too many positive externalities.

If you’re the kind of 🤓who does Pectra MaxEB tools you need to know this: No, the withdrawal addresses do NOT need to match when consolidating. I think a lot of us read the spec wrong. “Ethereum: Too smart for your dumb ass”.