Avalanche C-Chain Protocol

• Avalanche C-Chain is a linear, EVM-compatible blockchain that uses the Snowman consensus to achieve rapid finality and probabilistic Byzantine fault tolerance.
• It leverages metastable subsampling and randomized voting, allowing nodes to switch preferences based on sampled network consensus, ensuring safety and liveness.
• Empirical evaluations show high throughput and sub-second latency across thousands of nodes, with tunable parameters balancing security and performance under adversarial conditions.

Avalanche’s C-Chain is a linear, EVM-compatible blockchain that leverages the Snowman protocol, a variant of the leaderless metastable consensus mechanism introduced by the Snow protocol family, to achieve probabilistic Byzantine fault tolerance. Unlike blockchains relying on proof-of-work, Avalanche C-Chain utilizes network subsampling and metastable randomised voting to deliver rapid block finality with high throughput, scalable to thousands of nodes, and safety and liveness guarantees controlled via explicit protocol parameters. The protocol architecture, decision process, and performance are described in detail by the Avalanche team (Rocket et al., 2019).

1. Protocol Architecture: From Snow Family to Avalanche C-Chain

The C-Chain’s consensus mechanism is founded on the Snow protocol family, which comprises single-decree protocols—Slush, Snowflake, and Snowball—based on repeated random sampling and majority voting. Avalanche, the system described in (Rocket et al., 2019), deploys multiple Snowball instances on a DAG (directed acyclic graph) of transactions to construct a UTXO ledger (the so-called X-Chain). In contrast, the C-Chain employs a strictly linear EVM chain on which each block height is adjudicated as an independent single-decree instance using the Snowman protocol.

Snowman, a specialization of Snowball, restricts consensus to one block per height. At each height $h$, all blocks referencing the same parent at $h-1$ constitute a conflict set, with each such block contending for finality. Consensus at each height completes before block proposals for height $h+1$ proceed. This architecture preserves linearity—there is no DAG for the C-Chain branch.

2. Metastable Subsampling and Voting Mechanism

Snowman consensus at each block height $h$ proceeds as follows. In each round, a node:

• Uniformly selects $k$ peers from the validator set.
• Issues a query containing its current block preference (represented by the hash of the preferred block at height $h$).
• Receives $k$ replies, each denoting the peer’s current preference.
• Counts the fraction of votes for each candidate block.

The node applies the following state updates:

• If $\geq \alpha$ replies favor a block different from the node’s own, the node flips its preference and resets its consecutive-success counter.
• If $\geq \alpha$ replies favor its current preference, it increments its consecutive-success counter.
• Otherwise, the counter is reset.

Upon observing $\beta$ consecutive successful confirmations for the same candidate, the node marks that block as accepted and ceases participation for that height. This is the metastable drift: any majority bias present in the network will stochastically amplify until a high degree of unanimity is achieved throughout the network, making reversal after acceptance exponentially unlikely.

3. Probabilistic Safety and Liveness Guarantees

Key protocol parameters include the validator count $h-1$0, sample size $h-1$1, majority threshold $h-1$2, consecutive-success threshold $h-1$3, adversarial fraction $h-1$4, and irreversibility drift $h-1$5 (fraction of honest nodes having accepted a value).

Safety ($h-1$6-safety):

Once the network exhibits a $h-1$7-majority for one candidate, the probability of a minority candidate overtaking (reversion) is bounded using a hypergeometric tail:

$h-1$8

Tuning $h-1$9 so that acceptance only occurs when $h+1$0 is high ensures:

$h+1$1

Practical values can achieve $h+1$2.

Liveness:

A continuous-time Markov chain (CTMC) birth-death analysis demonstrates the following:

• From any biased initial configuration ($h+1$3 initial support), consensus terminates in finite expected time, and with strictly positive probability within any bounded time window.
• With $h+1$4 and $h+1$5, consensus is reached in $h+1$6 rounds with high probability:

$h+1$7

for any constants $h+1$8.

4. Specialization: Snowball to Snowman Linear Chain

The transition from generic Snow protocols to Snowman for the C-Chain involves:

• Defining conflict sets at each height as all blocks with the same parent at $h+1$9.
• Each node selects a preferred block at each height and performs a single sampling round for every new block, awarding a chit $h$0; confidence $h$1 is the cumulative chit total in the descendant chain.
• For height $h$2, the node prefers the block with maximal confidence and applies $h$3-majority, $h$4-consecutive logic as previously described.
• Upon $h$5 consecutive confirmations, the block achieves finality, and the node advances to height $h$6.
• No DAG structure exists for C-Chain; strict linearity is enforced, but the protocol inherits the metastability and rapid convergence rates of Snowball.

5. Empirical Performance and Robustness

Experimental evaluation on up to $h$7 geo-replicated EC2 nodes, each capped at 20 Mbps, demonstrates the following key metrics:

Metric	Value	Conditions
Throughput	~3400 tps (250 B/tx)	Crypto-bound; up to ~9000 tps with sigs removed
Median Latency	1.35 s	2000-node, geo-distributed
99th pct. Latency	4 s	As above
Adversarial Load	up to 25% conflicts	Linear throughput effect, slightly lower latency

Signature verification is the main system bottleneck. Increasing adversarial transaction load proportionally reduces throughput but slightly lowers latency due to lighter honest load.

6. Tunable Parameters and Operational Trade-offs

The protocol’s security and performance profile can be tailored by adjusting three core parameters:

• $h$8 (sample size): Larger $h$9 exponentially decreases safety failure probability $k$0, with marginal communication overhead.
• $k$1 (majority threshold), typically $k$2: Higher $k$3 accelerates drift per round, yet requires more flips for preference inversions.
• $k$4 (consecutive wins): Lower values (e.g., $k$5–$k$6) can be used for optimistic “early commit,” higher values ($k$7–$k$8) for full finality, with increased finality confidence but slight latency increase.

Parameter selection yields:

$k$9

This provides explicit trade-offs: lowering finality latency versus minimizing the probability of conflicting acceptance events.

7. Security Model and Comparative Guarantees

The C-Chain’s protocol admits a highly tunable security-liveness regime equivalent in safety guarantees to PBFT-class protocols, without reliance on leadership, deterministic rounds, or heavy communication. The leaderless, green (zero-PoW) design does not require accurate participant enumeration and exhibits quiescence—no activity occurs when there are no proposals. Safety and liveness scale as a function of adversarial fraction, sample size, and threshold selection, enabling operation in both permissioned and permissionless environments with sub-second latency and throughput comparable to, or exceeding, longest-chain PoW-based systems (Rocket et al., 2019).