The First Quantum-Resistant Blockchain Built for the Future
Founder: Kishore K — admin@quantachain.org — quantachain.org
QUANTA is a production-ready blockchain operating as a Post-Quantum Institutional Settlement Layer. While Bitcoin and Ethereum use cryptography vulnerable to future quantum computers, QUANTA is designed as an impenetrable digital vault for institutional capital and sovereign wealth.
It deliberately omits smart contracts to minimize attack surfaces, focusing entirely on providing the most secure store-of-value network ever built.
Built with:
- Falcon-512 — NIST-standardized post-quantum signatures
- Kyber-1024 — post-quantum wallet encryption
- SHA3-256 — quantum-resistant double-hash Proof-of-Work
- Rust — memory-safe, high-performance implementation
| Resource | Description |
|---|---|
| Documentation | Node setup, mining, API reference, wallets |
| Whitepaper | Complete technical specification and architecture |
| Tokenomics | Economic model, supply schedule, and incentive design |
| Governance | Treasury multisig, PoS transition, on-chain voting roadmap |
| Contributing | Development guidelines and how to contribute |
| Security | Vulnerability reporting and security practices |
| Docker Hub | Official node image |
| Website | Official project website |
Docker is the recommended way to run a Quanta node. No Rust toolchain required.
docker pull xd637/quanta-node:latest
docker run -d \
--name quanta-node \
--restart always \
-p 3000:3000 -p 8333:8333 -p 7782:7782 -p 9090:9090 \
-v quanta-data:/home/quanta/quanta_data \
-v quanta-logs:/home/quanta/logs \
xd637/quanta-node:latestCheck it's running:
docker logs quanta-node --tail 20 -f
curl http://localhost:3000/health# Download and start
docker compose -f docker-compose.single.yml up -d
# Check status
docker exec -it quanta-node quanta status --rpc-port 7782For VPS deployment with NGINX and HTTPS, see the full deployment guide.
| Port | Protocol | Purpose |
|---|---|---|
| 3000 | HTTP | REST API |
| 8333 | TCP | P2P networking |
| 7782 | TCP | RPC server (CLI to node) |
| 9090 | HTTP | Prometheus metrics |
# Create HD wallet (24-word recovery phrase — recommended)
docker exec -it quanta-node quanta new_hd_wallet --file hd_wallet.json
# Show wallet address
docker exec -it quanta-node quanta wallet_address --file hd_wallet.json
# Start mining to your address
docker exec -d quanta-node quanta start_mining YOUR_ADDRESS --rpc-port 7782
# Check mining status
docker exec -it quanta-node quanta mining_status --rpc-port 7782
# Stop mining
docker exec -it quanta-node quanta stop_mining --rpc-port 7782If you prefer to build the binary directly:
Prerequisites: Rust 1.70+, Git, OpenSSL 1.1.1+
git clone https://github.com/quantachain/quanta.git
cd quanta
cargo build --release
# Run node
./target/release/quanta start -c quanta.tomlAll commands are available on the quanta binary (inside Docker via docker exec -it quanta-node quanta ...).
quanta start [--config FILE] [--network mainnet|testnet]
[--port API_PORT] [--network-port P2P_PORT] [--rpc-port RPC_PORT]
[--db PATH] [--bootstrap host:port,...] [--no-network] [--detach]
quanta status [--rpc-port 7782] # Running node status
quanta print_height [--rpc-port 7782] # Current block height
quanta peers [--rpc-port 7782] # Connected peers
quanta stop [--rpc-port 7782] # Graceful shutdownquanta new_wallet [--file wallet.qua] # Single keypair wallet
quanta new_hd_wallet [--file hd_wallet.json] [--accounts 3] # HD wallet (24-word mnemonic)
quanta wallet [--file wallet.qua] # Show balance
quanta wallet_address [--file wallet.qua] # Show address (offline)
quanta hd_wallet [--file hd_wallet.json] # Show HD wallet infoquanta start_mining <ADDRESS> [--rpc-port 7782] # Start mining
quanta mining_status [--rpc-port 7782] # Hashrate & last block
quanta stop_mining [--rpc-port 7782] # Stop miningquanta get_block <HEIGHT> [--rpc-port 7782] # Block by height
quanta stats [--db ./quanta_data] # Chain statistics
quanta validate [--db ./quanta_data] # Validate chain integrity
quanta send --wallet W --to ADDR --amount QUA # Send transactioncurl http://localhost:3000/health
curl http://localhost:3000/blocks/latest
curl http://localhost:3000/blocks/100
curl http://localhost:3000/accounts/0xYOUR_ADDRESS/balance
curl http://localhost:3000/accounts/0xYOUR_ADDRESS/nonce
curl http://localhost:3000/mempool
curl http://localhost:3000/network/stats
# Submit transaction
curl -X POST http://localhost:3000/transactions \
-H "Content-Type: application/json" \
-d '{"sender":"0x...","recipient":"0x...","amount":5000000,...}'| Component | Technology |
|---|---|
| Language | Rust 2021 |
| Async | Tokio 1.35 |
| Database | sled 0.34 (embedded, crash-safe) |
| P2P | Tokio TCP + custom protocol (bincode, zstd) |
| REST API | Axum 0.7 (port 3000) |
| RPC | Custom TCP JSON-RPC (port 7782) |
| PQ Signatures | pqcrypto-falcon 0.3.0 (pinned) — Falcon-512 |
| PQ Encryption | pqcrypto-kyber 0.8 — Kyber-1024 |
| Hashing | sha3 0.10 — SHA3-256 double-hash |
| KDF | argon2 0.5 — Argon2id wallet protection |
| HD Wallet | bip39 2.0 + hmac 0.12 — BIP39/BIP32 Falcon keys |
- Falcon-512 signatures — NIST Level 1, 897-byte pubkey, stateless, unlimited reuse
- 120+ TPS — parallel Rayon verification, LRU sig cache (100k entries), bloom filter mempool
- Account model — balance + nonce + locked_balances; not UTXO
- 30-second block time — 1,200 TX/block max, 2 MB limit
- Headers-first sync — Bitcoin IBD style, cumulative work-based peer selection
- Checkpoint system — hardcoded hashes prevent deep chain reorgs
- 3-of-5 Treasury Multisig —
ms69216b1d10425689704d5ae3b2a4aa17049f59b1, consensus-enforced
Transfer — Standard value transfer
TimeLockTransfer { unlock_height } — Cryptographic escrow / vaulting
MultiSigTransfer { signers_required } — Institutional M-of-N multisig
| Parameter | Value |
|---|---|
| Block reward | 100 QUA |
| Miner immediate (47.5%) | 47.5 QUA/block |
| Miner locked ~54.75 days (47.5%) | 47.5 QUA/block |
| Treasury (5%) | 5 QUA/block |
| Fee burn | 70% of all fees |
| Daily blocks | ~2,880 |
- Core blockchain, P2P, REST API, RPC server
- HD Wallet (BIP39/BIP32), Multisig (M-of-N Falcon-512)
- 3-of-5 Treasury Multisig — live on-chain
- Parallel Falcon-512 verification, LRU sig cache, bloom filter mempool
- Headers-first sync, cumulative work-based peer selection
- Cross-chain replay protection (
network_id) - Checkpoint system with hardcoded hashes
- Docker image + monitoring setup
- ✅ Public testnet live — chain at 91,000+ blocks, 2 active miners, 276 kH/s network hashrate
- ✅ Block explorer live at scan.quantachain.org
- ✅ Docker image:
xd637/quanta-node:latest - 🔄 External security audits + bug bounty program
- 🔄 Developer SDK and tooling
Comprehensive audit, penetration testing, protocol finalization
Code freeze, genesis configuration, multi-region bootstrap nodes, block explorer, desktop wallets
Genesis event, block explorer, production wallets, exchange integrations
Light client (SPV), hardware wallet support, PoW → PoS hybrid transition
| Package | Description |
|---|---|
quanta-sdk |
JS/TS SDK — build wallets, explorers, and integrations |
quanta-wasm |
Rust→WASM Falcon-512 crypto for browser and Node.js |
quantascan |
Block explorer |
quanta-wallet |
Chrome extension wallet |
Q: What makes QUANTA different from QRL and QAN? A: QUANTA uses NIST-standardized Falcon-512, delivers 120+ TPS, is written in production-grade Rust, and deliberately removes smart contracts to serve as a hyper-secure Institutional Settlement Vault.
Q: When is mainnet? A: Planned Q1 2027, after public testnet (Q2 2026) and security hardening (Q3 2026).
Q: Is there a token sale or ICO? A: No. 100% fair launch through mining. No pre-mine, no ICO, no insider allocation.
Q: Why Proof-of-Work? A: PoW enables a fair launch, has 15+ years of proven security, and provides Sybil resistance without stake centralization. PoS is planned as a future upgrade — see GOVERNANCE.md.
Q: What hardware do I need to mine? A: 4-core CPU, 8 GB RAM. QUANTA's SHA3-256 PoW is CPU-friendly — no specialized ASICs required.
Q: Why Falcon-512 (Level 1) and not Falcon-1024?
A: Level 1 gives 64-bit post-quantum security. Falcon-1024 would roughly double transaction sizes, cutting throughput by half. The sig_scheme field enables a soft-fork upgrade if cryptanalysis improves.
We welcome contributions. See CONTRIBUTING.md for guidelines.
git clone https://github.com/YOUR_USERNAME/quanta.git
git checkout -b feature/your-feature-name
cargo fmt && cargo clippy && cargo test
git commit -m "feat: your feature description"
git push origin feature/your-feature-nameQUANTA: Engineering a Production-Ready Post-Quantum Blockchain with Falcon-512 Lattice Signatures Kishore K — February 2026 DOI: 10.5281/zenodo.18753528
@misc{quanta2026,
title = {QUANTA: Engineering a Production-Ready Post-Quantum Blockchain
with Falcon-512 Lattice Signatures},
author = {Kishore K},
year = {2026},
month = feb,
doi = {10.5281/zenodo.18753528},
url = {https://doi.org/10.5281/zenodo.18753528}
}MIT License — see LICENSE for details.
Copyright (c) 2026 Kishore K — QUANTA Development Team
Build for the Future. Secure Against Quantum.
Kishore K, Founder — admin@quantachain.org — quantachain.org