How Does a Consortium Blockchain Achieve Consensus?

A consortium blockchain typically uses a consensus mechanism like Delegated Proof-of-Stake (DPoS) or a Byzantine Fault Tolerance (BFT) variant, such as Practical Byzantine Fault Tolerance (pBFT). Consensus is achieved by a pre-selected, limited set of trusted validator nodes, which are usually the member organizations.

These nodes validate transactions and propose new blocks. A supermajority of these trusted nodes must agree on the block's validity for it to be added to the chain.

This approach provides high transaction throughput and faster finality compared to public chains.

How Does DPoS Aim to Solve the Scalability Issue in Blockchain?
What Is a Potential Drawback of the Limited Set of Validators in DPoS?
What Is the Maximum Fraction of Malicious Nodes a BFT System Can Tolerate While Maintaining Safety?
How Does a BFT-based Consensus Mechanism Prevent a Malicious Node from Disrupting the Network?
How Do ‘Byzantine Fault Tolerance’ (BFT) Consensus Mechanisms Offer Stronger Finality?
What Is a “Byzantine Fault Tolerance” (BFT) Consensus Mechanism?
What Is the Key Trade-off between DPoS and Pure PoS?
How Does ‘Delegated Proof-of-Stake’ (DPoS) Modify the Basic PoS Model?

Glossar