@[email protected]

Moving to Mastodon: @[email protected]

[Justin Drake @drakefjustin]

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.

[Catalin @catalinmpit]

If your employer does this, run fast and far.

[the finite physicist @FinitePhysicist]

A homemade particle collider! This collider accelerates electrons to nearly 1.5 eV before smashing them into carbon atoms (10 trillion times less energy than the LHC!)

[Correos @Correos]

¡Gracias de corazón! 💛📯

[Raido / Samū → NFC @RuneRaido]

Fuck it

NOR-way

[@[email protected] @lnsd_es]

@ReinaDeLosGatos @threadreaderapp unroll

[Abel Aparicio @abel_aparicio_]

Hoy, repartiendo el voto por correo en dos pueblos de la Cepeda (León), en uno fui a buscar al destinatario a la pista de petanca y en el otro al huerto. Digo esto para que defendamos el servicio postal público como algo nuestro. Ninguna empresa privada lo mimará más. @Correos

[Timoneda - #UnaTiraCadaDia @Timoneda]

Esta va dedicada a Esa Gente™
#UnaTiraCadaDia

[mmadrigal @SoyMmadrigal]

Lo que ha hecho Feijoo hoy es utilizar una técnica para debatir llamada Galope de Gish (literalmente) y más conocida como ametralladora de falacias
Consiste en lanzar en tu turnos varías de estas mentiras de tal manera que el oponente no tenga tiempo en su turno de desmontarlas

[Álvaro Medina @alvaro_medinas]

A estas alturas no entiendo que no haya una redacción junto al plató verificando los datos que lanzan los candidatos en tiempo real. Para cualquier ciudadano es imposible entender qué es cierto y qué no en este formato. #CaraACaraAtresmedia

[DEV Community @ThePracticalDev]

For a lot of experienced developers, these "rules" may seem pretty clear, yet I often come across code changes that don't follow these principles. Sometimes, I even find some that I've made myself!

#DEVCommunity
https://t.co/VaxRbenYas

[Cálico Electrónico @CalicoOficial]

Perdón, perdón, perdón, perdón.... #CalicoElectronico Las tiras de Cálico" ( https://t.co/HLx1wvtIpZ) y "Las tiras de Cálico 2" ( https://t.co/35o4UgberC) en @0xword #multiverso

[🚀 Maria Alvarez @ostraperlera]

Imagínate un país donde en los años 80 se privatizó el agua. Para ganar el apoyo popular, se ofreció a cada ciudadano comprar un trocito de la empresa de aguas privatizada. A cambio de invertir, tendrían el suministro de agua gratis, y siempre podrían vender sus acciones.

[JPA Buddy @JPABuddy]

Do not expose #JPA entities via REST API, use DTOs instead - it is a well-known best practice. @Baeldung provides a great explanation how to do mapping right: https://t.co/VGYERVCIaU.
@JPABuddy provides postfix auto-completion to make it joy: https://t.co/G7zMh0Jp8g.

[@[email protected] @lnsd_es]

@pepicrft @marvinhagemeist We also have German people and German speakers in Valencia 😜

[Jaime Gómez-Obregón @JaimeObregon]

La Administración puede ser un tractor importante para la industria tecnológica nacional. O un lastre para su desarrollo.

Publiqué este análisis sobre cómo la Administración induce a la #precariedad laboral en un sector que es estratégico para el país. 👇

[Marcin Juszkiewicz 🙃 @haerwu]

As I mentioned FOSDEM then have to remind my "How to survive FOSDEM" blog post:

https://t.co/n610OgbT38

Several people found it useful, some hints are from user submittions.

@fosdem

[Felix Geisendörfer @felixge]

How Often Does Go Preempt Goroutines?

The conventional wisdom says CPU-bound goroutines are preempted every 10ms, but this is wrong. #golang

[Sipeed @SipeedLab]

New Tiny #tinyML #AIoT module M0S coming out~
Based on BL616, WiFi6+BT5.2+Zigbee, 384MHz #RISCV RV32GCP, 4MB Flash + 512KB SRAM, and USB2.0 HS in tiny 10x11mm stamp module!
It would be <2$ ~