-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[consensus] support committee with 1 node #20530
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
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.
nice!
You rock @mwtian, thanks a lot! |
As I am a bit of a noob in this area, does this change restrict the committee size to only 1? |
No problem! This change just makes sure 1-validator committee works in the scenarios covered by the tests (with epoch change). Using any other number (2,3,4,...) of validators in a committee is still supported. |
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.
Nice one @mwtian 👍 !
break 'main; | ||
} | ||
|
||
let mut total_stake = 0; |
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.
Nice fix as well moving the total_stake
here.
Thanks a lot @mwtian!!! 🚀 |
Description
Obviously there is no fault tolerance. But this should be useful for running local cluster cheaply.
min_round_delay
should be set to a higher value for local cluster so not too many consensus blocks are built.Test plan
Add unit and simtest.
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.