AFoundationQualification required
Feasibility & rule scope
Qualify the pinned fork-table comparison, wide-balance/revert behavior, and the scope of XDC-specific rules.
- Source estimate
- 19 Nov 2026
- Depends on
- Oracle access and owner decisions
05 / WORK IN THE OPEN
Where we go.
What it takes.
xOne qualification gates, seven competitor planning references, and a source-linked opportunity backlog. Evidence defines the next step.
RESEARCH SNAPSHOT / 14 November 20267 client references · 6 xOne gates · 12 proposed workstreams
OUR SOURCE PLAN
Evidence opens
the next gate.
These gates come from xOne’s execution plan. Dates below are that document’s estimates, not completion claims or release commitments. Each gate needs its own acceptance evidence.
How to read the estimates
The source plan starts on 16 November 2026 and applies a 1.5× calendar allowance. Dependencies, oracle access, soak time, and owner decisions can move the dates. No gate is marked qualified by this website.
Read the full source planBFoundationQualification required
Correctness & durability
Retain zero-mismatch fork-boundary replay, crash/restart/unwind evidence, and one regression per resolved finding.
- Source estimate
- 27 Nov 2026
- Depends on
- Gate A prerequisites
CQualificationQualification required
Sync & follower qualification
Qualify authenticated bootstrap, bounded resources, supported RPC parity, and live follower restarts on the declared networks.
- Source estimate
- 6 Dec 2026
- Depends on
- Correctness, storage, and retention evidence
DQualificationQualification required
Isolated producer safety
Prove anti-equivocation under rollback, restore, and failover; complete the declared 72-hour fault-injected devnet soak.
- Source estimate
- 6 Dec 2026
- Depends on
- Durable state and signer integration
ERolloutQualification required
Packaged release & rollout
Verify the exact artifact, authorize each public producer test separately, and complete the mainnet follower replay and 14-day soak.
- Source estimate
- 7 Jan 2027
- Depends on
- B/C/D evidence, artifacts, public-test authorization
QResearchQualification required
Post-quantum readiness research
Maintain crypto inventory, threat model, pinned standards, interface options, and measured costs. Research does not establish quantum resistance.
- Source estimate
- 24 Nov 2026
- Depends on
- Separate research track
Research stays separate. Track Q and the competitor-inspired backlog do not establish quantum resistance, protocol approval, or permission to activate a network change.
THE WIDER FIELD
Learn from
every direction.
All seven external clients in xOne’s comparison are covered. Published plans, working roadmaps, release evidence, and milestone records are labelled separately.
7 client references
RustPublished direction + releases
Reth↗
Direction published 8 April 2026
The 2.0 announcement sets out AOT/JIT execution and block-access-list-driven parallelism. Its architecture work combines state-root pipelining, tiered storage, and configurable retention.
RELEVANCE TO xONE · OUR INTERPRETATION
Profile root computation and retained data before evaluating a compiler or parallel executor.
An announcement records intent at publication. Later releases may supersede it; no current completion state is inferred here.
GoRelease-led planning evidence
Geth↗
Release stream reviewed 14 November 2026
Release notes document archive-history controls, database durability fixes, EVM execution improvements, and evolving network/fork support.
RELEVANCE TO xONE · OUR INTERPRETATION
Treat crash recovery, retained-history contracts, and fork-boundary tests as explicit release gates.
A separate current client roadmap was not verified. These are observed release themes, not a promised future schedule.
Go / C++Published roadmap · historical
Erigon↗
Roadmap published 28 March 2025
The published plan explores parallel execution, compact historical data, separable RPC/txpool services, account abstraction, L2 use, and a longer-term Erigon NeXT architecture.
RELEVANCE TO xONE · OUR INTERPRETATION
Evaluate hot/cold data, bounded service isolation, and dependency-aware execution as separate experiments.
This is a 2025 planning document with a 2026/27 research horizon. Its dates are historical context, not verified current milestones.
C#ZK roadmap + release evidence
Nethermind↗
ZK article updated April 2026; releases reviewed November 2026
The ZK article sequences witness capture, stateless replay, a minimal execution binary, and proof generation. Later release notes add flat-database safeguards, archive indexing, and more zkVM targets.
RELEVANCE TO xONE · OUR INTERPRETATION
Start with deterministic XDC witness replay and migration safety; proof-system integration is a separate research decision.
The article's milestone labels describe its April snapshot. Release records are a separate, newer evidence stream.
JavaPublished performance roadmap
Besu↗
2026 plan published 19 November 2025
The maintainer plan prioritizes worst-case execution benchmarks, further sync improvements, Bonsai archive performance, and a more efficient UInt256 arithmetic stack.
RELEVANCE TO xONE · OUR INTERPRETATION
Measure adversarial opcode and precompile workloads alongside ordinary replay, sync, and archive-query tests.
The source describes goals for 2026. The page does not certify whether each goal has since shipped.
RustWorking repository roadmap
ethrex↗
Main-branch roadmap reviewed 14 November 2026
The working plan covers execution hot paths, PGO/BOLT, database I/O, caching, RPC allocations, and root computation. It records discarded experiments as well as pending and measured work.
RELEVANCE TO xONE · OUR INTERPRETATION
Use small, falsifiable experiments and retain rejected optimizations when they explain a measured regression.
The file explicitly calls itself work in progress. Priority is relative urgency, not effort or a delivery date.
Go / XDC referencePublished milestone record
XDPoSChain↗
2026-Summer-Release milestone reviewed 14 November 2026
The milestone groups reward automation, dynamic gas-limit testing, EIP-7702 testing, epoch-penalty testing, audit work, and release documentation.
RELEVANCE TO xONE · OUR INTERPRETATION
Map only approved XDC rules into fork tables and conformance vectors; retain reward and epoch-boundary regression coverage.
The milestone name is a source label. It is not evidence that all included work shipped or activated on a network.
FROM REFERENCE TO RESEARCH
Turn a signal
into a test.
These are proposed website planning items derived from the review. “Next” is a suggested priority, not an assigned sprint. They do not claim a new issue, owner, implementation, or approved delivery date.
12 proposed workstreams
RM-01Next · proposed
Controlled performance baseline
Create repeatable replay and adversarial workloads with pinned inputs and a shared report format.
ACCEPTANCE TO DEFINE & VERIFY
Publish correctness results, wall time, CPU, p50/p95/p99, RSS, disk growth, hardware, and repeat variance.
Reference signals: Reth · Besu · ethrexxOne context / source
RM-02Next · proposed
Retention profiles and disk budgets
Specify which queries and consensus reads remain available under each supported retention profile.
ACCEPTANCE TO DEFINE & VERIFY
Measure equal block ranges; prove restart, unwind, historical-query behavior, and bounded cleanup before reporting savings.
Reference signals: Reth · Erigon · Geth · ethrexxOne context / source
RM-03Next · proposed
State-root and execution pipeline experiments
Profile root calculation and overlap independent work only where state ownership permits deterministic results.
ACCEPTANCE TO DEFINE & VERIFY
Match roots, receipts, bloom, and gas across ordinary, conflicting, reorg, and failure workloads; reject noisy or regressing gains.
Reference signals: Reth · Erigon · ethrexxOne context / source
RM-04Next · proposed
RPC correctness under bounded load
Complete declared method wiring and enforce work, range, response, and subscription budgets.
ACCEPTANCE TO DEFINE & VERIFY
Differential method tests and reorg-aware subscriptions pass; tail latency and error rates remain within an explicitly declared workload budget.
Reference signals: Geth · ethrex · ErigonxOne context / source
RM-05Next · proposed
Crash, migration, and rollback qualification
Test interrupted writes and schema transitions rather than inferring durability from a clean restart.
ACCEPTANCE TO DEFINE & VERIFY
A fault matrix proves canonical-head coherence, incompatible-layout refusal, recoverable upgrades, and signer-state preservation.
Reference signals: Geth · NethermindxOne context / source
RM-06Next · proposed
Worst-case EVM and precompile coverage
Pair routine replay with adversarial arithmetic, memory, storage, and precompile workloads under XDC gas rules.
ACCEPTANCE TO DEFINE & VERIFY
Pin vectors and protocol rules; publish maximum processing times and correctness before adjusting any capacity claim.
Reference signals: Besu · ethrexxOne context / source
RM-07Next · proposed
Network and fork conformance refresh
Track approved XDC changes through reference pins, generated tables, and explicit reward/epoch-boundary vectors.
ACCEPTANCE TO DEFINE & VERIFY
A reviewed pin update and differential corpus cover each adopted rule; Ethereum proposals alone cannot authorize XDC activation.
Reference signals: XDPoSChain · GethxOne context / source
RM-08Evaluate · proposed
Modular node and indexer boundaries
Evaluate bounded interfaces for state access, reorg-aware notifications, RPC service isolation, and embeddable components.
ACCEPTANCE TO DEFINE & VERIFY
An architecture decision records ownership, backpressure, restart behavior, API compatibility, and measured overhead.
Reference signals: Reth · ErigonxOne context / source
RM-09Research · proposed
Witness-based deterministic replay
Investigate the minimum XDC execution and consensus context needed to replay a block from an explicit witness.
ACCEPTANCE TO DEFINE & VERIFY
A prototype reproduces outputs without undeclared disk/network reads; measure witness size and generation/replay cost before selecting a prover.
Reference signals: Nethermind · ethrexxOne context / source
RM-10Research · proposed
Compiler and parallel execution feasibility
Evaluate compilation and dependency-aware scheduling against the qualified sequential implementation.
ACCEPTANCE TO DEFINE & VERIFY
Define XDC rule compatibility, deterministic conflicts, fallback behavior, portability, and complete end-to-end costs before an adoption decision.
Reference signals: Reth · Erigon · ethrexxOne context / source
RM-11Research · proposed
Account abstraction and transaction-pool study
Assess approved and proposed account behavior separately, including validation, pool limits, fees, and replay semantics.
ACCEPTANCE TO DEFINE & VERIFY
Publish an XDC-specific design and test vectors; separate an implementation experiment from network governance and activation.
Reference signals: Erigon · XDPoSChainxOne context / source
RM-12Next · proposed
Operational release qualification
Connect source identity, artifact checks, installation, soak evidence, and rollback into one reviewable release record.
ACCEPTANCE TO DEFINE & VERIFY
The exact packaged binary passes the declared network and recovery gates; owner authorization remains required for public producer tests.
Reference signals: Geth · Nethermind · XDPoSChainxOne context / source
SOURCES, NOT SHORTCUTS
Primary publisher pages and repositories were reviewed on 14 November 2026. The summaries are a planning snapshot; later releases may change them. Ethereum roadmaps inform research and do not automatically transfer Ethereum consensus rules, EIPs, gas limits, or timelines to XDC.
KEEP THE CURIOSITY GOING