Skip to content
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

Merged
merged 23 commits into from
Feb 11, 2019
Merged

Updated phase 1: shard block structure #578

merged 23 commits into from
Feb 11, 2019

Conversation

vbuterin
Copy link
Contributor

@vbuterin vbuterin commented Feb 7, 2019

No description provided.

@hwwhww hwwhww added the phase1 label Feb 7, 2019
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,
Copy link
Contributor

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

Copy link
Contributor Author

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)

specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
@djrtwo
Copy link
Contributor

djrtwo commented Feb 9, 2019

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:

  1. get_shard_block_proposer() could have a fallback by incrementing by 1 if selected is not active (keep incrementing until find active).
  2. keep non-active validators from committee in the bitfield but enforce 0 bit.

@vbuterin
Copy link
Contributor Author

Added a fix as three suggested changes to the code: https://github.com/ethereum/eth2.0-specs/pull/578/files

Copy link
Contributor

@djrtwo djrtwo left a 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.

specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
specs/core/1_shard-data-chains.md Outdated Show resolved Hide resolved
@djrtwo djrtwo merged commit 5b198e0 into dev Feb 11, 2019
@djrtwo djrtwo deleted the vbuterin-patch-6 branch February 11, 2019 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants