Added requirements for guaranteeing persistence for consensus protocol with immediate finality #52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
with immediate finality
saltiniroberto
changed the title
drequinox
reviewed
Sep 11, 2019
| * MUST withstand a sigificant fraction of malfunctioning / malicious actors (around 1/3 of nodes); | ||
| * MUST have a formal proof of correctness that we can show to regulators; | ||
| * MUST guarantee timely finality; | ||
| * MUST guarantee the robustness property for consensus protocols with immediate finality |
There was a problem hiding this comment.
It is not clear that what the robustness property is, please see discussion in the issue #14
saltiniroberto
added
the
blocked
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
with immediate finality