THE xONE LAB Explore the performance record
xone.sh

13 / OPERATE DELIBERATELY

Make trust
inspectable.

Understand the limits of the reviewed builds, keep sensitive interfaces bounded, and handle vulnerability details carefully.

01 /

Readiness and audits

The engineering audit on this website is a source and feature review. It is not an independent security certification. Review each client’s current status before treating a build as suitable for your environment.

02 /

Node and signer boundaries

Keep keys and signing material separate from public application traffic. Follow the signer-safety and key-management documentation for the client you operate. Review RPC namespace and transport access before exposing an endpoint.

03 /

Release provenance

Use the selected repository’s release procedure. Retain the source commit, binary version, target platform, and checksum when supplied. Inspect version-specific data-format compatibility before an upgrade.

04 /

Potential vulnerabilities

Do not publish exploit details, keys, or unredacted sensitive logs in an ordinary issue. Check the current project or XDC security reporting instructions and establish a confidential channel with the maintainers before sharing vulnerability details. No dedicated xOne disclosure address or response-time commitment is published here.

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