BTCX · MAINNET

Quantum protection

Post-quantum signatures for spending. Hybrid encryption for peer connections.

Status reviewed October 4, 2026. Activation is set by block height.

SPENDING · BLOCK 22,464

Two signatures to spend

Quantum-safe addresses require both Ed25519 and ML-DSA-44. Breaking the classical key alone is not enough to spend their coins.

ML-DSA is NIST’s post-quantum signature standard. FIPS 204 ↗

LIVE · COMPATIBLE PEERS

Network connections

X25519 + ML-KEM-768 protects links when both peers support it. Older peers can connect without this protection; the exchange does not authenticate peer identity.

ML-KEM · FIPS 203 ↗
BLOCK 22,464

Receiving & payouts

At activation, current wallets use protected addresses for new receiving addresses, change, mining and new masternode payouts. Restart a running miner to pick up its new payout address.

KEY DEADLINE · BLOCK 39,744

Masternodes

Hybrid signing starts at block 22,464. Migrate existing masternode keys in the desktop wallet by block 39,744.

IN DEVELOPMENT

Private payment encryption

Amounts and memos still use classical encryption. An ML-KEM-768 layer is in development. Terminal message encryption also remains classical.

Protect your coins

  1. Use Quantum Wallet 0.2.18 on Windows or 0.2.5 on Android before block 22,464.
  2. After activation, use Move to quantum-safe address for older coins, especially where a public key has already been exposed.
  3. If you run a masternode, migrate its keys in the desktop wallet before block 39,744.

Updating the wallet does not protect coins still held at older addresses. Those addresses remain valid, with no retirement deadline.

Mining, private proofs & research

GX9 mining uses SHA3. Quantum search affects hash functions differently from the attacks on elliptic-curve signatures.

Private-note hash commitments and pool accounting add safeguards. The private proofs still rely on elliptic-curve cryptography; they are not post-quantum proofs.

A hash-based private pool is research work. SLH-DSA, a second signature family based on hashes, is planned.

There is no privileged emergency key or built-in central pause switch. Rule changes are delivered through node releases that operators choose to install.