xOneC.
12 stories
Apothem datadir size by xOne client: measured after snap sync
How big an xOne Apothem datadir is after snap sync, per client: 13 to 72 GB as recorded in issue 149, a fresh byte count, growth over eight hours, and why.
How to run an XDC Apothem follower with xOne: measured
Run an xOne follower on XDC Apothem by full or snap sync. See what the xOne team measured on its Apothem nodes: head, disk, memory, and what is not measured.
Four xOne clients minting fair share on XDC net2040
Over 25,377 blocks of a 14-seat era on XDC net2040, four xOne clients (Rust, C++, Python, TypeScript) each sealed 7.11% to 7.24% of blocks. Fair share: 7.14%.
Inside xOneC: MDBX and the producer path on XDC
Follow one block through xOneC, the C++ XDC client, from import to the libmdbx commit, then one sealed block from the leader turn to broadcast, with file:line.
How to run and verify xOneC, the C++ XDC client
Build xOneC or use the v0.1.0 binary, follow net2040 or Apothem, pick a sync mode, and check the node: version stamp, board, head, replay gate and known gaps.
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.
Which xOne client should you run on XDC Network?
Which xOne client should you run on XDC? xOneRS, xOneTS, xOnePy and xOneC follow one specification. This post compares the four and says how to choose one.
How to run an XDC archive node with xOne: flags and status
Run an XDC archive node with xOne: use --gcmode archive on an empty datadir. See the reads it serves, how history is stored and the status of each client.
How xOne releases work and how to read the version stamp
The latest tags of the four xOne clients, how to read the xOne version stamp, and the checks a release must pass before the owner publishes it on GitHub.
How xOne stores XDC chain data: engines and datadir
How xOne stores XDC chain data in its four clients: the database engine of each, the datadir files, segment publication, crash-safe commits and datadir sizes.
How snap, fast and full sync work in xOne on XDC
How snap, fast, full and minimal sync work in the four xOne clients on XDC: flags, pivot steps, net2040 status, and how other clients describe sync modes.
xOneC: close to the machine, open to ideas
A C++23 execution client with its own EVM interpreter, libmdbx storage, and XDC consensus modules.
Edit this page on GitHub opens the page source (app/blog/tags/[tag]/page.jsx). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.