Reporting window: November 9, 2026, 00:00:00 to November 16, 2026, 00:00:00 WITA (Asia/Makassar), end exclusive.

Hegotá lost its champion for shorter slots. On November 12, Barnabé Monnot withdrew Quick Slots from consideration for the fork. EthLabs committed its own resources to post-quantum readiness in 2027. The distinction matters: the team has made a choice about what to stop working on. Core developers still face a choice about what to build instead.

EthLabs distinguishes readiness from full capacity: it wants post-quantum consensus and a migration route for every account, even if an emergency switch would reduce throughput. Full throughput with post-quantum transactions and blobs is its stretch goal. Saulius Grigaitis proposed a different sequence: have validators sign votes both ways, keep BLS authoritative, and test post-quantum aggregation at mainnet scale before making finality depend on it. Watch which approach client teams choose to prototype: the two paths ask validators to trust the new aggregation code at different points.

Glamsterdam still needs a rule that binds a bid to one payload

The consensus specification now checks a revealed payload’s gas limit against the bid and its withdrawals against the post-state before forwarding the envelope. Previously, the payload timeliness committee could attest to seeing an envelope that would fail on import. These checks narrow that gap. They leave a separate question: how does a node know it saw the particular payload the builder bid on?

One proposal recomputes the execution block hash in the consensus client. Its alternative puts the payload’s SSZ root in the signed bid, leaving the execution engine to check the block hash. After the consensus call, Justin Traglia asked the November 16 testing call to settle the choice so a spec release could proceed. That decision, rather than the checks already merged, is the next release signal.

The same call also has an application-level question. Juicebox developer Jango submitted examples and asked which changes to the protocol’s guarantees developers would tolerate under Glamsterdam. The submission gives reviewers a concrete application to assess; it does not establish how broadly the problem applies. Watch whether reviewers answer Jango’s question about acceptable breakage, as well as whether they agree with the examples.

Sources and further reading