LEARN
Tutorials
Task guides drawn from the field notes. Each lists what you need first and an outcome you can check. Editorial guide. This site has not independently re-run these steps. Other field notes are editorial and are not listed here.
6 of 6 guides shown.
Run and verify xOneRS
Build or download the Rust client, follow Apothem or net2040, and compare it with geth-XDC.
- Difficulty (editorial estimate)
- Intermediate
- Tools
- xone binary, Rust toolchain, geth-XDC node, curl
- Prerequisites
- A machine that can build xone with the pinned Rust toolchain, or the v0.1.0 release binary.
- A geth-XDC node on the same network to compare block hashes.
- Expected outcome you can check
- The version stamp commit matches the release tag, and block hashes from xone match block hashes from geth-XDC for the same block numbers.
- Reviewed against
- xOneRS v0.1.0 and main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.
Run an Apothem follower
Start an xOne follower on XDC Apothem (chain 51) by full sync or snap sync.
- Difficulty (editorial estimate)
- Intermediate
- Tools
- xone binary, curl
- Prerequisites
- An xone binary.
- Apothem bootnodes and enough disk for the datadir. The article gives measured sizes.
- Expected outcome you can check
- eth_blockNumber on the local node rises and approaches the Apothem reference head.
- Reviewed against
- xOneRS main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.
Run a one-validator dev chain
Start a local XDC chain with xone --dev, send a transaction and read the block.
- Difficulty (editorial estimate)
- Beginner
- Tools
- xone binary, curl
- Prerequisites
- An xone binary on your machine.
- Expected outcome you can check
- eth_chainId returns chain id 1337 (0x539), and the transaction you send appears in a block you read back.
- Reviewed against
- xOneRS main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.
Bootstrap a node from a snapshot
Export a snapshot from a synced node and import it, with a pins file, into an empty datadir.
- Difficulty (editorial estimate)
- Advanced
- Tools
- xone binary
- Prerequisites
- A stopped, synced xOne node to export from.
- An empty datadir and a pins file for the import.
- Expected outcome you can check
- xone snapshot import passes its anchor and pins checks, and the new node starts with --minimal.
- Reviewed against
- xOneRS main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.
Verify a release artifact
Check a downloaded xOne release file against SHA256SUMS and its version stamp.
- Difficulty (editorial estimate)
- Beginner
- Tools
- sha256sum, xone binary
- Prerequisites
- An asset and SHA256SUMS from the same release page.
- Expected outcome you can check
- sha256sum -c reports OK for the file, and the commit in the version stamp matches the release tag. This does not prove who built the file.
- Reviewed against
- xOneRS main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.
Monitor a node
Turn on metrics, scrape them with Prometheus and use the health endpoint.
- Difficulty (editorial estimate)
- Intermediate
- Tools
- xone binary, Prometheus, curl
- Prerequisites
- A running xone node.
- A Prometheus server.
- Expected outcome you can check
- Prometheus scrapes /metrics from the node, and /readyz answers for the node.
- Reviewed against
- xOneRS main, article updated 2026-11-15
- Testing
- Editorial guide. This site has not independently re-run these steps.