Protocol

Bitcoin Core, hardened for the quantum era.

Bitcoin Quantum keeps Bitcoin's UTXO model, scripting system, halving schedule and SHA-256 proof-of-work intact — and replaces the signature algorithm with NIST-standardized post-quantum primitives.

Specifications

Protocol parameters at a glance.

SHA-256
Proof-of-work consensus
21M
Maximum BTQ supply
1 min
Target block time
8 MB
Per-block size limit
Under the hood

Cryptography that outlasts the quantum threat.

Every address is generated and spent with NIST-standardized post-quantum primitives — verifiable today, secure against the computers of tomorrow.

  • CRYSTALS-Dilithium (ML-DSA, NIST FIPS 204) signatures replace ECDSA
  • Native dilithium-bech32 and dilithium-legacy address formats
  • Cryptographic agility — ready to adopt new NIST PQC standards
shell · btq-cli testnet
# Generate a quantum-safe Dilithium address# and sign a testnet transaction. $ btq-cli -testnet createwallet "main"{ "name": "main" } $ btq-cli -testnet -rpcwallet=main \ getnewdilithiumaddresstdbt1qk4xv…q7n # Dilithium-bech32 $ btq-cli -testnet -rpcwallet=main \ sendtoaddress "tdbt1qk4xv…q7n" 0.508a7f…e2c1 # Every spend signed with ML-DSA — quantum-safe.
Network parameters

Ports and address prefixes.

The same three-network split Bitcoin operators expect — Mainnet for production, Testnet for the public test network, Regtest for local development.

NetworkRPC portP2P portAddress prefix
Mainnet83349333b, D, dbtc
Testnet1833419333n, tdbt
Regtest1844319444n, rdbt
References

Read the source.

Source

BTQ-Core

The full-node implementation, forked from Bitcoin Core and extended for post-quantum signatures.

View on GitHub →Specification

Whitepaper integration design

How CRYSTALS-Dilithium is wired through the UTXO model, scripting system, and consensus rules.

Read the doc →Standard

NIST FIPS 204

The standardized Module-Lattice-Based Digital Signature Algorithm — the cryptography behind every BTQ spend.

NIST publication →Operator guide

Mining guide

Step-by-step setup for running a node and connecting to the testnet pool, including the full CLI reference.

Read the guide →