-
Notifications
You must be signed in to change notification settings - Fork 90
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
dkg: lock hash k1 signature in lock file #2224
Conversation
This commit ensures all node operators individually sign the agreed lock hash with their K1 private keys, and stores the resulting signature in the lock file itself.
@@ -172,6 +177,29 @@ func (l Lock) VerifySignatures() error { | |||
return errors.Wrap(err, "verify lock signature aggregate") | |||
} | |||
|
|||
if len(l.NodeSignatures) != 0 { |
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.
please move this to Lock.VerifySignatures
remove implicit verification from marshalling, only do explicit verification via VerifySignatures
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.
not sure I got what you mean, this check is already in Lock.VerifySignature
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2224 +/- ##
==========================================
- Coverage 53.79% 53.77% -0.02%
==========================================
Files 187 188 +1
Lines 25059 25191 +132
==========================================
+ Hits 13480 13547 +67
- Misses 9917 9975 +58
- Partials 1662 1669 +7
☔ View full report in Codecov by Sentry. |
…ly, without middleware handlers Instead of initializing a bcast.BroadcastFunc with bcast.New, return a bcast.Component on which callers can register handlers after initialization.
This commit ensures all node operators individually sign the agreed lock hash with their K1 private keys, and stores the resulting signature in the lock file itself.
category: feature
ticket: #2204