Field notes.
Page 3. Back to the latest note.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
How the xOne 13-section issue format keeps XDC gaps clear
Every xOne issue uses the same 13 headings in the same order. See what each section holds, with excerpts from real xOneRS and xOnePy issues and a count.
How to join net2040 with xOne: step-by-step guide
Join net2040, XDC chain 2040, with xOne: get the binary, pass a peer, start the node, check the head against a reference, resume, swap the binary, pick a mode.
XDC validator key custody and seat rotation with xOne
Where an xOne validator key lives, what the node never does with it, and the exact steps to rotate or hand off an XDC seat, one signer at a time, on net2040.
xOne log formats: text, JSON and slow-block lines on XDC
How to read xOne logs on XDC: set --log.format text or json, tune --verbosity and --log.vmodule, and find budget, slow-block and producer lines in the output.
Measuring an xOne node before and after a change with measure-node.sh
How ops/bench/measure-node.sh records RPC latency, block import times, disk I/O and memory of a running xOne node before and after a window, and only reads.
A first run of measure-node.sh on a net2040 xOne node: latency, memory and I/O
We ran measure-node.sh for eight minutes on a net2040 xOne follower: RPC latency for seven calls, memory split, disk I/O, and errors the tool cannot explain.
Block-level access lists on XDC net2040: Amsterdam at block 21,600, as xOne checks it
net2040 activated Amsterdam and EIP-7928 block-level access lists at block 21,600. What the header carries, how xOneRS checks it, and the RPC to read a list.
How fast does a block reach each XDC client? A net2040 sample
A five-minute read-only sample on three hosts: when each xOne and fork node on net2040 first reported a new head, compared with the block's own timestamp.
How many blocks are in an XDC epoch? net2040 numbers
An XDC epoch is 900 rounds, not 900 blocks. On net2040, 554 of 933 epochs hold 900 blocks and 379 hold fewer. See the counts and how to repeat them with RPC.
net2040 incident: a 3 h 35 min halt after a late epoch block without a QC
net2040 incident log, 2026-11-15, 08:59 to 12:34 UTC: why block 852,529 got no QC, why no client recovered, the three re-proposals, the fixes, what is open.
One tracker for four XDC clients: how the hourly net2040 report works
How the hourly net2040 tracker on xOneRS issue 140 is built: one row per node, head and lag against the archive tip, the stats-board flag, and the mint column.
net2040 incident log, week 46: xOne seat misses and outages
Blameless net2040 incident log for 2026-11-09 to 2026-11-15: each recorded miss and outage of the four xOne seats, with its recorded cause, fix and open gaps.