-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(spec): Consensus network requirements and gossip property #764
Conversation
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.
Thanks!
specs/consensus/overview.md
Outdated
> In other words, the `broadcast` primitive cannot be just implemented by | ||
> sending the same message (via "unicast") to every process. | ||
|
||
[comment]: <> (I wonder whether the next paragraph is more design related) |
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 don't think it is design-related. It is related to the fact that there is wiggle room in the assumptions in the arXiv paper that we explore. The point is that there are two relevant assumptions on the message system
- the one given in the paper (gossip)
- the one actually needed by the algorithm in the paper (the one that you describe below)
So the point is that instead of considering 1, we actually care about 2, because it is realistic.
Co-authored-by: Josef Widder <[email protected]> Signed-off-by: Daniel <[email protected]>
Part of #761.
Rendered section
PR author checklist
For all contributors
For external contributors