Field notes.
Page 8. Back to the latest note.
Explore the notes.
Different languages. A shared curiosity.
131 stories from the client collective
Transaction types on XDC: legacy, EIP-2930 and EIP-1559 in xOne
Which transaction types XDC accepts at which block: type 1 and type 2 wait for Eip1559Block, not Berlin or London. The xOne pool gates, fork numbers and tests.
The XDPoS RPC namespace in xOne: the 15 methods and what each returns
The 15 XDPoS_ RPC methods xOneRS serves, the parameters and answer shape of each, the case-exact names, and what is not served, from the spec and the tests.
What a timeout looks like on net2040: reading a skipped round over RPC
A real XDPoS v2 timeout on net2040: round 829,630 has no block, and XDPoS_getV2BlockByNumber shows it. How to decode the QC and find the round a TC closed.
How to run an XDC archive node with xOne: flags and status
Run an XDC archive node with xOne: use --gcmode archive on an empty datadir. See the reads it serves, how history is stored and the status of each client.
How xOne builds an XDC block: from the transaction pool to the seal
How an xOneRS producer builds an XDPoS v2 block: the slot timing, header, pool selection, 0x89 sign transaction, execution, safety record and the seal.
100 xOne posts by operator question: install, sync, validate, RPC and more
An index of the first 100 xone.sh posts, grouped by the operator question each one answers: install, sync, validate, RPC, troubleshoot, measure and compare.
How xOne stamps a build: version string and reproducible releases
How xOneRS builds its version stamp, why SOURCE_DATE_EPOCH fixes the date, which flags make two builds byte-equal, and what the static musl test build showed.
Streaming XDC chain events from xOne: subscriptions, txLifecycle, Kafka and hooks
Four ways an indexer gets XDC chain events from an xOneRS node: the eth_subscribe kinds, the txLifecycle stream, the Kafka exporter and in-process hooks.
The xOne CLI for XDC operators: attach, rpc check, wait-ready and more
What the xOneRS command line gives an operator next to a running node: xone attach, rpc check, wait-ready, sync-status, evm t8n and statetest, with exit codes.
The xone db toolkit: inspect, check, repair and compare an XDC node's database
Every xone db subcommand in xOneRS, grouped by job: what each reads or writes, which ones are safe beside a running node, and which need the node stopped.
The debug namespace in xOne: 30 debug_ methods for XDC operators, grouped by use
The debug_ JSON-RPC methods xOneRS serves on main, grouped by use: raw data, tracing, state inspection and node control, with limits, open checks and safety.
How to run a one-validator XDC dev chain with xone --dev
Start a local XDC chain with xone --dev: chain id 1337, one validator with an in-memory key, one funded test account. Send a transaction, read a block, stop it.