Consensus is the process that allows distributed participants to converge on a common history even when messages are delayed, nodes fail or competing blocks appear.
What you'll understand
- Consensus discussions often separate safety and liveness.
- A fork-choice rule tells nodes which branch to follow when more than one valid candidate history exists.
- Finality describes the point at which a transaction or block is treated as extremely difficult or protocol-invalid to reverse.
- A blockchain consensus protocol includes message rules, validation logic, incentives, networking assumptions and fork-choice behavior.
Safety and liveness
Consensus discussions often separate safety and liveness. Safety asks whether honest participants can avoid accepting conflicting final histories. Liveness asks whether the system can continue making progress.
Different protocols balance these properties under different network assumptions.
Fork choice
A fork-choice rule tells nodes which branch to follow when more than one valid candidate history exists. Proof of work and proof of stake typically use different signals for this decision.
Temporary forks do not necessarily mean a blockchain has failed; some are expected and resolved by protocol rules.
Finality
Finality describes the point at which a transaction or block is treated as extremely difficult or protocol-invalid to reverse. Some systems have probabilistic finality, while others add explicit finality votes.
Application developers choose confirmation policies based on the network's model and their own risk tolerance.
Consensus is more than voting
A blockchain consensus protocol includes message rules, validation logic, incentives, networking assumptions and fork-choice behavior. Calling it 'voting' can be useful as an analogy, but it is incomplete.
The clearest way to understand this topic is to separate the protocol, the digital asset, the software interface and any third-party service. Each layer has different responsibilities, dependencies and risks.
