-
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
Permissioning for block creation #15
Comments
OK, but we need to clarify “All honest nodes must agree on the validator set for all blockchain heights.”, what does this mean in practical terms? Does this mean that no block is finalised until it has enough validator seals, or does it mean from the voting point of view that all validators remain consistent of their view of correct validator set, please clarify. |
What I mean by this assumption is that if node |
The issue's title is misleading. This should be something like "Dynamic quorum" requirement. |
Could we take THIS as the requirement: |
agree with @kubasiemion, "Validator set consistency" seems more logical, but I would argue that this property is not a core requirement for achieving consensus, however, it can be considered a general integrity property for the blockchain "validator management sub-protocol". |
Resolved in meeting 2020-05-27 to keep this open, and label to be tested in impementation |
Validator set is defined here as the list of nodes that can propose a new block and participate in the consensus protocol.
Nodes that are not included in the validator set are not allowed to propose new blocks and participate in the consensus protocol.
All honest nodes must agree on the validator set for all blockchain heights.
The *BFT Consensus Protocol must allow for a mechanism for adding or removing validators to/from the set of authorised validators.
The text was updated successfully, but these errors were encountered: