WINMAR CHAIN

GOVERNANCE / VALIDATOR NETWORK

Accountable consensus.
Progressive independence.

Winmar Chain separates protocol governance, validator authorization, treasury control, and public access—then expands the validator set by measurable operational independence.

LIVE MAINNET4

authorized validators

FINALITY QUORUM3

commits per block

TARGET TOPOLOGY11

independent validators

TARGET QUORUM8

commits per block

Consensus scales by quorum, not server count

Q(N) = ceil(2N / 3)     f_max = floor((N - 1) / 3)

Current: N = 4 → Q = 3 → f_max = 1
Target:  N = 11 → Q = 8 → f_max = 3

Eleven machines controlled by one operator do not represent eleven independent trust domains. Expansion prioritizes distinct operators, regions, cloud providers, network paths, signing custody, and incident authority.

Validator admission is an evidence-based process

Disclosure

Candidate identity, jurisdiction, operator, infrastructure, custody model, monitoring, backups, and escalation contacts.

Technical qualification

A synchronized non-validating node demonstrates stable peers, reproducible deployment, restore testing, and health telemetry.

Independence review

Governance evaluates common-control and correlated-failure exposure against the active validator set.

On-chain activation

Membership changes become effective only after the authorized validator-set update is finalized and independently verified.

No single key should control the network

KEY DOMAIN
AUTHORITY
RECOMMENDED BOUNDARY
Validator signing
QBFT proposal and voting
Dedicated host or controlled remote signer
Treasury multisig
Governed asset movement
Separated signers and approval threshold
Contract administration
Upgrade, pause, and roles
Multisig plus timelock where applicable
Deployment key
Contract publication
Short-lived account with minimal balance
Monitoring identity
Read-only telemetry
No signing or governance authority

Operational evidence, not promises

IDENTITY

Canonical parameters

Chain ID, genesis hash, client version, and validator set must be independently observable.

CONSENSUS

Block progression

Height, proposer activity, peer health, round changes, and finality stalls are monitored continuously.

ACCESS

RPC and explorer

Public services are isolated from validator signing and checked for chain identity, freshness, and availability.

CHANGE

Release discipline

Material upgrades require review, test rehearsal, coordinated activation, rollback planning, and release records.

INCIDENTS

Escalation

Quorum loss, key exposure, chain-ID mismatch, or unauthorized membership change is treated as critical.

ROADMAP

11-validator target

Growth is staged and verified; the website will not represent planned validators as currently active.

GOVERNANCE PRINCIPLE

Trust must be explicit,
bounded, and observable.

Read full specification ↗