Consensus for the quantum era.
An independent Rust proof-of-stake prototype covering account signatures, authenticated transport, staking consensus and a replayable ledger.
Candidate network, not public mainnetProtocol foundations
ML-DSA-87 is used for account and consensus signatures. Node transport combines mutual TLS 1.3 with P-384 + ML-KEM-1024 hybrid key exchange. System security still depends on implementation, key management and reviewed upgrades.
How PoS reaches consensus
The candidate uses stake-weighted BFT with strictly more than two-thirds of weight required to commit. Its assumptions include less than one-third Byzantine stake. Loss of quorum can halt blocks; node or IP counts alone do not establish decentralization.
Holding and staking
Users need actual assets from a valid issuance or transfer before staking. Holding does not require staking. Running a computer or an empty node does not create initial funds. Staking carries slashing and exit constraints; there is no APY commitment.
Current implementation boundaries
- Candidate limits include 4,096 total accounts and 128 active validators.
- The v0.2 GUI wallet is local-only. Candidate network accounts use the pqnode CLI.
- There is no general-purpose contract VM or verified bridge.