THE xONE LAB Explore the performance record
xone.sh

GET STARTED / 02

Know your
network.

Network identity comes first. Keep test assets, data directories, and configuration separate between environments.

01 /

Network reference

These identifiers distinguish the public XDC networks from the development environment used in the Rust follower evidence.

NetworkChain IDxOne context
XDC mainnet50 / 0x32Rust mainnet follow and mint are not qualified.
Apothem51 / 0x33Documented Rust public-testnet follower path.
net20402040 / 0x7f8Development network used in Rust replay and follower records.
02 /

Public application endpoints

For applications, the XDC documentation lists https://erpc.xinfin.network for mainnet and https://rpc.apothem.network for Apothem. These are external network services, not an xOne-hosted RPC product.

Official endpoint referenceApothem explorer
03 /

Node peers and bootnodes

The Rust Apothem node reads bootnodes from ops/bootnodes/apothem.txt; the README says there is no built-in boot list. Use the current repository file and the matching network guide. net2040 has separate configuration.

Apothem follower guidenet2040 follower guide
FOLLOW THE SOURCE

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

Network status in the Rust READMEXDC network endpoint documentation

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