Skip to content

Added requirements for guaranteeing persistence for consensus protocol with immediate finality #52

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

Open
saltiniroberto wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added requirements for guaranteeing persistence for consensus protocol with immediate finality #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,5 @@ The goal of this work is to agree on an interoperable consensus protocol that me

* 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
Copy link

@drequinox drequinox Sep 11, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not clear that what the robustness property is, please see discussion in the issue #14

* SHOULD have a specification sufficient to enable implemetation without having to refer to someone else's code;