QMC Documentation
Everything you need to understand and use the Quantum Matrix Chain
What is Quantum Matrix Chain?
Quantum Matrix Chain (QMC) is a standalone quantum Layer 1 blockchain built by WeAD. It is the world's first live blockchain with a dedicated quantum layer — both quantum-resistant (safe from future quantum computer attacks) and quantum-powered (actively uses quantum hardware in its consensus mechanism). The quantum layer handles post-quantum cryptographic signing, quantum random number generation for validator selection, and quantum circuit proof verification for every block.
| Property | Value |
|---|---|
| Token | QWD (Quantum WeAD) |
| Decimals | 6 |
| Total Supply | 8,100,000,000 QWD |
| Block Time | ~30 seconds |
| Consensus | Proof-of-Quantum (PoQ) |
| Signatures | Dilithium (ML-DSA, NIST-approved) |
| Chain ID | 7771 (mainnet) / 7772 (testnet) |
| Base Fee | 0.001 QWD |
| Minimum Stake | 10,000 QWD |
Why We're Building This
Here's the uncomfortable truth most of Web3 is ignoring: quantum computers are an existential threat to every blockchain in existence today.
The Quantum Threat to Crypto
Two quantum algorithms, both already proven in theory and being scaled in hardware, can dismantle the cryptographic foundations that every major blockchain depends on:
Shor's Algorithm — Breaks wallet security
Every blockchain wallet — Bitcoin, Ethereum, BNB Chain, Solana, all of them — uses elliptic curve cryptography (ECDSA/EdDSA) to generate private keys from public keys. The security assumption is simple: deriving a private key from a public key is mathematically infeasible for classical computers.
Shor's algorithm destroys that assumption. A sufficiently powerful quantum computer running Shor's algorithm can derive your private key directly from your public key. Every wallet that has ever broadcast a transaction has exposed its public key on-chain. That means every active wallet on every major blockchain is a target — not hypothetically, but mathematically.
Impact: Any wallet with an exposed public key can be drained. All EVM signatures become forgeable. The entire trust model of Web3 collapses.
Every blockchain wallet — Bitcoin, Ethereum, BNB Chain, Solana, all of them — uses elliptic curve cryptography (ECDSA/EdDSA) to generate private keys from public keys. The security assumption is simple: deriving a private key from a public key is mathematically infeasible for classical computers.
Shor's algorithm destroys that assumption. A sufficiently powerful quantum computer running Shor's algorithm can derive your private key directly from your public key. Every wallet that has ever broadcast a transaction has exposed its public key on-chain. That means every active wallet on every major blockchain is a target — not hypothetically, but mathematically.
Impact: Any wallet with an exposed public key can be drained. All EVM signatures become forgeable. The entire trust model of Web3 collapses.
Grover's Algorithm — Breaks mining and hash security
Proof of Work blockchains like Bitcoin rely on SHA-256 hashing to secure mining. The assumption is that finding valid hashes requires brute-force computation, and no shortcut exists.
Grover's algorithm provides that shortcut. It offers a quadratic speedup on brute-force search, effectively cutting SHA-256's security from 256 bits to 128 bits. A quantum-equipped miner could find valid blocks exponentially faster than classical miners, dominating hash rate and opening the door to 51% attacks — the ability to rewrite transaction history, double-spend, and censor blocks.
Impact: Proof of Work consensus becomes compromised. Mining centralises around whoever has quantum hardware first.
Proof of Work blockchains like Bitcoin rely on SHA-256 hashing to secure mining. The assumption is that finding valid hashes requires brute-force computation, and no shortcut exists.
Grover's algorithm provides that shortcut. It offers a quadratic speedup on brute-force search, effectively cutting SHA-256's security from 256 bits to 128 bits. A quantum-equipped miner could find valid blocks exponentially faster than classical miners, dominating hash rate and opening the door to 51% attacks — the ability to rewrite transaction history, double-spend, and censor blocks.
Impact: Proof of Work consensus becomes compromised. Mining centralises around whoever has quantum hardware first.
The Timeline Is Closer Than You Think
| Event | Date |
|---|---|
| NIST finalises post-quantum cryptography standards (FIPS 203/204/205) | August 2024 |
| Industry projections for cryptographically relevant quantum computers (CRQCs) | 2027 — 2033 |
| Australia's ASD mandates post-quantum migration | By 2030 |
| NIST prohibits classical cryptography (RSA, ECDSA, DSA) | By 2035 |
The window between "quantum computers can break crypto" and "everyone has migrated to quantum-safe crypto" is where catastrophic losses happen. Billions of dollars in wallets, smart contracts, and bridges will be vulnerable during that gap.
What QMC Does Differently
The Matrix Quantum Chain doesn't patch the problem — it was built from the ground up to be immune to it:
- Lattice-based signatures replace ECDSA — Every QMC wallet uses post-quantum cryptography approved by NIST. Shor's algorithm cannot derive private keys from these signatures. Not today, not ever.
- Proof-of-Quantum replaces Proof of Work — Validator selection is powered by true quantum randomness from physical measurements, not hash computation. Grover's algorithm has nothing to speed up because there is no hash race.
- Quantum hardware in the consensus loop — Every block carries a verifiable quantum proof from a real superconducting chip. This isn't a theoretical whitepaper — it's running infrastructure.
Most blockchains will need to hard-fork to survive the quantum era. QMC was born quantum-safe.
Architecture
QMC uses three layers of quantum technology:
- Dilithium Signatures — Every wallet and transaction is signed using lattice-based cryptography (NIST ML-DSA standard). Immune to Shor's algorithm.
- Quantum Random Number Generation — Validator selection uses true random numbers from ANU's quantum vacuum fluctuation lab. Physically impossible to predict or manipulate.
- Quantum Circuit Proofs — Each block includes a proof generated by running a parameterized GHZ entanglement circuit on Origin Quantum's Wukong 72-qubit superconducting chip.
The chain also features:
- WebSocket P2P networking for decentralized block/transaction propagation
- A stack-based smart contract VM with the QWD-20 token standard
- A lock-and-mint bridge to BNB Chain, Base, and Soneum
- An encrypted browser wallet with dApp injection (
window.qmc)
Networks
| Network | Chain ID | P2P Port | RPC Endpoint | Faucet |
|---|---|---|---|---|
| Mainnet | 7771 | 9900 | https://wead.live/rpc |
1,000 QWD / hour |
| Testnet | 7772 | 9901 | testnet endpoint (TBD) |
10,000 QWD / unlimited |
Mainnet is live at
wead.live. Testnet is available for development — run your own node with --network testnet.Wallets
QMC wallets use Dilithium (post-quantum) key pairs. Each wallet has:
- Address — your account identifier (safe to share)
- Public Key — used to verify your signatures
- Secret Key — used to sign transactions (generated and stored only in your browser — never sent to any server)
Create via Web Wallet (Recommended)
Go to /qmc-wallet, set a password, and click Create New Wallet. Your Dilithium keys are generated in your browser, AES-256-GCM encrypted, and stored locally. Your secret key never leaves your device.
Create via API (Deprecated)
POST /api/qchain/wallet/create
Response:
{
"address": "qwd1a2b3c4d...",
"public_key": "base64..."
}
// secret_key is no longer returned for security
Use client-side generation with
@noble/post-quantum ml_dsa44 or the QMC Web Wallet. The API no longer returns secret keys.Create via JavaScript SDK
import { QMCProvider, QMCWallet } from "@wead/qmc-sdk";
const provider = new QMCProvider("https://wead.live");
const wallet = await QMCWallet.create(provider);
console.log(wallet.address);
Transactions
QMC supports several transaction types:
| Type | Purpose |
|---|---|
transfer | Send QWD to another address |
mint | Faucet / system mint |
stake | Lock QWD to become a validator |
unstake | Begin withdrawing staked QWD |
deploy_contract | Deploy a QWD-20 token or custom contract |
call_contract | Call a contract function |
bridge_lock | Lock QWD for bridging to BNB Chain, Base, or Soneum |
bridge_release | Release QWD from bridge |
Build → Sign → Send Flow
# 1. Build transaction (server computes tx_id, nonce, gas)
POST /api/qchain/tx/build
{ "sender": "qwd1...", "recipient": "qwd1...", "value": 100, "tx_type": "transfer" }
# 2. Sign locally in your browser (secret key never leaves your device)
const signature = QMCCrypto.signLocally(tx.tx_id, mySecretKey);
# 3. Send signed transaction
POST /api/qchain/tx/send
{ "tx_id": "...", "sender": "...", "recipient": "...", "value": 100,
"signature": "base64...", "public_key": "base64...", "tx_type": "transfer" }
Signing is done client-side using Dilithium (ML-DSA-44). The deprecated
/api/qchain/tx/sign endpoint still works but sends your key over the wire — avoid it.Every transaction includes a fee (base: 0.001 QWD + gas). Fees go to the block producer.
Staking
Stake at least 10,000 QWD to become a validator and participate in block production.
Stake
POST /api/qchain/stake
{ "address": "qwd1...", "amount": 10000 }
Unstake
POST /api/qchain/unstake
{ "address": "qwd1...", "cooldown_blocks": 100 }
Claim (after cooldown)
POST /api/qchain/stake/claim
{ "address": "qwd1..." }
Check Validators
GET /api/qchain/validators
Response:
{ "validators": [{ "address": "qwd1...", "stake": 10000, "is_active": true }] }
QWD-20 Token Standard
QWD-20 is the native token standard for QMC (similar to ERC-20 on Ethereum). Any project can deploy their own token.
Deploy a Token
Send a deploy_contract transaction with this JSON in the data field:
{
"standard": "qwd20",
"args": {
"name": "My Token",
"symbol": "MTK",
"total_supply": 1000000
}
}
Supported Contract Calls
| Method | Parameters | Description |
|---|---|---|
balance_of | address | Get token balance of an address |
transfer | to, amount | Send tokens to another address |
approve | spender, amount | Allow another address to spend your tokens |
allowance | owner, spender | Check approved spending amount |
transfer_from | from, to, amount | Spend tokens on behalf of another (with approval) |
metadata | — | Get token name, symbol, supply, decimals |
Calling a Contract
POST /api/qchain/tx/build
{
"sender": "qwd1...",
"recipient": "contract_address_here",
"value": 0,
"tx_type": "call_contract",
"data": "{\"method\":\"transfer\",\"args\":{\"to\":\"qwd1...\",\"amount\":500}}"
}
Cross-Chain Bridge
QMC includes a lock-and-mint bridge to multiple EVM chains. Current targets are BNB Chain, Base, and Soneum. This allows QWD to flow between QMC and these networks.
Supported Chains
| Chain | Key | Mainnet Chain ID |
|---|---|---|
| BNB Chain | bnb | 56 |
| Base | base | 8453 |
| Soneum | soneum | 1868 |
How It Works
- Lock — You lock QWD on QMC by sending a
bridge_locktransaction with a target chain and EVM recipient address. - Relay — A relayer watches for lock events and mints wrapped QWD on the selected target chain.
- Return — To come back, the target-chain contract burns wrapped QWD and the relayer sends a
bridge_releaseon QMC.
Bridge Lock
POST /api/qchain/tx/build
{
"sender": "qwd1...",
"recipient": "qwd1...",
"value": 100,
"tx_type": "bridge_lock",
"data": "{\"to_chain\":\"base\",\"evm_recipient\":\"0xYourEvmAddress...\"}"
}
Bridge APIs
| Endpoint | Method | Description |
|---|---|---|
/api/qchain/bridge/chains | GET | List supported target chains |
/api/qchain/bridge/locks | GET | List recent bridge locks |
/api/qchain/bridge/releases | GET | List recent bridge releases |
/api/qchain/bridge/release | POST | Submit a bridge release |
REST API Reference
Base URL: https://wead.live
| Endpoint | Method | Description |
|---|---|---|
/api/qchain/status | GET | Chain status (height, supply, validators, P2P) |
/api/qchain/blocks | GET | Recent blocks (query: ?limit=10) |
/api/qchain/block/<height> | GET | Block by height |
/api/qchain/tx/<tx_id> | GET | Transaction by ID |
/api/qchain/address/<addr> | GET | Account details |
/api/qchain/validators | GET | Active validator list |
/api/qchain/mempool | GET | Pending transactions |
/api/qchain/wallet/create | POST | Create a new wallet |
/api/qchain/wallet/balance | POST | Check wallet balance |
/api/qchain/tx/build | POST | Build an unsigned transaction |
/api/qchain/tx/sign | POST | |
/api/qchain/tx/send | POST | Send a signed transaction |
/api/qchain/faucet | POST | Request free QWD |
/api/qchain/stake | POST | Stake QWD |
/api/qchain/unstake | POST | Begin unstaking |
/api/qchain/stake/claim | POST | Claim unstaked QWD |
/api/qchain/bridge/chains | GET | List supported bridge target chains |
/api/qchain/bridge/locks?chain=base | GET | List recent locks (optional chain filter) |
/api/qchain/contract/<addr>/meta | GET | Contract metadata |
/api/qchain/contract/<addr>/balance/<who> | GET | Token balance |
JSON-RPC Reference
Endpoint: POST https://wead.live/rpc
Standard JSON-RPC 2.0 format. Compatible with any JSON-RPC client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "qwd_blockNumber",
"params": []
}
| Method | Params | Description |
|---|---|---|
qwd_chainId | — | Returns chain ID |
qwd_blockNumber | — | Returns current block height |
qwd_getBlockByNumber | [height] | Block details by height |
qwd_getBlockByHash | [hash] | Block details by hash |
qwd_getTransactionByHash | [tx_id] | Transaction details |
qwd_getBalance | [address] | Account balance |
qwd_getTransactionCount | [address] | Account nonce |
qwd_sendRawTransaction | [tx_object] | Submit signed transaction |
qwd_call | [contract, method, args] | Read-only contract call |
qwd_estimateGas | [tx_object] | Estimate gas cost |
qwd_getCode | [contract] | Contract bytecode |
qwd_getLogs | [filter] | Contract event logs |
qwd_getValidators | — | Active validators |
qwd_getStake | [address] | Stake details for address |
net_version | — | Network version |
net_peerCount | — | Connected peer count |
Example: Get Balance via cURL
curl -X POST https://wead.live/rpc \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"qwd_getBalance","params":["qwd1youraddress"]}'
Testnet Access
The Matrix Quantum Chain testnet is hosted and operated by WeAD. Node software is not publicly distributed — all access is through the WeAD platform and RPC endpoints.
Get Started
- Visit wead.live/quantum-chain to explore the live chain dashboard
- Use the RPC endpoints below to interact with the testnet programmatically
- Testnet QWD tokens are available via the faucet API for development and testing
Testnet RPC Endpoint
https://wead.live/rpc
Chain Details
| Property | Value |
|---|---|
| Chain ID | 7772 (testnet) |
| Token | QWD |
| Block Interval | ~30 seconds |
| Consensus | Proof-of-Quantum (QRNG validator selection) |
| Signatures | Post-quantum lattice-based cryptography |
| Quantum Backend | 72-qubit superconducting chip + simulator fallback |
Faucet (Get Testnet QWD)
curl -X POST https://wead.live/api/qchain/faucet \
-H "Content-Type: application/json" \
-d '{"address": "qwd1youraddress"}'
Validator Program
Interested in running a validator node? The validator program will open during the public testnet phase. Join the waitlist at dev@wead.live to get early access when node software is distributed to approved operators.
Network Configuration
Key chain parameters for developers integrating with the Matrix Quantum Chain:
| Parameter | Value | Description |
|---|---|---|
| Chain ID (Mainnet) | 7771 | For mainnet transactions |
| Chain ID (Testnet) | 7772 | For testnet transactions |
| Block Interval | 30s | Target time between blocks |
| Max TX per Block | 100 | Transaction throughput limit |
| Minimum Stake | 10,000 QWD | Minimum to become a validator |
| Base Fee | 0.001 QWD | Minimum transaction fee |