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

Update requirements.md #58

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update requirements.md #58

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9635268
Update requirements.md
drequinox Oct 16, 2019
d5e9934
Update requirements.md
drequinox Nov 18, 2019
0ea9dd2
Update requirements.md
drequinox Nov 18, 2019
7fad19f
Update requirements.md
drequinox Nov 29, 2019
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
5 changes: 5 additions & 0 deletions docs/requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,8 @@ The goal of this work is to agree on an interoperable consensus protocol that me
* MUST guarantee timely finality;
* MUST guarantee all of the requirements listed here when operating in eventually synchronous network
* SHOULD have a specification sufficient to enable implemetation without having to refer to someone else's code;
* The consensus algorithm MUST support the following safety and liveness properties
- Agreement — Any two honest processes MUST decide the same block (no two honest processes decide different blocks).
- Validity — If an honest process decides on a block, then that block must have been proposed by some process. Secondly the proposal itself must be a valid block.
- Integrity — An honest process MUST only decide for a block at most once (in a round)
- Termination — Any honest process MUST eventualy decide (ensuring progress)