xOne team.
The contributors who write about the xOne XDC execution-client family. Articles describe source and evidence at their review date.
xOne on GitHubArticles
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.
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.
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.
Running the net2040 replay with xone-replay: fetch, run, gate
How xone-replay replays net2040 on xOneRS's own state: the block cache, the run command, what a mismatch record holds, and why it gates consensus changes.
Why net2040 makes a block every 4.5 seconds today: two late xOne seats
net2040 averaged 4.0 to 4.5 s per block on 2026-11-15, not 2 s. No round timed out: the Python and C++ xOne seats sealed 13 to 27 seconds after their parent.
How to run an XDC validator on net2040 with xOne
How to run an XDC validator on net2040 with xOne: follow the network, import a signer key, pass the mint gate, start the producer, and hand off the seat safely.
Banning a peer by hand on xOne: admin_banPeer on XDC
How an xOneRS operator bans and unbans a peer by node id with admin_banPeer, how the ban differs from automatic reputation bans, and what it does not keep.
How to check an xOne node's networking from another host
The xOneRS p2p live checks: advertised address and NAT, enode and peer probes, a discovery bootnode, the node allowlist and interop with other XDC clients.
How xOne checks a peer's chain before syncing from it
xOne drops a peer that serves the wrong hash at a required block, and refuses a chain through it. See the Apothem anchor, the flag and the other peer checks.
How xOne chooses and drops XDC peers: dial sample, score, bans
How an xOneRS node picks peers to dial from a seeded discovery sample, scores each peer's offences, bans a peer at 100 points, and where operator bans fit.
How xOne computes XDC penalties and rewards bit-exactly
Who xOne penalises on XDC, how long a penalty lasts, how a node returns, how signing sets rewards, and how golden vectors and mutants prove the result.
Running xOne with Prometheus and Grafana in Docker Compose
How to start the xOneRS monitoring stack with Docker Compose: Prometheus, Grafana, node_exporter and an optional Alertmanager on loopback, and how to check it.
A load miss, explained: the Python validator at round 841,894
Incident note: the xOnePy validator missed one net2040 turn at round 841,894 under host load 41.8. What the log showed, why, and what to watch next time.
QC, TC and timeouts: what an XDPoS v2 follower verifies in xOne
What a quorum and a timeout certificate hold, how xOneRS counts signers, which checks a follower runs on each XDPoS v2 header, and what only a voter adds.
Reading an xOne node log on XDC: the ten lines that matter
Ten log lines an xOne operator meets on XDC: the exact format from the source, what each line means, and what to do. Start, import, disk guard, producer, stop.
xOne release checklist: upgrade the four clients on XDC
Checklist for xOneRS, xOneTS, xOnePy and xOneC: find the release, check the file, upgrade followers first, prove the start, roll back, and see the open defects.
How xOne reinjects transactions after a reorg on XDC
After a branch switch, xOneRS offers each transaction of the abandoned branch to the pool once, by normal admission. Read the rules, the 64-block cap, tests.
Why a one-block reorg wedged an xOne node on Apothem
Post-mortem of xOneRS issue 577: a one-block reorg stopped an Apothem validator. Read the cause, the per-block undo added in PR 606, its test and open work.
xOne replay gate in numbers: vectors, blocks and hours
The xOne replay gate in numbers for XDC: 430 vector files, replayed block ranges, transactions, epoch switches and wall-clock times for four clients, with sums.
reth-xdc on Apothem: a slow catch-up measured over nine samples
A reth-xdc minimal node on Apothem held a gap of about 48,900 blocks for seven hours, then gained about 30 blocks a minute. The samples, rate and ETA.
Exposing xOne JSON-RPC safely on XDC: limits, namespaces, JWT
The xOneRS JSON-RPC limits an operator relies on: 100-item batches, 5 MiB bodies, -32005 rate limits, namespace lists and -32601, JWT, and subscriptions.
xOne RPC parity on Apothem and net2040 in numbers
The xOneRS RPC parity reports against geth-XDC: 820 and 1,038 equal answers, 0 differ, and what not-backed and allowlisted rows mean on each XDC network.
How to run the xOne RPC parity sweep, and compare your own node
How to run the xOneRS RPC parity sweep from the repository, what it compares, and how to compare your own xOne node with a geth-XDC node of the same network.
How to run and verify xOneC, the C++ XDC client
Build xOneC or use the v0.1.0 binary, follow net2040 or Apothem, pick a sync mode, and check the node: version stamp, board, head, replay gate and known gaps.
How to run and verify xOnePy, the Python XDC client
xOnePy is the Python xOne client for XDC. This guide shows how to install it, follow net2040, pick a sync mode, and check its version, head and replay records.
How to run and verify xOneTS, the TypeScript XDC client
Build xOneTS with Bun or take the v0.1.0 binary, follow net2040, then check the version stamp, the stats board, head lag and replay records. Private repo.
How to run and verify xOneRS, the Rust XDC client
Build or download xOneRS, follow Apothem or net2040, and check the node against geth-XDC: version stamp, block hashes, doctor, /readyz, and open gaps.
The xOne safety record: what an XDC signer writes before it votes
What the xOneRS signer safety record holds, where it lives, the write-ahead order before every signature, why it is never lowered, and how a restore keeps it.
Setting up an XDC validator key with xone-signer-setup.sh
How ops/xone-signer-setup.sh in xOneRS checks a keystore against its address, imports it only with --apply, runs a roles report and prints a commented line.
What happens when a snap pivot moves in xOne on XDC
When peers drop the state root of a snap pivot, xOneRS picks a new pivot, keeps the rows it has and heals them with GetTrieNodes. Steps, limits and live runs.
How to bootstrap an XDC node from a snapshot with xOne
Export a snapshot from a synced xOne node, import it with a pins file, and start in minimal mode. Covers the checks, what the node keeps, and all four clients.
Snapshot import with --staging: restore an xOne node safely
How xone snapshot import avoids a half-written XDC datadir: checks before any write, a resumable chunk buffer, --staging on another disk, head.json last.
How xOne snapshots and backups are made and verified
What xOne hashes and what it signs in chain snapshots and datadir backups: the manifest, chunk checks, the pins file, the anchor proof, and the ADR-006 gap.
State of parity for XDC clients in xOne, week of 2026-11-15
xOne parity with geth-XDC on 2026-11-15: replay ranges and mismatch counts for four clients, RPC parity counts, vector counts, the pin and fork rows covered.
How xOne qualifies a release tarball with the t8n corpus gate
How ci/qualify-artifact.sh runs the recorded t8n corpus through the packaged xOneRS binary and refuses a tarball whose output differs from the pinned geth-XDC.
How to trace an XDC transaction with xOne tracers
Trace an XDC transaction with xOne: callTracer, prestateTracer, flatCallTracer and the struct logger. Example requests, response shapes, limits, parity counts.
How to upgrade or roll back an xOne node safely
Upgrade or roll back an xOneRS node on XDC: check the binary, upgrade followers first, back up the datadir, and never lower or restore the signer safety record.
XDC validator daily checklist: what to watch with xOne
A daily checklist for an XDC validator running xOne: Grafana panels, alert rules, producer log lines, seat watch, ethstats, disk lines and the version stamp.
How to verify an xOne release artifact on XDC
Check an xOne release download: SHA256SUMS, the version stamp against the tag, what ci/qualify-artifact.sh tests, and what the release page lacks today.
Which xOne client should you run on XDC Network?
Which xOne client should you run on XDC? xOneRS, xOneTS, xOnePy and xOneC follow one specification. This post compares the four and says how to choose one.
How xOne handles XDC balances above 2^256
How xOne keeps an XDC balance above 2^256 exact: the EVM sees the low 256 bits, the state leaf keeps the full value, undo restores it, and what is still open.
How xOne refuses the wrong XDC network for a datadir
How xOneRS keeps a datadir on its own chain: the chain marker with chain id, genesis hash and consensus schedule, the --chainspec.update rule, and peer checks.
Memory per XDC client: resident memory of 33 nodes from the fleet probe
Resident memory (RSS) of 33 XDC nodes by client and sync mode, from eight read-only fleet samples, and why file-backed pages make some numbers look larger.
How fast does an XDC datadir grow? Growth per hour and per block for 30 nodes
Datadir growth of 30 XDC nodes over 8.8 hours of read-only samples: per hour and per block, on Apothem and net2040, with one outlier that is now an issue.
eth_getLogs on XDC with xOne: the 5,000-block range, the 10,000-log cap, retries
The two eth_getLogs limits in xOneRS, the errors they return, the retry range in the overflow error, and how they compare with the geth and erigon flags.
Block explorers on xOne: the trace_ and ots_ namespaces for Blockscout and Otterscan
Which trace_ (Parity) and ots_ (Otterscan) methods xOneRS serves for XDC block explorers, how to turn them on, their limits, and what is still unverified.
Finality on XDC for exchanges and bridges: what xOne reports
When an XDPoS v2 block is final, how xOne exposes it through the finalized tag and eth_getBlockFinalityByNumber, and why to wait for commit, not a fixed count.
The XDC gas limit rule in xOne: xdcGasLimit and --miner.gaslimit
How an xOneRS producer sets the gas limit of a new XDC block: three rows around DynamicGasLimitBlock, the 1/1024 step, the mainnet plateau and the ceiling.
Newer JSON-RPC methods on XDC: what xOne serves and what it does not yet
eth_simulateV1, eth_callBundle, eth_getProof, eth_getStorageValues and debug_traceBadBlock in xOneRS: what each does, its limits, and what is still unverified.
Running an XDC RPC endpoint on xOne: a checklist for providers
A checklist for public XDC JSON-RPC on xOneRS: history and archive, limits, TLS and per-key method lists, health checks, log queries and what to monitor.
RPC read latency of XDC clients: a 20-call sample on 33 nodes
Median and p95 latency of eth_blockNumber, eth_getBlockByNumber and eth_getBalance on 33 XDC nodes and three hosts, from a read-only sample, and how to read it.
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.
Local XDC development with xOne: impersonation, a loopback explorer and network workspaces
Three xOneRS dev tools from 2026-11-15: anvil_impersonateAccount on --dev, a loopback block explorer, and xone network up, status and down for local networks.
DNS peer discovery for XDC nodes: xOne's --discovery.dns and signed EIP-1459 trees
How xOneRS finds peers from a signed EIP-1459 DNS tree with --discovery.dns, what it checks before it dials, and why no XDC network has a tree to use yet.
XDC node hardware and disk requirements for xOne
XDC node hardware requirements for xOne: no CPU or RAM sizing is published. Read the enforced limits, disk watermarks, and the memory and disk use measured.
Health checks for an XDC node: /livez and /readyz in xOne for load balancers
How xOne's /livez and /readyz endpoints decide health, the five not-ready reasons, the configurable head-age limit, and their use behind a load balancer.
History retention in xOne: pruning bodies, receipts, logs and state, and backfill
The xOneRS --history flags: how long a node keeps bodies, receipts, logs, state and preimages, how to prune a stopped datadir, and backfill after snap sync.
Serving HTTP and WebSocket JSON-RPC on one port with xOne
How xOneRS serves HTTP and WebSocket RPC on one port: when it shares the listener, what stays separate per protocol, the TLS rule, and one admin_stopWS caveat.
Ten xOne Prometheus metrics to alert on for an XDC node
Ten Prometheus series the xOne node exports on XDC: name, type, meaning, one PromQL alert and the first check. It also says which series the node fills now.
What changed in xOne this week: a mid-week digest to 2026-11-15
The 507 pull requests the four xOne clients merged from 2026-11-13 to 2026-11-15, grouped by area: RPC, operations, CLI, sync, storage, execution and testing.
A permissioned XDC network with xOne: the node allowlist and the perm_ methods
How xOneRS restricts peers to an enode allowlist with --permissions.nodes, refuses everyone else, and changes the list at run time with perm_ RPC or SIGHUP.
How to monitor an XDC node with xOne: metrics, logs, ethstats
How to monitor an XDC node with xOne: log budgets, Prometheus metrics and health paths, the ethstats client, and the alert rules an operator should start with.
xOne ops toolbox: ten host tools for XDC node operators
The xOne ops toolbox in xOneRS: ten host tools for XDC nodes. Each entry says what the tool does, whether it changes anything, and gives one example command.
OpenTelemetry tracing for an XDC node: xOne's --tracing.otlp, and what it sends today
How to point xOneRS at an OTLP/HTTP collector with --tracing.otlp, how the bounded export queue works, and why the exporter has no xOne spans to send yet.
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.
From xOne v0.1.0 to main: what changes for an operator after upgrading
What an operator notices when moving an xOneRS node from the v0.1.0 release to a build of main: new defaults, new flags that stay off, and formats that change.
xOne vs besu-xdc: measured head, disk, memory and RPC
Read-only measurement of besu-xdc (Bonsai) and xOne nodes on net2040 and Apothem: head, datadir size, memory and RPC JSON shape, with the sync mode of each row.
xOne vs erigon-xdc: what we could measure on Apothem
One read of the only erigon-xdc node, on Apothem, while it re-synced from block 0: datadir and memory only, next to xOne rows and published erigon-xdc claims.
xOne vs geth-XDC on net2040 and Apothem: measured results
Measured results of xOne against geth-XDC: block share on net2040, RPC parity, replay parity and archive reads, each with its network, range, date and source.
xOne vs nethermind-xdc on XDC: measured head, disk, memory, RPC
xOne against nethermind-xdc on net2040 and Apothem: head, datadir size, memory and RPC JSON for each node, with sync or pruning mode, network and date.
xOne vs reth-xdc on XDC: measured head, disk, memory, RPC
Head, datadir size, memory and RPC output of xOne and reth-xdc on net2040 and Apothem, from one read-only sample taken on 2026-11-14, with each node's mode.
What changed in xOne on XDC this week (to 2026-11-15)
A digest of the 484 pull requests merged in xOneRS, xOneTS, xOnePy and xOneC from 2026-11-10 to 2026-11-14, grouped by sync, archive, producer, RPC and storage.
xOneRS: a Rust foundation for XDC
A layered Rust execution client with revm, MDBX storage, and XDPoS V1/V2 consensus.
xOneC: close to the machine, open to ideas
A C++23 execution client with its own EVM interpreter, libmdbx storage, and XDC consensus modules.
xOnePy: a readable path into the protocol
A Python execution client with typed workspace packages, a py-evm adapter, and SQLite WAL storage.
xOneTS: the protocol, in a familiar language
A TypeScript execution client on Bun, with modular packages, an EthereumJS EVM adapter, and SQLite-backed state.