-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Specified the robustness property to refer to consensus protocols with immediate finality #49
Conversation
immediate finality
terminology.md
Outdated
@@ -13,7 +13,10 @@ In order alphabetically by `Label` then by `Term`, or just `Term` if there is no | |||
|
|||
|Label | Term | Definition | | |||
|------| ---------------------------------- | --------------- | | |||
| CP | Liveness | Every correct propsed value will eventually be accepted by correct nodes. aka something good happens. | | |||
| CP | Chain Agreement with Immediate Finality | At any point in time, for any two nodes `n1` and `n2`, either the blockchain of `n1` is a prefix of the blockchain of `n2` or the blockhain of `n2` is a prefix for the blockchain of `n1` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO this seems like more of a Ledger property in general not necessarily specific to consensus. Even if we consider this a consensus property, this "common prefix" attribute is, in fact, better defined as consistency instead of "chain agreement with immediate finality". The definition seems not complete either, should we not also consider the case when "at any point in time . . " both blockchains are identical?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the safety property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am happy to change the name if required
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If two blockchains are identical then they are the prefix of each other. I will add this bit in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have pushed a new commit that clarifies this.
| CP | Liveness | Every correct propsed value will eventually be accepted by correct nodes. aka something good happens. | | ||
| CP | Chain Agreement with Immediate Finality | At any point in time, for any two nodes `n1` and `n2`, either the blockchain of `n1` is a prefix of the blockchain of `n2` or the blockhain of `n2` is a prefix for the blockchain of `n1` | | ||
| CP | Honest Chain Growth | For any point in time `t` and any node `n`, there exists a fine value `τ` such that the length of the blockchain of node `n` at time `t+τ` includes block proposed by honest nodes that were not included in the blockchain for node `n` at time `t`. | | ||
| CP | Robust Consensus Protocol with Immediate Finality | A consensus protocol with immediate finality is robust if and only if it guarantees all of the following properties: <ul><li>Chain Agreement with Immediate Finality<li>Honest Chain Growth</ul> | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should revisit the robustness definition here #14 before including it in any other document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thi sis the liveness property
immediate finality