THE xONE LAB Explore the performance record
xone.sh

04 / SIDE BY SIDE

Choose with
context.

Compare the four xOne implementations, then explore the wider execution-client ecosystem. The source review is dated 14 November 2026.

Swipe the table to compare all four clients →

Present in source Partial / limited Missing / not measured
xOne family source comparison, 14 November 2026
CAPABILITYxOneRSRUSTxOneCC++xOnePyPYTHONxOneTSTYPESCRIPT
Language / runtimeRust / nativeSource C++23 / nativeSource Python / CPythonSource TypeScript / BunSource
Execution enginerevm + XDC hooksSource C++ EVM interpreterSource py-evm adapterSource EthereumJS adapterSource
State storageMDBXAppend-only history segmentsSource libmdbxSource SQLite WALSource SQLiteSource
LicenseGPL-3.0-or-laterSource MITSource MITSource Apache-2.0Source
RepositoryPublicSource Access requiredSource Access requiredSource Access requiredSource
Mainnet productionGatedDevelopment clientSource GatedDevelopment clientSource GatedDevelopment clientSource GatedDevelopment clientSource

Four implementations of the XDC protocol, with different engines and storage choices. Language alone does not establish performance.

01 /

Read the labels carefully

Present means evidence was found in the reviewed source. Partial marks important limits. Missing includes work not implemented or not measured. This table does not certify production readiness.

Inspect the engineering auditBuild a client

KEEP THE CURIOSITY GOING

Another way in.

The client familyDeveloper handbookField notes
YOUR NEXT STEP

Build your way.

Choose an implementation to see its source-based build recipe.

Use the pinned Rust toolchain and platform build prerequisites in the repository.

git clone https://github.com/XDCIndia/xOneRS.git
cd xOneRS
cargo build --locked --release -p xone
./target/release/xone --version

This recipe builds the client; it does not start a node. Mainnet operation is not yet qualified.

Open source guide