Governance
Validators (n)
4
Fault Tolerance (f)
1
Vote Threshold
3 of 4
Block Period
2s
Current Validator Set
| Node | Classical Address | PQC Address (ML-DSA-65) |
|---|---|---|
| node1 | 0xc0f4710f…2df91e | 0x563e34dd…92eaf2 |
| node2 | 0x7f74a28c…42b093 | 0x772cf9d1…9e82d3 |
| node3 | 0x58b92936…e79fbf | 0x3556b9ca…c6aafb |
| node4 | 0xc2b059ea…5e46d4 | 0x95c755c7…06c601 |
QBFT Consensus Model
- Algorithm
- Quorum Byzantine Fault Tolerance (QBFT)
- Finality
- Deterministic — no forks, no reorgs
- Fault formula
- f = ⌊(n−1)/3⌋ = ⌊(4−1)/3⌋ = 1
- Quorum
- 2f+1 = 3 validators must sign each block
- Request timeout
- 10s per round
- Block period
- 2s target
Adding or Removing Validators
Validator set changes require 3 of 4 current validators to each cast a vote via their node's authenticated JSON-RPC endpoint.
// Propose add:
qbft_proposeValidatorVote("0xNEW_ADDR", true)
// Propose remove:
qbft_proposeValidatorVote("0xOLD_ADDR", false)
Each validator operator must call this independently. Once 3 votes are cast for the same address, the change takes effect at the next block.
Security Model — KXCO Armature uses QBFT with 4 validators, tolerating up to 1 Byzantine (malicious or faulty) node. With hybrid PQC, the network remains secure against both classical and quantum adversaries. Validator set changes are governed entirely on-chain through the QBFT vote mechanism — no admin keys, no multisig.See Validator Dashboard for live block production data.