THE xONE LAB Explore the performance record
xone.sh

Field notes.

Page 6. Back to the latest note.

Explore the notes.

Different languages. A shared curiosity.

131 stories from the client collective

Validator5 min read

The xOne safety record: what an XDC signer writes before it votes

What the xOneRS signer safety record holds, where it lives, the write-ahead order before every signature, why it is never lowered, and how a restore keeps it.

Nov 15, 2026Read story
Validator4 min read

Setting up an XDC validator key with xone-signer-setup.sh

How ops/xone-signer-setup.sh in xOneRS checks a keystore against its address, imports it only with --apply, runs a roles report and prints a commented line.

Nov 15, 2026Read story
Sync7 min read

What happens when a snap pivot moves in xOne on XDC

When peers drop the state root of a snap pivot, xOneRS picks a new pivot, keeps the rows it has and heals them with GetTrieNodes. Steps, limits and live runs.

Nov 15, 2026Read story
Sync6 min read

How to bootstrap an XDC node from a snapshot with xOne

Export a snapshot from a synced xOne node, import it with a pins file, and start in minimal mode. Covers the checks, what the node keeps, and all four clients.

Nov 15, 2026Read story
Snapshot4 min read

Snapshot import with --staging: restore an xOne node safely

How xone snapshot import avoids a half-written XDC datadir: checks before any write, a resumable chunk buffer, --staging on another disk, head.json last.

Nov 15, 2026Read story
Snapshot6 min read

How xOne snapshots and backups are made and verified

What xOne hashes and what it signs in chain snapshots and datadir backups: the manifest, chunk checks, the pins file, the anchor proof, and the ADR-006 gap.

Nov 15, 2026Read story
Testing7 min read

State of parity for XDC clients in xOne, week of 2026-11-15

xOne parity with geth-XDC on 2026-11-15: replay ranges and mismatch counts for four clients, RPC parity counts, vector counts, the pin and fork rows covered.

Nov 15, 2026Read story
Release4 min read

How xOne qualifies a release tarball with the t8n corpus gate

How ci/qualify-artifact.sh runs the recorded t8n corpus through the packaged xOneRS binary and refuses a tarball whose output differs from the pinned geth-XDC.

Nov 15, 2026Read story
RPC6 min read

How to trace an XDC transaction with xOne tracers

Trace an XDC transaction with xOne: callTracer, prestateTracer, flatCallTracer and the struct logger. Example requests, response shapes, limits, parity counts.

Nov 15, 2026Read story
Operations7 min read

How to upgrade or roll back an xOne node safely

Upgrade or roll back an xOneRS node on XDC: check the binary, upgrade followers first, back up the datadir, and never lower or restore the signer safety record.

Nov 15, 2026Read story
Validator8 min read

XDC validator daily checklist: what to watch with xOne

A daily checklist for an XDC validator running xOne: Grafana panels, alert rules, producer log lines, seat watch, ethstats, disk lines and the version stamp.

Nov 15, 2026Read story
Release7 min read

How to verify an xOne release artifact on XDC

Check an xOne release download: SHA256SUMS, the version stamp against the tag, what ci/qualify-artifact.sh tests, and what the release page lacks today.

Nov 15, 2026Read story
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