strawmapcast: the strawmap as a community object

The strawmap is EF Protocol's strawman roadmap for Ethereum L1: one visual of the upgrades under discussion, spanning forks through 2029 and beyond. Upstream it lives in a Google Drawing, maintained by EF Architecture and updated roughly quarterly.

strawmapcast renders the same map from data in a git repo instead:

• generated from YAML — strawmap.yaml is the source of truth, the site is just a renderer
• modified via PRs — anyone can propose a change on ethlabs-org/strawmap-data
• tracked via changelog — every change carries its rationale
• machine readable — strawmap.json at a stable URL for other tools
• linked to relevant resources — every box carries its EIPs and write-ups

Build your own version

Rough consensus is emergent; a roadmap in a decentralized ecosystem can't be official. So remix it:

• In the browser: hit “build your own version” on the map, move items between forks, add or remove upgrades. Your entire edit is compressed into the URL — sharing your roadmap is copying a link. Export the YAML or open a PR when you want to propose it upstream.
• As a git fork: fork the data repo and load it here via ?src=you/strawmap-data@your-branch.
• Compare: the diff view shows what moved, appeared, and disappeared between any two versions — canonical vs a fork, or between two revisions.

Reading the map

• Forks progress left to right: Glamsterdam, Hegotá, then placeholder names I* through L*, at a rough cadence of one fork every six months.
• Three color-coded layers: consensus (CL), data (DL), execution (EL), each organized by theme (goal: performance or hardness) and sub-theme.
• Dark boxes are headliners (the modern ACD process aims for one CL and one EL headliner per fork), light boxes are onchain upgrades, grey boxes are offchain, black boxes are north stars.
• Badges: EIP (has an EIP), SFI (scheduled for inclusion), CFI (considered for inclusion). 🤔 marks uncertainty about ever shipping.
• Arrows are hard technical dependencies or natural progressions.

Provenance and disclaimers

Seed data transcribed from the strawmap.org drawing, revision 2026-06-26, maintained by EF Architecture (Francesco, Justin, Thomas, Toni, Vitalik). Not affiliated with the EF. As upstream puts it:

• strawman: work-in-progress rough consensus
• EF takes: not authoritative or representative
• uncertain flag (🤔 emoji upstream): uncertainty about ever shipping upgrade

The strawmap is not a prediction; it is a coordination tool sketching one coherent path among many. This site adds one property: the sketch is now something the community can hold, edit, and argue with, one PR at a time. See also forkcast.org for the near-term ACD fork process.