Consensus Message
Pronunciation: kuhn-SEN-sus MES-ij
Definition
A consensus message is a protocol message exchanged by blockchain nodes to propose blocks, vote, attest, commit, report state, or coordinate progress toward agreement. It usually includes a height or slot, round or epoch, message type, block reference, and cryptographic authentication. Validity depends on the sender’s current consensus role and the exact protocol state.
Overview
Meaning and scope
A consensus message is a protocol message exchanged by blockchain nodes to propose blocks, vote, attest, commit, report state, or coordinate progress toward agreement. It usually includes a height or slot, round or epoch, message type, block reference, and cryptographic authentication. Validity depends on the sender’s current consensus role and the exact protocol state.
Mechanism and operation
A proposer can broadcast a candidate block, validators can send prevotes or precommits, and peers can exchange information about known votes or current round state. Proof-of-stake systems can use attestations that support a head and checkpoints. Each message is interpreted within a specific height, round, slot, committee, or epoch. Authentication prevents an observer from inventing another validator’s message, but verification also checks context. The signer must belong to the relevant validator set, the message must use the expected domain and version, and duplicate or conflicting messages may constitute slashable evidence. Nodes collect them, apply locking and fork-choice rules, and determine whether their combined voting power reaches a Consensus Quorum.
Practical payment example
During a liveness incident, validator logs show delayed signed votes. The engineering team identifies the message type and round to separate networking delay from invalid consensus signatures.
Operational checks
Delayed, missing, or reordered messages can slow progress without violating safety. Conflicting messages from one validator can reveal equivocation, while conflicting messages from different validators may be normal before the protocol converges. Operators should monitor message propagation, participation, and validation errors without exposing private signing keys.
Distinctions and limits
Consensus protocols rely on structured communication rather than informal node agreement. A correct Digital Signature on the wrong height or message type is not a valid consensus contribution.
Related reading
Related definitions: Digital Signature, Consensus Quorum.
Example
During a liveness incident, validator logs show delayed signed votes. The engineering team identifies the message type and round to separate networking delay from invalid consensus signatures.
Comparison
A correct Digital Signature on the wrong height or message type is not a valid consensus contribution. Conflicting messages from one validator can reveal equivocation, while conflicting messages from different validators may be normal before the protocol converges.
Key Takeaway
A consensus message is an authenticated input to agreement; only protocol processing and sufficient voting weight turn messages into commitment or finality.
Sources
- CometBFT Consensus Message Types — CometBFT (2026-08-02)
- CometBFT Byzantine Consensus Algorithm — CometBFT (2026-08-02)
- Ethereum Proof-of-Stake — Ethereum Foundation (2026-08-02)