Highlights from our research and engineering — multi-client infrastructure, the modern go-ethereum re-baseline, and the post-quantum work behind XDSS-PQ. Each entry below links to the full write-up on this site.
How we re-based the XDPoS engine onto current go-ethereum and what it inherits — path-based state, Pebble, freezer, snap sync — with bit-exact consensus parity. The single most impactful infrastructure change in the XDC multi-client effort.
Trade documents must stay legally valid for 20–30 years — longer than most Q-Day estimates. Why that makes harvest-now-decrypt-later a present risk, and how XDSS-PQ answers it.
Four independent clients across three languages — go-ethereum (GP5), Erigon, Nethermind and Reth — live on mainnet, so no single implementation can halt the chain.
Why we're mapping and migrating XDC's quantum-exposed surface now, and the post-quantum signature standard (XDSS-PQ) built on NIST-selected algorithms.
Why "when will quantum break ECDSA?" is best treated as a risk distribution — and what that means for 20–30 year trade documents you can't re-sign later.
Our take on Craig Gidney's 2025 estimate that breaking RSA-2048 may need far fewer qubits than once thought — and why it tightens the timeline for migration.
Read the analysis →
Dates reflect when each topic was written up for this site. These entries summarise and index existing pages and published research — follow each link for the full detail and sources.
Go deeper into the work.
Explore the engineering and the post-quantum initiative behind XDC Innovation Labs — or get in touch with the team.