-
Notifications
You must be signed in to change notification settings - Fork 44
Optional signed message in registered signatures #1909
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
Optional signed message in registered signatures #1909
Conversation
Else we would need to change signatures of multiple methods in the signer in order to pass it to the `RegisterSignnatureMessage`. It will also be usefull in aggregator to handle signature buffer on the service side (since most services use entities instead of messages).
Test Results 4 files ±0 53 suites ±0 9m 18s ⏱️ -7s Results for commit 064aa0a. ± Comparison against base commit cbd65d0. This pull request removes 1 and adds 3 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
LGTM
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.
LGTM
* Mithril-aggregator from `0.5.57` to `0.5.58` * Mithril-signer from `0.2.175` to `0.2.176` * Mithril-common from `0.4.47` to `0.4.48` * Mithril-end-to-end from `0.4.29` to `0.4.30`
eb7d638
to
064aa0a
Compare
Content
This PR add an optional field to single signatures:
signed_message
.In order to decentralize signatures orchestration we will need to buffer incoming single signatures when the Aggregator has yet to create an open message for the signed entity type.
But in that case we won't be able to some validation to reject immediately malicious signatures from bad actors.
This new field will allow us to do an integrity check of incoming signatures, by checking their validity against their signed message and the current stake distribution, .
Pre-submit checklist
Issue(s)
Closes #1899