Apothem.
7 stories
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.
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.
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.
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.
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.
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.
Edit this page on GitHub opens the page source (app/blog/tags/[tag]/page.jsx). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.