Consensus Node

Definition

A consensus node is a network participant that runs the consensus protocol or supports it by validating, relaying, and tracking blocks and consensus messages. Some consensus nodes also hold validator keys and cast votes, while others are non-validating full nodes. The role should not be inferred from the word node alone.

Overview

Meaning and scope

Mechanism and operation

Consensus nodes maintain a view of blockchain height, round or slot, candidate blocks, votes, and canonical state. They verify incoming data, relay messages to peers, and apply the fork-choice or state-machine rules that determine progress. In CometBFT, a node can participate in relaying proposals, blocks, and votes without possessing a validator private key. A validator node adds the ability and responsibility to sign consensus votes. A non-validating node can independently verify history and serve application queries but contributes no voting power. A validator node influences consensus according to its assigned weight and must protect an online signing key from compromise or double signing.

Practical payment example

A network deployment includes validating and non-validating nodes. The operator does not assume a public RPC replica participates in consensus just because it returns current block numbers.

Operational checks

One operator may run several machines, yet the protocol can still recognize only one validator identity or voting allocation. A consensus node can be synchronized, lagging, partitioned, misconfigured, or connected to the wrong network. Applications should verify chain identifiers, software versions, peer health, and current height before trusting responses.

Distinctions and limits

A node’s local Best Chain is not automatically the global final state, especially during an incident. A healthy node does not guarantee network health, and a failed node does not necessarily mean Consensus Failure.

Related definitions: Best Chain, Consensus Failure.

Example