xOneC: close to the machine, open to ideas

A C++23 execution client with its own EVM interpreter, libmdbx storage, and XDC consensus modules.

xBy xOne teamNov 13, 2026 / 1 min read

xOneC is the native C++ implementation in the xOne family. Its focus is a native implementation of the XDC execution client.

What it is

Runtime: native C++23
Execution: its own C++ EVM interpreter
Storage: libmdbx
Consensus: XDC consensus modules
License: MIT

Why a C++ client

Writing the EVM interpreter and consensus modules directly gives a codebase with no borrowed execution engine, and a different set of failure modes from the other clients. That independence is the point: disagreement between implementations is how protocol bugs get found.

How to build it

The repository is currently private, so you need access first. The toolchain is clang 19+, clang-format, clang-tidy, CMake 3.28+, Ninja, and Python 3.

git clone https://github.com/XDCIndia/xOneC.git
cd xOneC
cmake --preset dev
cmake --build --preset dev
build/dev/xonec --version

The presets are defined in CMakePresets.json.

Source

github.com/XDCIndia/xOneC

A NOTE ON READINESS

This article describes the source and evidence at its review date. Check the linked repository for current implementation and qualification status.

Explore the engineering evidence

xWritten by xOne team← All field notes

Build your way.

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

ClientGoal

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

What it is

Why a C++ client

How to build it

Source

Continue the investigation.

Four clients, one protocol: what each xOne client is for

How xOne releases are made, and how to read the version stamp

The conformance and replay gate