THE xONE LAB Explore the performance record
xone.sh

06 / SOURCE & RELEASES

Build it.
Know what you run.

Start from the source, inspect available release artifacts, and retain the identity of every binary you deploy.

01 /

Source is the reliable starting point

Select a client below for its source-based recipe. Availability of a tag or artifact does not, by itself, certify a build for mainnet use.

Native / RustPublic source

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
02 /

Release channels

The Rust README describes a local release script and notes that GitHub Actions is on a billing hold. Check the release page for any published artifacts and use the operator release procedure for verification; this website does not mirror binaries.

03 /

Before replacing a node binary

Record the source commit, toolchain, target platform, binary version, and artifact checksum where provided. Review data-format compatibility and keep a rollback plan. The repository guide is authoritative for the selected version.

FOLLOW THE SOURCE

Reviewed 14 November 2026. Repository guides hold the current implementation details.

KEEP THE CURIOSITY GOING

Another way in.

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