Field notes.
Page 5. Back to the latest note.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
xOne release checklist: upgrade the four clients on XDC
Checklist for xOneRS, xOneTS, xOnePy and xOneC: find the release, check the file, upgrade followers first, prove the start, roll back, and see the open defects.
How xOne reinjects transactions after a reorg on XDC
After a branch switch, xOneRS offers each transaction of the abandoned branch to the pool once, by normal admission. Read the rules, the 64-block cap, tests.
Why a one-block reorg wedged an xOne node on Apothem
Post-mortem of xOneRS issue 577: a one-block reorg stopped an Apothem validator. Read the cause, the per-block undo added in PR 606, its test and open work.
xOne replay gate in numbers: vectors, blocks and hours
The xOne replay gate in numbers for XDC: 430 vector files, replayed block ranges, transactions, epoch switches and wall-clock times for four clients, with sums.
reth-xdc on Apothem: a slow catch-up measured over nine samples
A reth-xdc minimal node on Apothem held a gap of about 48,900 blocks for seven hours, then gained about 30 blocks a minute. The samples, rate and ETA.
Exposing xOne JSON-RPC safely on XDC: limits, namespaces, JWT
The xOneRS JSON-RPC limits an operator relies on: 100-item batches, 5 MiB bodies, -32005 rate limits, namespace lists and -32601, JWT, and subscriptions.
xOne RPC parity on Apothem and net2040 in numbers
The xOneRS RPC parity reports against geth-XDC: 820 and 1,038 equal answers, 0 differ, and what not-backed and allowlisted rows mean on each XDC network.
How to run the xOne RPC parity sweep, and compare your own node
How to run the xOneRS RPC parity sweep from the repository, what it compares, and how to compare your own xOne node with a geth-XDC node of the same network.
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.
How to run and verify xOnePy, the Python XDC client
xOnePy is the Python xOne client for XDC. This guide shows how to install it, follow net2040, pick a sync mode, and check its version, head and replay records.
How to run and verify xOneTS, the TypeScript XDC client
Build xOneTS with Bun or take the v0.1.0 binary, follow net2040, then check the version stamp, the stats board, head lag and replay records. Private repo.
How to run and verify xOneRS, the Rust XDC client
Build or download xOneRS, follow Apothem or net2040, and check the node against geth-XDC: version stamp, block hashes, doctor, /readyz, and open gaps.