-
Notifications
You must be signed in to change notification settings - Fork 997
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
Updated phase 1: shard block structure #578
Conversation
specs/core/1_shard-data-chains.md
Outdated
for i in range(chunks-1, 0, -1): | ||
o[i] = hash(o[i*2] + o[i*2+1]) | ||
return o[1] | ||
def get_proposal_committee(seed: Bytes32, |
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.
What will it be? persistent or proposal committee?
I think persistent is mildly better.
right now this doc uses both
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.
Let's do persistent.
(edited all the appearances to make it that way)
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
`hash32` -> `bytes32` ['uint384'] -> `bytes96`
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
Co-Authored-By: vbuterin <[email protected]>
Note: merge pending resolving handling exited validators within persistent committees. To ensure the 9 day lookahead on the set, we are leaning towards leaving them within, but having a method of fallback proposers when exited:
|
Added a fix as three suggested changes to the code: https://github.com/ethereum/eth2.0-specs/pull/578/files |
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.
Cleaned up a couple things in the suggested code you wrote.
Added a couple of suggestions that fix minor bugs and formatting.
good to merge after you accept all suggestions.
No description provided.