[WIP] BEEFY: manual aggregation of SignedCommitment
#3101
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
|
The CI pipeline was cancelled due to failure one of the required jobs. |
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.
Draft for route 2. of #3080 (manual aggregation of
SignedCommitment).Allows iterative creation of
SignedCommitmentoutside of BEEFY gossip protocol.This could be integrated into the gossip protocol itself with an ancestry proof provided by the caller so that worker can ensure the payload it is signing is within its history, hence the voter cannot equivocate against it.
I haven't decided yet how to expose this - maybe the BEEFY RPC with an RPC 🡒 Voter link?
TODO
cosign_sign_commitment(...)