WIP: Leader election #31
Open
Conversation
This file contains 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
added 2 commits
May 31, 2017 04:47
YuryYa
suggested changes
Jun 1, 2017
| # Leader Election | ||
| # Leader Election algorithm | ||
|
|
||
| This page describes the problem and solution for the problem of leader |
There was a problem hiding this comment.
problem ... problem
It seems that the intro from the blog was better
| `1 block out of F+1 blocks` is guaranteed to be mined by honest miners | ||
| (instead of `sufficient fraction of K blocks`).* | ||
|
|
||
| ## Round Robin overview |
There was a problem hiding this comment.
Round Robin -> Leader Election everythere
| Round Robin algorithm defines how the order of validating nodes for the | ||
| height `H` should be calculated. Such order determines node's `block | ||
| proposal` priority. That is, block proposal from node #2 would be | ||
| accepted only if `block proposal` from node #1 was absent. ## Algorithm |
| selection. To remove any centrality point, Exonum needs make block | ||
| generation distibuted. The proposed algorithm is revealed here. | ||
|
|
||
| ## Solvable problem |
There was a problem hiding this comment.
Solvable problem or problems?
This section is also better written in blog
| Due to this property, byzantine nodes would not follow one after the | ||
| other in a series but would be randomly interspersed with fair nodes. | ||
|
|
||
| ## Round Robin details |
There was a problem hiding this comment.
This section is also better written in blog
There was a problem hiding this comment.
Is it really the implemented algorithm from Exonum?
| accepted only if `block proposal` from node #1 was absent. ## Algorithm | ||
| properties | ||
|
|
||
| The properties that are provided by the current algorithm: |
There was a problem hiding this comment.
It is rather surprising to see properties before the algorithm description
slowli
suggested changes
Jun 12, 2017
There was a problem hiding this comment.
Review as of adc3e00. The text should be restructured as follows:
- Short intro
- Description of what is actually accomplished in Exonum Core and how it can be configured/extended
- Motivation: why is the leader election algorithm needed and what security properties it yields
- Maybe, unsolved problems iff we will solve them
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Here is restored old file about leader selection. It needs review and comments to be changed accordingly to other documentation style