You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Post-quantum secure blockchain using Falcon-512 signatures and Asynchronous Byzantine Fault Tolerance (AlephBFT).
v2.0.1 — TESTNET UPDATE (2026-07-02)
Minor update and performance improvements on top of the V2 Hard Fork.
Genesis hash remains: ae37fe2f40a7e7dbe6d2d1337f260d57185ef5fb169008e2600f245809fd1fbf
This is a pre-release testnet build. Do not use real funds. APIs and chain parameters may change between alpha releases.
What Changed in v2.0.1
Hard Fork (Network Magic Bump) — Network magic bytes bumped to Q2T6 to isolate v2.0.1 nodes due to breaking block size and consensus changes.
Smart Contracts V3 — Full AI contract layer with 5 native templates (Escrow, AgentJob, AgentBid, Stream, AgentRegistry).
Staking & Slashing — Full validator staking, slashing, and unbonding logic. Open validator registration.
Performance Fixes — Block size increased to 4MB, TPS ceiling ~400. Round-robin proposer timeout removed to guarantee 6s blocks.
Validator Setup — Added setup-validator.sh script for secure, verifiable deployment.
HD Wallet Key Derivation — Deterministic Falcon-512 keypair derivation from account seed.
Block timing fixed (v2.0.0) — Blocks were slowing from 6s to 1–2h due to timestamp drift.
Genesis Reset (v2.0.0) — Replaced lost validator wallet, rotated faucet wallets, new genesis hash.
🚨 V2 Hard Fork Details 🚨
Consensus Engine: Migrated from SHA3-256 Proof of Work to AlephBFT (Asynchronous Byzantine Fault Tolerance).
Network Isolation: Updated network magic bytes to Q2T4 to prevent old nodes from connecting to the new consensus network.
Mining Removed: All start_mining commands and the quanta-miner binary have been removed.
AI Agent Support: Added headless QUANTA_WALLET_PASSWORD environment variable support for automated AI escrow workflows.
HD Wallets: The CLI wallet has been completely rewritten to support deterministic hierarchical generation natively.
Persistent Crash Recovery: AlephBFT DAG state is now persisted to disk (alephbft_backup.dat), allowing seamless recovery and network rejoin after node restarts.
🔄 Clean Start Guide (Wipe Data & Resync from Genesis)
You MUST perform a clean start to join the V2 Testnet!
The V2 BFT consensus engine uses a different block structure and state machine. It will crash if it reads old V1 PoW blocks.
Bare Metal / VPS (no Docker)
pkill -f "quanta start"# stop the old node
rm -rf ./quanta_testnet_data # WIPE THE OLD POW CHAIN DATA!
cargo build --release # compile the new V2 binary
./target/release/quanta start -c quanta.toml
Docker Validators (Safe Wipe)
If you are an existing validator using Docker, you must wipe the old chain data but KEEP your validator wallet file. Since you may have named your wallet file something other than validator.qua, you must be extremely careful.
Caution
If you run the rm -rf command below without successfully moving your wallet out first, you will delete your validator wallet forever!
Step 1: Stop your node and move your wallet out of the data folder. (Replace validator.qua with your actual wallet filename if it is different!)
⚠️ ATTENTION: This is currently a strictly permissioned testnet designed only for testing. Only the validators explicitly hardcoded in the Genesis set can run a node and produce blocks.
Once the network matures, we will implement full DPoS, allowing anyone to stake and participate in consensus. Until then, if you would like early access to participate, please email: contact@quantachain.org
If you have been selected as a validator, follow these exact instructions to spin up your validator node and connect to the core network using Docker:
1. Create a Wallet and Get Your Key
You must generate a raw wallet and provide the public key to the core team to be whitelisted in the Genesis block.
docker run --rm -it xd637/quanta-node:latest quanta-wallet new-raw --file /tmp/validator.qua
2. Directory Setup
Create the directory where your blockchain data will live. We recommend adding _v2 to avoid mixing it with any old testnet data:
mkdir -p ~/quanta_data_v2
3. Place Your Wallet File
Move your validator wallet file (e.g., validator.qua or whatever you named it) directly into the ~/quanta_data_v2 directory you just created.
Your folder should look exactly like this:
~/quanta_data_v2/
└── validator.qua
(Note: You do NOT need the genesis.json or quanta.toml files! The latest network configuration is securely baked directly into the V2 Docker image.)
4. Pull the Latest Image & Start the Node
Run the following Docker commands to pull the latest V2 build, launch your node, connect to the Bootstrap node, and begin proposing blocks.
Important
Before running the second command below, you MUST change two things:
Change "YOUR_PASSWORD_HERE" to your actual wallet password.
Change validator.qua at the very end of the command to match the exact name of your wallet file.
# New HD Wallet (Recommended)
quanta-wallet new --file my_wallet.json
# New Raw Wallet
quanta-wallet new-raw --file my_raw.qua
# AI Headless Mode (Set env var to skip password prompts)export QUANTA_WALLET_PASSWORD="your_password"
quanta-wallet info --file my_wallet.json
Ports
Port
Service
3000
REST API
8333
P2P Network
7782
RPC
9090
Prometheus Metrics
License
QUANTACHAIN operates under an Open-Core Dual License model:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
QuantaChain Testnet — V2 Release (v2.0.1)
Post-quantum secure blockchain using Falcon-512 signatures and Asynchronous Byzantine Fault Tolerance (AlephBFT).
This is a pre-release testnet build. Do not use real funds. APIs and chain parameters may change between alpha releases.
What Changed in v2.0.1
Q2T6to isolate v2.0.1 nodes due to breaking block size and consensus changes.setup-validator.shscript for secure, verifiable deployment.🚨 V2 Hard Fork Details 🚨
Q2T4to prevent old nodes from connecting to the new consensus network.start_miningcommands and thequanta-minerbinary have been removed.QUANTA_WALLET_PASSWORDenvironment variable support for automated AI escrow workflows.alephbft_backup.dat), allowing seamless recovery and network rejoin after node restarts.Genesis Block
1780704001(2026-06-06 00:00:01 UTC)ae37fe2f40a7e7dbe6d2d1337f260d57185ef5fb169008e2600f245809fd1fbf0xec4f49553e31f22b27a83036a044aff7d697f524🔄 Clean Start Guide (Wipe Data & Resync from Genesis)
Bare Metal / VPS (no Docker)
Docker Validators (Safe Wipe)
If you are an existing validator using Docker, you must wipe the old chain data but KEEP your validator wallet file. Since you may have named your wallet file something other than
validator.qua, you must be extremely careful.Caution
If you run the
rm -rfcommand below without successfully moving your wallet out first, you will delete your validator wallet forever!Step 1: Stop your node and move your wallet out of the data folder. (Replace
validator.quawith your actual wallet filename if it is different!)Step 2: Verify your wallet is safe in your home directory, then wipe the old data.
Step 3: Move your wallet back in (again, replacing
validator.quawith your actual filename if different), and restart the node.Validator Setup (Docker)
If you have been selected as a validator, follow these exact instructions to spin up your validator node and connect to the core network using Docker:
1. Create a Wallet and Get Your Key
You must generate a raw wallet and provide the public key to the core team to be whitelisted in the Genesis block.
2. Directory Setup
Create the directory where your blockchain data will live. We recommend adding
_v2to avoid mixing it with any old testnet data:mkdir -p ~/quanta_data_v23. Place Your Wallet File
Move your validator wallet file (e.g.,
validator.quaor whatever you named it) directly into the~/quanta_data_v2directory you just created.Your folder should look exactly like this:
(Note: You do NOT need the
genesis.jsonorquanta.tomlfiles! The latest network configuration is securely baked directly into the V2 Docker image.)4. Pull the Latest Image & Start the Node
Run the following Docker commands to pull the latest V2 build, launch your node, connect to the Bootstrap node, and begin proposing blocks.
Important
Before running the second command below, you MUST change two things:
"YOUR_PASSWORD_HERE"to your actual wallet password.validator.quaat the very end of the command to match the exact name of your wallet file.Wallet Management
Ports
3000833377829090License
QUANTACHAIN operates under an Open-Core Dual License model:
For commercial licensing: contact@quantachain.org
This discussion was created from the release Quantachain Testnet Alpha V2.0.1.
All reactions