Field notes.
Page 2. Back to the latest note.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
Running the Ethereum execution spec tests against xOne
The first pinned EEST v5.4.0 run of the xOneRS statetest runner: 1,645 cases run, 1,639 passed, 6 confirmed XDC rule differences, 42,386 entries skipped.
How epoch switches work on XDC and how xOne tests them
What an XDC epoch switch is, what its header carries, how masternode lists and leaders are derived, and how xOne checks V1 checkpoints and V2 switches.
How fair mint is measured on XDC net2040 with xOne
How xOne counts fair mint on XDC net2040: the miner of every canonical block, three windows, the leader formula and seal checks. Repeat a count over JSON-RPC.
XDC fleet snapshot 2026-11-15: xOne and other clients
Every node of the xOne fleet on net2040 and Apothem at 2026-11-15 01:50 UTC: head, lag, disk, memory and RPC sample, plus one correction to an earlier row.
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%.
Four XDC clients on one host: load and disk records
What xOne recorded with four XDC clients on one shared host: the 27-minute Python seat outage, load averages, disk lines and the memory cap, with sources.
How xOne tracks feature gaps against other XDC clients
How xOneRS finds feature gaps against other clients: scored competitors, a ledger of 319 gaps, one 13-section issue per gap, and how duplicates are avoided.
Is xOne later than geth-XDC to a new block? A same-host sample, and two tool problems
A 10-minute same-host sample of when xOneRS and geth-XDC first report each net2040 block, why measure-head-lag.sh cannot answer it, and a null latest block.
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.
Inside xOnePy: SQLite WAL and the event loop on XDC
How xOnePy, the Python XDC client, sets SQLite WAL, owns BEGIN and COMMIT, groups commits, and keeps its asyncio loop free, with the numbers its repo records.
Inside xOneTS: SQLite storage and dense sync on XDC
How xOneTS keeps XDC chain data in bun:sqlite and segment files, how group commit and the hashed-key migration work, and what the dense-sync fix changed.
What a refused block leaves behind: xOne's invalid-block evidence
When xOneRS refuses an XDC block, it keeps the block and the error in a bounded evidence directory: what an entry holds, the 16-entry and 1 GiB bounds, limits.