Consensus State

Overview

Meaning and scope

Consensus state is the protocol data a node maintains to track agreement progress, participants, votes, rounds, checkpoints, and finalized decisions. This state differs from application state such as account balances and contract storage. Consensus state determines which execution result is canonical, while application execution computes the contents committed by that result.

Mechanism and operation

Consensus state records where a node is within the agreement process. It can include the current height, round, validator set, locked proposal, received votes, justified or finalized checkpoints, randomness, and other variables required by the protocol state machine. Node software must persist and restore safety-critical fields without double voting or accepting stale context. Operators should back up only supported data, protect validator signing history, and verify state after recovery. Consensus State should be tied to a specific network, block hash, protocol version, and state-transition rules. For Consensus State, a state value without that context can become ambiguous after a reorganization, upgrade, or replay on another network even when the serialized bytes appear valid.

Practical payment example

An engineer reviews a validator node stuck in a pre-commit phase. Comparing its local consensus state with peers helps distinguish a protocol stall from a slow API endpoint.

Operational checks

A commitment associated with Consensus State proves only what its verification rules establish. Archive requirements, pruning, snapshots, and state expiry can change which historical observations remain available from ordinary infrastructure. Applications should record the canonical block reference, query method, proof or response, and node capability used to obtain it.

Distinctions and limits

Applications generally consume finalized outputs rather than modifying consensus state directly. For Consensus State, commitment integrity, data availability, execution correctness, and historical retrievability are separate properties; a valid root or proof does not by itself guarantee that every application can reconstruct the underlying state.

Related reading

Related definitions: Consensus, validator set.