feat: committee selection beacon slashing #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
snormore
force-pushed
the
s/committee-beacon-slashing
branch
3 times, most recently
from
44897c9
to
cc94b0a
Compare
snormore
force-pushed
the
s/committee-beacon-slashing
branch
from
6c6dc59
to
94cb380
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Slash nodes that commit without revealing in the committee selection random beacon process.
NodeRegistryChange::Slashedis used to propagate the slashing event on the block execution response.Metadata::EpochErais introduced to reset the narwhal store/dag so that it can be reconfigured mid-epoch when a committee member is slashed and no longer has sufficient stake.