QRDXDocs

What is QRDX?

A blockchain whose accounts are secured by post-quantum signatures, with a spot and perpetuals exchange built into the protocol.

QRDX is a proof-of-stake blockchain designed for a world with quantum computers. Its validators sign with ML-DSA-65, the NIST post-quantum signature standard (FIPS 204, formerly CRYSTALS-Dilithium), and every account can hold a post-quantum key alongside a classic Ethereum-style one.

The chain also has a native exchange: order books, concentrated-liquidity pools and perpetual futures are part of the protocol's state, not contracts deployed on top of it. A trade is a transaction the validators execute and every node agrees on.

Testnet, live
Block height
—
Finalized epoch
—
Block interval
—
last 50 blocks
Chain ID
—

Testnet is live; mainnet is not yet

Everything in these docs runs on QRDX testnet. Testnet tokens have no value. Mainnet has not launched; see the roadmap.

What you can do today

How it fits together

PieceWhat it isWhere
QRDX nodeThe chain: consensus, the EVM, native tokens and the exchange engine. Serves JSON-RPC, REST and WebSocket/SSE streams.test.qrdx.org
QRDX WalletHolds your keys and signs. Browser extension (Chrome, Firefox), web app, and an iPhone app installed from Safari.wallet.qrdx.org
QRDX TradeThe trading interface for the native exchange, and a public API over it.trade.qrdx.org
QRDX ExplorerBlocks, transactions, accounts, tokens and markets.explorer.qrdx.org

Every app reads the same node, so they always agree. The wallet signs everything; the apps never hold your keys.

Why post-quantum

Ethereum and Bitcoin accounts are secured by elliptic-curve signatures. A large enough quantum computer running Shor's algorithm could derive a private key from a public one, and every account whose public key is known (any account that has ever sent a transaction) would be exposed. QRDX's post-quantum accounts are signed with ML-DSA-65, which no known quantum algorithm breaks. Post-quantum cryptography explains what that protects, and what it does not.

Try it now

This runs in your browser against testnet. Edit it and run it again.

JS
Read the chain head
output⌘/Ctrl + Enter to run
Edit the code and run it. It talks to testnet from your browser.

On this page