Topology
How KMCoin separates block producers, validators, and transaction hosts while keeping the current validator flow deterministic.
Producer, Validator, Host
Transaction hosts collect player messages, block producers create candidate blocks, and validators verify signed peer data before final settlement.
Collects player messages from game or chat servers.
Creates candidate blocks from hosted servers or auditable APIs.
Verifies signed peer data, queue majority, and API-backed blocks.
Signed Validator Group
Validators share signed TCP block and consensus messages. Candidate blocks move through majority queue snapshots before final network processing.
A validator verifies signed peer messages, checks majority queue snapshots, and maintains the KMCoin ledger.
Block producers create candidates, and validators share them before majority queue settlement.
Peers identify each other with public keys and exchange signed data through the validator group.
Validators share consensus updates after network blocks settle.
Deterministic Scaling
KMCoin starts with deterministic validator grouping. Verified API data can later be gossiped for availability while official settlement remains tied to agreed group rules.
Deterministic Validator Groups
KMCoin begins with rigid validator groups, starting from a seven-node model. Validator addition transactions can be sorted by the timestamp of the KMCoin block that contains them, so every node can independently derive group placement.
Signed TCP Peer Network
Validators share blocks and consensus snapshots through signed TCP messages. Public keys identify peers, replay windows reject old messages, and rate limits protect the network from repeated malformed traffic.
Majority Queue Settlement
Candidate blocks enter shared queue snapshots before final processing. A validator promotes a block only after the configured majority of source snapshots contains the same candidate and the settlement age has elapsed.
Auditable API Blocks
Steam blocks can be rebuilt and checked against public API data. Because validators can verify the block content itself, API-backed blocks can support wider availability testing as the network grows.
Transaction Intake Hosts
Hosted game servers can act as transaction intake layers instead of trusted block producers, such as Unturned for SteamID transactions or Minecraft and Rust for legacy player-name transactions.