Will the Base sequencer publish a decentralisation roadmap before the end of the quarter?

As of 2026-09-08, the probability of Base publishing a new, dated roadmap for decentralising transaction sequencing by September 30 is 30%, with a plausible range of 15 to 50. Base has already published broader decentralisation plans and reached Stage 1, but those achievements concern proofs and upgrade control rather than a scheduled transfer of sequencing authority. The answer depends on requiring a new sequencing-specific commitment; a broad reading that accepts existing Stage plans would produce a different result. 1 2

Forecast

• Probability: 30% (plausible range 15 to 50).
• As of: 2026-09-08, evidence cutoff and source access date.
• Resolves: 2026-09-30, by an official Base or Coinbase publication available by 23:59 UTC.
• Base rate: Two annual strategy documents, for 2024 and 2025, discuss decentralisation; neither establishes a measured frequency of sequencing-roadmap announcements. They support a qualitative prior only. 2 3
• What would move it: A dated proposal naming independent sequencing operators raises the forecast; a commitment only to faster proofs leaves it unchanged; an explicit deferral beyond September lowers it.

Why

1. The strongest positive evidence is delivery against earlier commitments. Base's Stage 1 announcement describes permissionless fault proofs and a security council, and identifies further proof systems and Stage 2 as next steps. That makes another technical publication credible, but its subject still matters. 1
2. Sequencing is a separate responsibility. Ethereum's rollup documentation distinguishes transaction ordering from validating state transitions, while the OP Stack derivation specification explains how the chain derives its history from Ethereum data. A roadmap can improve verification without allocating block production to independent operators. 4 5
3. The public engineering direction centres on proof improvements. Base's multiproof article explains a combined trusted-hardware and zero-knowledge approach, then sets out a future path toward full zero-knowledge proving. This is concrete decentralisation work, but the article's future-roadmap section does not supply dates for permissionless sequencing. 6

The 30% estimate is an editorial forecast, not a frequency calculated from historical releases. There are only 22 days between the evidence cutoff and the deadline. Publishing a plan is easier than deploying a new consensus arrangement, so the estimate is appreciably above zero. The missing ingredient is evidence of an imminent announcement that meets the narrow resolution test.

An illustrative decomposition gives the estimate some discipline. Assign a 50% chance to a substantive official decentralisation update during the remaining period, and a 60% chance that such an update includes both sequencing changes and a schedule. Multiplying those assumptions gives 30%. Neither input is an observed Base statistic. They explain the judgement and identify exactly which assumption new evidence should change.

Evidence for

• Base's 2024 strategy explicitly included sequencer redundancy and sharing its operational lessons. This shows that sequencer design has been within the team's published work programme. Redundancy can create prerequisites for a broader operator set, although multiple machines controlled by one organisation would not satisfy the forecast. 2
• The 2025 strategy made Stage 1 a stated annual objective alongside scaling and faster transactions. Treating decentralisation as an explicit strategic commitment increases the chance that future changes receive a public explanation. It does not imply a quarterly publication schedule. 3
• The earlier testnet fault-proof announcement named an additional requirement, adding the Security Council to upgrade keys. This is a useful example of Base explaining intermediate steps before completion. A similar publication naming sequencing milestones would count even if implementation extended beyond September. 7
• Current transaction-ordering documentation describes priority fees, arrival time and Flashblocks. That provides a concrete baseline against which a future operator or ordering change can be assessed. A qualifying announcement should explain which actor gains authority over this process and under what conditions. 8

Evidence against

• Stage 1 is not proof that sequencing has become permissionless. The official announcement's account of reaching the milestone concerns permissionless state proposals and changes to upgrade approval. Counting it as a new sequencing roadmap would erase the distinction at the centre of the question. 1
• The multiproof publication already gives Base a substantial decentralisation programme to explain. Its stated priorities concern proof security, efficiency and finality times. The inference is that the next update could continue that programme while leaving the sequencing operator unchanged. 6
• The published ordering rules explain how transactions receive priority, without announcing a timetable for selecting independent operators. Technical transparency is useful evidence about present behaviour, but it cannot substitute for a commitment to change control. 8

The strongest case against the forecast is therefore about timing and specificity. Base can make meaningful progress, release engineering documentation and improve the chain's security while this particular question still resolves no. A headline containing the word decentralisation is insufficient evidence by itself.

Assumptions and limits

• No external resolution rules are supplied with this question. This report interprets the quarter as Q3 2026 and requires publication after the question's August 10 listing. Earlier roadmaps are background evidence. If the intended question accepts any already-published plan about decentralisation, the premise is partly overtaken by the documents cited above and this 30% forecast should not be used.
• A qualifying publication must name at least one change to sequencing authority, describe implementation stages, and provide dates or calendar windows. A commitment to research the topic, a token announcement without operator changes, or a faster-proof schedule alone does not qualify. This is a proposed resolution convention, not an official rule attributed to Base.
• Sources were opened on September 8. Several official pages expose no reliable publication day in their rendered text. Their source entries therefore show access dates explicitly. An access date does not establish that the page was published that day, or that its wording has remained unchanged since the original announcement.
• Public documents cannot reveal an unpublished internal plan. The range reflects uncertainty about whether a qualifying publication occurs and about the reading of the question. It is not an interval for the eventual number of operators or the date of actual decentralisation.

What to watch

• Through September 30, inspect official Base engineering and strategy announcements for named sequencing participants, permissionless entry conditions and calendar milestones. These details would move the forecast sharply upward; architectural discussion without a schedule would have a smaller effect.
• At the deadline, preserve the publication itself and its timestamp. Compare the actual sequencing changes with the current transaction-ordering documentation. If only proof-system milestones appear, keep the outcome separate from this sequencing-specific forecast. 8

Sources

1. Base has reached Stage 1 Decentralization, Base, accessed 2026-09-08; publication day not exposed, https://blog.base.org/base-has-reached-stage-1-decentralization
2. Base's 2024 Mission, Strategy and Roadmap, Base, accessed 2026-09-08; publication day not exposed, https://blog.base.org/bases-2024-mission-strategy-and-roadmap
3. Base 2025 Mission, Vision, and Strategy, Base, accessed 2026-09-08; publication day not exposed, https://blog.base.org/base-2025-mission-vision-and-strategy
4. Optimistic rollups, Ethereum.org, accessed 2026-09-08; living documentation, https://ethereum.org/developers/docs/scaling/optimistic-rollups/
5. Derivation, OP Stack specification, accessed 2026-09-08; living specification, https://specs.optimism.io/protocol/derivation.html
6. Multiproofs on Base, Base Engineering, accessed 2026-09-08; publication day not exposed, https://blog.base.dev/multiproofs-on-base
7. Stage 1 Decentralization is Coming to Base, Base, accessed 2026-09-08; publication day not exposed, https://blog.base.org/stage-1-decentralization-is-coming-to-base
8. Transaction Ordering, Base documentation, accessed 2026-09-08; living documentation, https://docs.base.org/specifications/transactions/transaction-ordering