THE xONE JOURNAL
INDEPENDENT CODE. SHARED IDEAS.Field notes.
Inside the code. Behind the decisions.
Ideas from the people building
more ways into XDC.
Account recreation on XDC: SELFDESTRUCT, CREATE2 at the same address, and old storage
Why a client must wipe old storage when an account is deleted and created again in one block, how ADR-011 and PR #1084 change xOneRS, and what is unverified.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
Account recreation on XDC: SELFDESTRUCT, CREATE2 at the same address, and old storage
Why a client must wipe old storage when an account is deleted and created again in one block, how ADR-011 and PR #1084 change xOneRS, and what is unverified.
How to tune Prometheus alerts for an xOne node on XDC
Tune the eight Prometheus alert rules that ship with xOne on XDC: each rule's expression, for: time and severity, what fires it, what to check, what to change.
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.
xOne for XDC RPC providers: archive vs full, retention errors
What an XDC RPC provider gets from an xOneRS node: archive versus full reads, the typed unsupported-history error, eth_capabilities and the Apothem sweep.
xOne on Apothem vs net2040: what changes for an operator
Compare xOne on XDC Apothem and net2040: chain id, V2 switch block, bootnodes, state size, sync modes, --mine rules, quiet window and measured follower numbers.
Where does block time go? The xOne receive and slow-block log fields
How to join the xOne Block received and Slow block log lines on the block hash to get receive-to-head time and phase times for each block, field by field.
Choosing an xOne sync mode on XDC: a decision table
Pick full, snap, minimal or archive for an xOne node on XDC. One table maps your need to a mode, with measured datadir sizes and the flags of all four clients.
How xOne proves parity with geth-XDC: the replay gate
How xOne checks blocks, state roots and RPC answers against a pinned geth-XDC with its replay gate, and which recorded block ranges show 0 mismatches today.
Resuming an xone --dev chain: seeded fixtures on XDC
How a seeded xone --dev chain resumes from its datadir, how a copied datadir becomes a saved fixture, and which starts xOneRS refuses before writing anything.
How to plan disk space for an XDC node with xOne
Plan disk for an XDC node with xOne: the node's 2%, 3% and 1% free-space lines, the 15% alert, datadir sizes per sync mode, segment files and MDBX limits.
Disk watermarks and block sealing: why a full disk stops xOne
Why a low disk stops block sealing in xOne on XDC: one gate for import and producer, the NoSpace second line, and what the four clients do at the exit line.
FROM READING TO BUILDING
Bring your perspective.
Explore the clients, follow the engineering, or help write the next chapter.