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

[Sharding] Handle the case when committee count < active shards #2452

Merged

Conversation

Nashatyrev
Copy link
Member

  • Handle the case when a shard may not have a committee at slot in epoch transition
  • Treat the Block as invalid if it contains ShardBlobHeader lacking committee
  • Reject Gossip ShardBlobHeader and ShardBlob messages which lacks committee

Block is invalid if contains ShardBlobHeader lacking committee
Reject Gossip ShardBlobHeader and ShardBlob messages which lacks committee
Comment on lines 705 to 707
if index is None:
# the shard had no committee on this slot
continue
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another approach could be iterating through committees instead of shards.

@protolambda
Copy link
Contributor

I think we can drop the beacon-chain doc part of the changes, thanks to the improved state format (PR #2455, thanks for the original idea). But the p2p changes still make sense. Can you separate those out?

…-case

# Conflicts:
#	specs/sharding/p2p-interface.md
…he `compute_committee_index_from_shard` raises an error if no committee assigned to a shard
@Nashatyrev
Copy link
Member Author

Rebased this PR on top of #2455:

@protolambda protolambda merged commit 44f6453 into ethereum:dev Jun 4, 2021
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.

2 participants