Add Glamsterdam to roadmap & update carousel#17730
Merged
Merged
Conversation
mnelsonBT
requested review from
minimalsm,
pettinarip and
wackerow
as code owners
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
content 🖋️
GlossaryTooltip automatically parses from links of this format
wackerow
reviewed
Mar 10, 2026
Member
wackerow
left a comment
wackerow
left a comment
There was a problem hiding this comment.
Looks good overall! Left a review, mostly clerical stuff...
If you agree, can get those in, will review translations then this should be good to go
Comment on lines
+53
to
+71
| ### Headliner proposal: Enshrined proposer-builder separation (ePBS) {#epbs} | ||
|
|
||
| - Removes off-protocol trust assumptions and reliance on closed-source relays | ||
| - Enables L1 scaling by allowing much larger payloads through extended propagation windows | ||
| - Introduces trustless builder payments and encrypted transactions to anonymous builders | ||
|
|
||
| Currently, the process of proposing and building blocks includes a hand-off between block proposers and block builders. The relationship between proposers and builders isn’t part of the core Ethereum protocol, so it relies on closed-source, third-party software (relays), as well as off-protocol trust between entities. | ||
|
|
||
| The out-of-protocol relationship between proposers and builders also creates a ‘hot path’ during block validation that forces <GlossaryTooltip termKey="validator">validators</GlossaryTooltip> to rush through transaction broadcasting and execution in a tight 2-second window, limiting how much data the network can handle. | ||
|
|
||
| **Enshrined proposer-builder separation (ePBS, or EIP-7732)** formally separates the job of the proposer (who chooses the block) from the builder (who assembles the transactions), ‘enshrining’ this process directly into the Ethereum protocol to remove off-protocol trust. It also introduces the Payload Timeliness Committee (PTC) and a dual-deadline logic, with validators attesting to timeliness and data availability separately to maximize throughput. | ||
|
|
||
| <YouTube id="u8XvkTrjITs" /> | ||
|
|
||
| Separating the proposer and builder roles at the protocol level expands the propagation window (or the time available to spread data across the network) from 2 seconds to about 9 seconds. | ||
|
|
||
| ePBS reduces dependencies on extra third-party software and allows Ethereum to safely process much larger amounts of data (like more blobs for <GlossaryTooltip termKey="layer-2">Layer 2s</GlossaryTooltip>) without stressing the network. | ||
|
|
||
| **Resources**: [EIP-7732 technical specification](https://eips.ethereum.org/EIPS/eip-7732) |
Member
There was a problem hiding this comment.
No mention of MEV-Boost? If I understand correctly this basically removes the need for that, which is what most node operators are using to connect to relayers.
|
|
||
| Currently, the process of proposing and building blocks includes a hand-off between block proposers and block builders. The relationship between proposers and builders isn’t part of the core Ethereum protocol, so it relies on closed-source, third-party software (relays), as well as off-protocol trust between entities. | ||
|
|
||
| The out-of-protocol relationship between proposers and builders also creates a ‘hot path’ during block validation that forces <GlossaryTooltip termKey="validator">validators</GlossaryTooltip> to rush through transaction broadcasting and execution in a tight 2-second window, limiting how much data the network can handle. |
Member
There was a problem hiding this comment.
Would try to use standard quote marks to avoid bugs, esp with i18n, and for consistency
Suggested change
| The out-of-protocol relationship between proposers and builders also creates a ‘hot path’ during block validation that forces <GlossaryTooltip termKey="validator">validators</GlossaryTooltip> to rush through transaction broadcasting and execution in a tight 2-second window, limiting how much data the network can handle. | |
| The out-of-protocol relationship between proposers and builders also creates a "hot path" during block validation that forces [validators](/glossary/#validator) to rush through transaction broadcasting and execution in a tight 2-second window, limiting how much data the network can handle. |
|
|
||
| The out-of-protocol relationship between proposers and builders also creates a ‘hot path’ during block validation that forces <GlossaryTooltip termKey="validator">validators</GlossaryTooltip> to rush through transaction broadcasting and execution in a tight 2-second window, limiting how much data the network can handle. | ||
|
|
||
| **Enshrined proposer-builder separation (ePBS, or EIP-7732)** formally separates the job of the proposer (who chooses the block) from the builder (who assembles the transactions), ‘enshrining’ this process directly into the Ethereum protocol to remove off-protocol trust. It also introduces the Payload Timeliness Committee (PTC) and a dual-deadline logic, with validators attesting to timeliness and data availability separately to maximize throughput. |
Member
There was a problem hiding this comment.
Suggested change
| **Enshrined proposer-builder separation (ePBS, or EIP-7732)** formally separates the job of the proposer (who chooses the block) from the builder (who assembles the transactions), ‘enshrining’ this process directly into the Ethereum protocol to remove off-protocol trust. It also introduces the Payload Timeliness Committee (PTC) and a dual-deadline logic, with validators attesting to timeliness and data availability separately to maximize throughput. | |
| **Enshrined proposer-builder separation (ePBS, or EIP-7732)** formally separates the job of the proposer (who chooses the block) from the builder (who assembles the transactions), "enshrining" this process directly into the Ethereum protocol to remove off-protocol trust. It also introduces the Payload Timeliness Committee (PTC) and a dual-deadline logic, with validators attesting to timeliness and data availability separately to maximize throughput. |
|
|
||
| Separating the proposer and builder roles at the protocol level expands the propagation window (or the time available to spread data across the network) from 2 seconds to about 9 seconds. | ||
|
|
||
| ePBS reduces dependencies on extra third-party software and allows Ethereum to safely process much larger amounts of data (like more blobs for <GlossaryTooltip termKey="layer-2">Layer 2s</GlossaryTooltip>) without stressing the network. |
Member
There was a problem hiding this comment.
Yeah I think I'd recommend some mention of MEV-Boost in here to clarify.. just seems like an elephant in the room.
Copyedits Co-authored-by: wackerow <54227730+wackerow@users.noreply.github.com>
Collaborator
Translation Quality Review (Pre-Fix)PR: #17730 -- Add Glamsterdam to roadmap & update carousel SummaryThe Glamsterdam translations show decent baseline quality for prose and tone, but have systemic issues with technical terminology -- particularly the "state" polysemy problem affecting 8 languages where blockchain "state" was translated as political "state/government." The Marathi file contains an LLM artifact token ( Weighted average: 7.0/10 Quality Scores by Language
Universal Issues
Critical Issues Found
Reviewed by Claude Opus 4.6 |
- Fix "state" polysemy (8 langs): political -> blockchain - Strip <bos> LLM artifact token (mr) - Replace "LLM translation failed." literal (de) - Clean cross-script contamination (bn) - Fix meaning inversion centralization/decentralization (ur) - Convert GlossaryTooltip components to markdown links - Remove invalid *** horizontal rules - Fix "Github" -> "GitHub" brand casing (12 langs) - Fix stray space before fullwidth comma (zh-tw) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Add stripLlmArtifactTokens() to detect and remove <bos>, <eos>, <s>, </s>, <pad>, <unk>, <mask> tokens that leak from machine translation pipelines and break MDX compilation as unrecognized JSX components. - 9 unit tests (161 total passing) - Documented as pattern ethereum#33 in sanitizer research - Runs first in fix chain, preserves code blocks Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Collaborator
Translation Quality Review (Post-Fix)All critical issues from the pre-fix review have been resolved: LLM artifact token stripped (mr), MT pipeline failure string replaced (de), "state" polysemy corrected (8 langs), cross-script contamination cleaned (bn), semantic inversion fixed (ur), GlossaryTooltip components converted to markdown links, GitHub casing corrected, and stray spacing fixed (zh-tw). A new sanitizer function ( Remaining open items not addressed by these fixes: Weighted average: 8.6/10 (up from 7.0) Quality Scores by Language
Fixes Applied
Remaining Open Items
Reviewed by Claude Opus 4.6 |
- Lowercase "layer 2" (3 instances) and "denial-of-service" - Add second bullet to state-access gas cost update section Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
- Lowercase "layer 2" and "denial-of-service" where applicable - Add translated state-access gas cost bullet to all 17 langs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Add state-term and state-definition to all 24 non-English glossary-tooltip.json files. New sparse files for ar, bn, sw, ur. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
wackerow
approved these changes
Mar 12, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update roadmap carousel for Glamsterdam & Hegotá, and add Glamsterdam article
Description
This PR updates the roadmap carousel to reflect the latest planned Ethereum upgrades and improves the logic for how the active slide is determined.
Enhancements:
startIndexlogic. The carousel will now continue to highlight the most recently shipped upgrade for two months before automatically defaulting to the next planned release.displayDateproperty to theReleasetype to support fuzzy target dates (e.g., "H1 2026") on the carousel tiles, for before there are exact release datesGlamsterdam & Hegotá updates:
/roadmap/glamsterdam/; added a "Learn more" CTA button to the Glamsterdam carousel tile