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 | 0x2c7754df…b4dba4 | – |
| node2 | 0xc02c5c31…3a60f4 | – |
| node3 | 0xd1b53e93…08b9a3 | – |
| node4 | 0xdf3ba43e…c9a0e9 | – |
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.
Validator-Set Changesqbft_getPendingVotes · live
No validator-set changes are pending. Any proposed add or removal appears here as validators cast their on-chain votes, and takes effect once 3 of 4 have voted for the same address.
Signing Participationqbft_getSignerMetrics · recent window
| Node | Address | Blocks Proposed | Last Proposed Block |
|---|---|---|---|
| node1 | 0x2c7754df…b4dba4 | 25 | #4,047,213 |
| node2 | 0xc02c5c31…3a60f4 | 25 | #4,047,214 |
| node3 | 0xd1b53e93…08b9a3 | 25 | #4,047,211 |
| node4 | 0xdf3ba43e…c9a0e9 | 25 | #4,047,212 |
An on-chain, auditable record of which validators are producing blocks. Even participation across the set indicates a healthy QBFT network.
Who operates the validators, All 4 validators are currently operated by Knightsbridge Group. KXCO Armature is permissioned by design: the validator set is known and centrally operated today. The roadmap moves from this transparent permissioned set toward institutional co-validation, where onboarded institutions and custodians run validators under a published admission policy.
Security Model, KXCO Armature uses QBFT with 4 validators, tolerating up to 1 Byzantine (malicious or faulty) node. Blocks are sealed by QBFT proof-of-authority (classical secp256k1) with deterministic finality; each finalised block is additionally attested with validator ML-DSA-65 (NIST FIPS-204) keys, and post-quantum consensus signing is on the roadmap. 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.