XDPoS.
6 stories
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.
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.
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 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.
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.