devlongs

separated attestation and proposal keys for safer validator operation Steady progress toward a post quantum-ready consensus client written in golang

After completing Devnet-3 work, we have started preparation for Devnet-4. Focus for this phase includes: 1). recursive PQ aggregation via leanVM 2). coalescing partial aggregates into one final aggregate per message 3). one-aggregate-per-message block semantics

manifesting single-slot confirmations... check it out at fastconfirm.it shipping soonTM

Currently rounding up devnet-3 work on @geanclient Devnet-4 coming up soon!

Happy birthday my mentor

@geanclient bunch of nerds, a room and a tv. good life

@fede_intern @geanclient Yes! Lambdaclass inspires a lot of the things we do.

The GEAN TEAM

one block at a time.

Excited to share some progress from the Gean side. We’ve now completed the implementation of the Devnet-2 specification. As part of this phase, a few notable improvements were introduced:

Big News!!!! 🥁🥁 Cohort V registration is now open! Blockfuse Labs is building at the intersection of Blockchain and AI. These two technologies are redefining global software engineering. We are not training for yesterday’s internet. We are building engineers for what’s next. Don't just watch, be part of it. Register here: blockfuselabs.com/bootcamp

Geanie

The recording of yesterday’s Community Call is now available. During the session, we provided key updates on our progress, including the successful completion of Devnet-1 and the achievement of multi-client interoperability.

@Ebunayo08 @geanclient Thank you sir

@devlongs_ @geanclient Great work!

I am excited to share that @geanclient has successfully completed devnet-1 and achieved multi-client interoperability. During devnet-1, Gean has been: • Proposing blocks • Attesting correctly • Broadcasting across peers • Syncing and operating alongside other clients

@Dv_nmd @geanclient Thank you my bro

@devlongs_ @geanclient Amazing job, Longs! Kudos, brother!

Join us this Friday at 4:30 PM (WAT) for our 1st Community Call. We’ll review our current progress and share what’s coming next. The call link will be posted in our Telegram group: t.me/geanclient Be there.

Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.

@geanclient This marks an important milestone, it validates the core state transition, networking, and consensus flow under real multi-client conditions. This is just the beginning. Next up will be working on post quantum signature aggregation.

Join us for Gean update and conversations

@geanclient is Go