thai

[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.

[liminal @Liminal1988]

Read This 3x

[thai @baddest_dev]

It feels like one of the things that used to rely on off-chain indexers is now being built directly into the node. And indeed, it’s implemented as a separate asynchronous layer independent from blockchain sync.

Taking this further — what if node software itself could support various production indexing needs as plugins?

[Nethermind @Nethermind]

Large-range eth_getLogs queries are slow.

Once queries span hundreds of thousands of blocks, response times increase sharply. Many timeout entirely.

Nethermind just shipped Log Index to fix this. Here's what changed ⬇️

[thai @baddest_dev]

@fakedev9999 etherfi moving to OP?

[thai @baddest_dev]

This was blowing up on CT yesterday so I had to try it.

My personal take:

- The "Web 4.0" framing & marketing was genuinely brilliant — interesting concept that caught everyone's attention.

- Building Conway first, then creating the Automaton that runs on top of it — that's a genius flywheel. Conway usage must have skyrocketed. (I went in a bit too deep into Conway myself. If you're thinking about trying it, start small.)

- Still testing it out, but it feels a bit buggy and not super polished yet.

[Sigil Wen @0xSigil]

I built the first AI that earns its existence, self-improves, and replicates without a human

wrote about the technology that finally gives AI write access to the world, The Automaton, and the new web for exponential sovereign AIs

WEB 4.0: The birth of superintelligent life

[thai @baddest_dev]

cool

[Alpin Yukseloglu @0xalpo]

new collab from @paradigm and @OpenAI:

evmbench is a benchmark and agent harness for exploiting smart contract bugs

a few months ago, the best models found <20% of critical, fund-draining @Code4rena bugs in our benchmark. today they find > 70%

[thai @baddest_dev]

@0xalpo this is amazing!

[Tomasz K. Stańczak @tkstanczak]

5 Steps to Make Ethereum Driven by LLMs
1/ Validator operators delegate to agents the decision-making on accepting/rejecting network upgrades and setting the parameters.
2/ EIP authors use LLMs to create and submit EIPs.
3/ EIP editors use LLMs to review and approve EIPs.
4/ All Core Devs use LLMs to moderate meetings and vote on EIP inclusion and spec changes.
5/ Client teams generate codebases from specs.
It is important for Ethereum to be the first chain to be LLM-driven; it is an advantage akin to being the first PoW chain. Ethereum has a natural advantage because it already has an existing spec that LLMs were trained on, and a very transparent governance process that LLMs can be trained on (all past ACD calls, EIP processes, open discussions) and participate in.

The EF recently hired tooling coordinators and established a dAI team. Between ACD moderators, tooling coordinators, Ethereum Cat Herders, EIP editors, and the dAI team, there should be a high-priority process on:
1/ Ensuring that agentic participation in the EIP submission process is simple and functional.
2/ EIP editors have tooling for AI review of all EIPs.
3/ There is AI support for real-time ACD moderation (connected to chat, analyzing the discussion content in real time, and making suggestions).
4/ Expanding https://t.co/gwjaDMpEGV over time to be a real-time, listener-context-aware broadcast of the Ethereum governance process.
5/ Establish a cross-client team of core devs that would work on an AI-generated client codebase driven by specs only. Such a client should be fully formally verified, test-covered, and developed in parallel to other codebases until it becomes a canonical client codebase.

[thai @baddest_dev]

@fakedev9999 btw there is no meaningful advance for programming language in a recent few years. actually nothing more to study

[thai @baddest_dev]

@dongheena92 가끔 예전의 낭만의 시절이 그립네요 (꼰대 발언)

[thai @baddest_dev]

@fakedev9999

[thai @baddest_dev]

@dankrad thanks for a great article!

[thai @baddest_dev]

Minimmit achieves consensus in a single round, unlike traditional PBFT which requires two rounds (prepare/commit).
It's a slight oversimplification, but you can think of it this way: 40% notarization ≈ prepare, 80% notarization ≈ commit.

The n ≥ 5f+1 requirement is a trade-off, but I think it's perfectly acceptable for modern blockchains. The consensus process is simple and fast — blocks can keep being produced with just 40% notarization, which directly improves block time and throughput.
However, since finality requires 80% notarization, validator uptime and stability become even more critical.

For blockchains running a permissioned validator set, this might be the ideal consensus algorithm.

[Dankrad Feist @dankrad]

I wrote an article explaining Minimmit consensus:

https://t.co/6tBJemHZAv

[Soubhik Deb @soubhikdeb]

Hear more on how @commonwarexyz is pioneering the field of blockchain infra engineering with their primitive of Deterministic Runtime.

Paraphrasing what @_patrickogrady said Deterministic Runtime:

"The motivation here is that when one is doing distributed systems development, often time you'll hit a bug and have no clue what happened. And it ends up taking days to reproduce the bug. Half the time you just give up and hope it doesn't happen again. Deterministic runtime enables you to reproduce the entire run of the system locally and get exactly the same error."

[thai @baddest_dev]

@TradeOnKaizen 🔥

[thai @baddest_dev]

@alocealoce_ @DaedalusRsch yeah interesting

[thai @baddest_dev]

@0xwhysomad @MitosisOrg @multiplifi so so haha

[thai @baddest_dev]

@0xwhysomad @MitosisOrg @multiplifi whysobear

[thai @baddest_dev]

@0xwhysomad @MitosisOrg @multiplifi how are u nowadays?

[thai @baddest_dev]

@0xwhysomad @MitosisOrg @multiplifi whysoenvy