Snowman Consensus

Overview

Snowman is a chain-structured consensus protocol in the Avalanche family. Nodes repeatedly query sampled validators, update their preference, and accumulate confidence until a block and its ancestors satisfy finalization conditions. Because blocks form a linear parent-child history, Snowman suits smart-contract platforms that require ordered execution. Its safety and liveness depend on configured sample sizes, quorum thresholds, repeated successful polls, network assumptions, and the fraction of adversarial stake. Probabilistic finality means confidence grows through the protocol’s repeated sampling process rather than a single deterministic voting round. Operators must use compatible parameters and protect validator availability. Applications should rely on the network’s accepted finality status instead of inventing a fixed confirmation count without understanding the implementation.

A mechanism’s label does not define those details across every implementation. Evaluation should cover the complete decision process: who may propose data, how other participants validate it, how competing histories are ranked, and what evidence makes an outcome difficult or impossible to reverse. Security assumptions depend on the resource or authority used to influence consensus, participant concentration, network timing, client behavior, and the cost of equivocation, censorship, or history revision. Safety, liveness, and accountability should be assessed separately under partitions and coordinated failures.

Local block visibility is only an intermediate signal; canonical status, execution outcome, and protocol-level settlement evidence must also be checked before fulfillment becomes irreversible. Payment applications relying on Snowman Consensus need network-specific confirmation and finality policies. Practical implication: Snowman reaches linear-chain finality through repeated validator sampling, with guarantees determined by stake, parameters, and network conditions.