Field notes.
Page 10. Back to the latest note.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
Installing xOne with Homebrew, Helm, Stereum, Eth Docker or WSL2
What each xOneRS package covers: a pinned Linuxbrew formula, a follower-only Helm chart, Stereum and Eth Docker service files, and the WSL2 guide, with limits.
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.
xOne roadmap: what gates A to E mean for XDC clients
xOne roadmap for XDC clients: gates A to E and track Q each close on recorded evidence. See what each gate requires and where it stands on main today.
Why a fast poller gets HTTP 429 from an xOne node, and how to follow the head instead
The xOneRS RPC rate bucket: 400 units of burst, 200 units per second, method costs of 1 to 100 units, what a refusal looks like, and polling versus subscribing.
XDC JSON-RPC methods in xOne and how parity is checked
XDC JSON-RPC methods in xOne: the namespaces xOneRS serves, the default transports, and how answers are diffed against geth-XDC to check parity on net2040.
Securing xOne RPC without a proxy: native TLS, client certificates and method ACLs
How to serve xOneRS JSON-RPC over TLS, require client certificates, and give each JWT principal its own method list with --rpc.acl, with the errors to expect.
xone setup: a guided first XDC follower, in English, Hindi or Marathi
How the xOneRS guided setup plans a first follower node: the questions it asks, the dry run, the JSON-lines events for scripts, and Hindi and Marathi prompts.
Smaller and safer xOne datadirs: zstd segments, compact receipts and a staging volume
Five xOneRS storage changes: zstd history segments, receipts without stored blooms, size-capped segment files, a staging volume and a resize-aware disk guard.
Running EVM state tests with xone evm statetest on XDC
How the xOneRS statetest runner runs a GeneralStateTests or EEST fixture, which cases it skips and why, and how a fixture reproduces the pinned geth-XDC root.
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.
How the xOne transaction pool keeps up with each block: touched-sender resets
After each block, the xOneRS pool now rechecks only the senders the block changed. When it still does a full reset, how it is tested, and the gossip scheduler.