Skip to content

Commit

Permalink
Minor edits
Browse files Browse the repository at this point in the history
  • Loading branch information
ipopescu committed Apr 3, 2024
1 parent 106e859 commit 4b35c92
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions source/docs/casper/concepts/design/consensus.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ To summarize, the consensus mechanism will determine how a blockchain meets the

## Casper Consensus Protocols

Each Casper network can choose and configure its consensus protocol using the network's chainspec. The protocols available are [Zug](./zug.md) and [Highway](./highway.md). Since the launch of the Casper Mainnet, the [Highway](https://arxiv.org/pdf/2101.02159.pdf) protocol was in use until Casper Node 2.0 (Condor) was released. The Zug consensus protocol was introduced in version 2.0 to simplify and speed up the consensus process without compromising safety. Zug enables faster block times, less overhead, and a larger validator set in Mainnet. Zug is an implementation of the ideas from the paper [From Weakly-terminating Binary Agreement and Reliable Broadcast to Atomic Broadcast](https://arxiv.org/abs/2205.06314), which describes how Zug meets the safety, liveness, and resiliency requirements.
Each Casper network can choose and configure its consensus protocol using the network's chainspec. The protocols available are [Zug](./zug.md) and [Highway](./highway.md). Since the launch of the Casper Mainnet, the [Highway](https://arxiv.org/pdf/2101.02159.pdf) protocol was used until Casper Node 2.0 (Condor) was released. The Zug consensus protocol was introduced in version 2.0 to simplify and speed up the consensus process without compromising safety. Zug enables faster block times, less overhead, and a larger validator set in Mainnet. Zug is an implementation of the ideas from the paper [From Weakly-terminating Binary Agreement and Reliable Broadcast to Atomic Broadcast](https://arxiv.org/abs/2205.06314), which describes how Zug meets the safety, liveness, and resiliency requirements.

## Consensus in the Casper Mainnet

Expand Down Expand Up @@ -63,7 +63,7 @@ The final block of an era is a *switch block* and forms the initial state of the

### Finality

Finality occurs when the network can be sure that a block will not be altered, reversed, or canceled after addition to the chain. This occurs via consensus, and as all transactions happen within a block, it allows for confirmation that a transaction cannot be changed. After finality, it would require greater than 1/3 of all validators to double-sign to cause a disparity between nodes. In this event, the network would shut down and require a manual restart.
Finality occurs when the network can be sure that a block will not be altered, reversed, or canceled after addition to the chain. This occurs via consensus, and as all transactions happen within a block, it allows for confirmation that a transaction cannot be changed. After finality, it would require greater than one third of all validators to double-sign to cause a disparity between nodes. In this event, the network would shut down and require a manual restart.

On a Casper network, a transaction finalizes alongside the finalizing of the block in which it is included. Validators that equivocate risk eviction, in which the network removes them from the validator set. Therefore, honest nodes receive rewards for their participation, while equivocating nodes risk loss of revenue for acting maliciously.

Expand Down
2 changes: 1 addition & 1 deletion source/docs/casper/concepts/design/zug.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Notice that proposals, votes, and echoes are gossiped, so if one correct node re
### Example 2 (BK)
- if half the nodes vote (either true or false?), the round is not skippable
- if 1/3 of the nodes vote true, then we have at least one honest node that voted true, meaning there is a proposal that has a quorum of echoes. Therefore,, eventually all other honest nodes will see a quorum of echoes and accepted proposal, which will be used as a parent in future rounds.
- if one third of the nodes vote true, then we have at least one honest node that voted true, meaning there is a proposal that has a quorum of echoes. Therefore,, eventually all other honest nodes will see a quorum of echoes and accepted proposal, which will be used as a parent in future rounds.
- if a round is not finalized nor skippable, the block will become finalized at some point most likely, but not yet.
-->

Expand Down

0 comments on commit 4b35c92

Please sign in to comment.