Consensus Algorithms and Protocols Flashcards

Which of the following BEST describes the primary difference in how Delegated Proof-of-Stake (DPoS) and standard Proof-of-Stake (PoS) select block validators?

Answer: In PoS, any stakeholder can be chosen to validate based on stake size, while in DPoS, stakeholders vote to elect a smaller, fixed number of delegates who then validate blocks.

The core distinction between PoS and DPoS lies in the selection process. In a typical PoS system, any user who stakes the required amount of cryptocurrency is eligible to be algorithmically selected to validate a block, often with a higher stake increasing their chances. In contrast, DPoS introduces a democratic layer where token holders use their stake to vote for a limited number of 'delegates' or 'witnesses' who are then responsible for block production and validation.

A consortium blockchain for supply chain management requires high transaction throughput and low latency. The participants are known and trusted entities. Which consensus algorithm is most suitable for this scenario?

Answer: Proof-of-Authority (PoA)

Proof-of-Authority (PoA) is ideal for permissioned or private blockchains where participants are known and have a reputation to uphold. In PoA, a set of pre-approved 'authorities' (validators) are responsible for creating blocks. Since validators are trusted and their identities are known, this model forgoes the need for computationally intensive puzzles (PoW) or large capital stakes (PoS), resulting in significantly higher throughput and faster finality, which is crucial for enterprise use cases like supply chain management.

What is meant by 'probabilistic finality' in the context of a Proof-of-Work (PoW) blockchain like Bitcoin?

Answer: The assurance of a transaction's immutability increases as more blocks are added after it, but it never reaches absolute certainty.

In Proof-of-Work systems, finality is probabilistic. This means that as more blocks are mined on top of the block containing a specific transaction (i.e., as it gets more 'confirmations'), the likelihood of that transaction being reversed through a chain reorganization becomes exponentially smaller. However, there is always a theoretical, albeit negligible, possibility that a longer, competing chain could emerge and invalidate it. Therefore, finality is a matter of increasing probability rather than absolute, deterministic certainty.

The Byzantine Generals' Problem is a fundamental challenge in distributed computing that consensus algorithms aim to solve. What is the primary goal of a Byzantine Fault Tolerant (BFT) system?

Answer: To allow a distributed system to reach a reliable consensus, even if some nodes fail or act maliciously.

Byzantine Fault Tolerance (BFT) is the property of a system that allows it to continue operating correctly and reach consensus despite the presence of faulty or malicious (Byzantine) nodes. The core problem is for honest 'generals' (nodes) to agree on a unified action despite receiving potentially conflicting messages from traitorous generals. A BFT consensus mechanism ensures the network's integrity as long as the number of malicious nodes does not exceed a certain threshold (typically one-third).

A development team is designing a permissioned blockchain for a financial consortium that requires very fast transaction finality and can tolerate a small number of known, trusted validators. The system must be able to withstand up to one-third of these validators failing or acting maliciously. Which specific consensus algorithm fits these requirements best?

Answer: Practical Byzantine Fault Tolerance (PBFT)

Practical Byzantine Fault Tolerance (PBFT) is a consensus algorithm designed for distributed systems that provides high performance, low latency, and deterministic finality. It is particularly well-suited for permissioned networks with a known, limited number of validators. A key feature of PBFT is its ability to reach consensus and guarantee correctness as long as fewer than one-third of the nodes are Byzantine (malicious or faulty).

Which of the following is a key difference between how Proof-of-Work (PoW) and Proof-of-Stake (PoS) systems penalize malicious actors?

Answer: PoW imposes an indirect penalty through wasted computational energy and resources, while PoS imposes a direct financial penalty by 'slashing' the actor's staked tokens.

In a Proof-of-Work system, a malicious actor who tries to create an invalid block or attack the network wastes significant amounts of electricity and computational resources with no chance of earning a reward, which is an implicit economic penalty. In a Proof-of-Stake system, the penalty is direct and explicit: validators who act maliciously (e.g., by double-signing or proposing invalid blocks) can have a portion or all of their staked cryptocurrency confiscated by the protocol. This mechanism is known as 'slashing'.