Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update 02_consensus.subpage.md #1633

Merged
merged 2 commits into from
Jun 29, 2023
Merged

Update 02_consensus.subpage.md #1633

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a32cc50
Update 02_consensus.subpage.md
bjoernek Jun 29, 2023
5947bbd
Merge branch 'master' into patch-12
sesi200 Jun 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion how-it-works/1_protocol/02_consensus.subpage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ low latency (almost instant finality);
high throughput;
robustness (graceful degradation of latency and throughput in the presence of node or network failures). The IC consensus protocol achieves these goals by leveraging [chain-key cryptography](/how-it-works/#Chain-key-cryptography).

The IC consensus protocol achieves these goals by leveraging [chain-key cryptography](/how-it-works/#Chain-key-cryptography).
The IC consensus protocol provides _cryptographically guaranteed finality_.
The option of choosing _probabilistic finality_ – similar to what is done in Bitcoin-like protocols, by considering a block final once a sufficient number of blocks have built on top of it in the blockchain – is not acceptable for the IC for two reasons: (1) probabilistic finality is a very weak notion of finality and (2) probabilistic finality would increase the time to finality drastically.

Expand Down