GET STARTED / 02
Know your
network.
Network identity comes first. Keep test assets, data directories, and configuration separate between environments.
Historical source snapshot. Source links point to commit 5af188d; text was reviewed 14 November 2026 and may differ from newer client builds.
Network reference
These identifiers distinguish the public XDC networks from the development environment used in the Rust follower evidence.
| Network | Chain ID | xOne context |
|---|---|---|
| XDC mainnet | 50 / 0x32 | Rust mainnet follow and mint are not qualified. |
| Apothem | 51 / 0x33 | Documented Rust public-testnet follower path. |
| net2040 | 2040 / 0x7f8 | Development network used in Rust replay and follower records. |
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.
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.
Reviewed 14 November 2026. Repository guides hold the current implementation details.
KEEP THE CURIOSITY GOING
Another way in.
Edit this page on GitHub opens the data definition (data/site-pages.js). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.