-
Notifications
You must be signed in to change notification settings - Fork 679
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
Nakamoto: Validate stacker signature of a Nakamoto Block #4039
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## next #4039 +/- ##
==========================================
- Coverage 0.04% 0.04% -0.01%
==========================================
Files 419 419
Lines 297652 297992 +340
==========================================
Hits 136 136
- Misses 297516 297856 +340 ☔ View full report in Codecov by Sentry. |
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! I just had one minor suggestion.
May the Schwartz be with you.
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 -- only had a minor comment
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.
I don't think we should be using MessageSignature
to encapsulate a Schnorr signature. I was using that as a placeholder for a Schnorr-specific signature type.
If you can instead create a Schnorr signature container, and use that in place of MessageSignature
in the block header, then I'll approve 👍
88d0745
to
7574a6c
Compare
Done. Just working on adding "aggregate_public_key" to the RewardCycleInfo |
de9b632
to
87a6c9c
Compare
Sounds good to me 👍 |
2717979
to
7c3aea9
Compare
510367a
to
220099a
Compare
3500cb3
to
d3e0aa8
Compare
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…nd verify it against the provided signature Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…d sets Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…ard cycle to determine the aggregate public key Signed-off-by: Jacinta Ferrant <[email protected]>
…n pre nakamoto blocks Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…r all reward cycles Signed-off-by: Jacinta Ferrant <[email protected]>
…are phase Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
ff3a01c
to
dbea8db
Compare
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 -- I think we should just flag a relevant issue for the block that the agg key is fetched from, I don't think it needs to block this PR.
Signed-off-by: Jacinta Ferrant <[email protected]>
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Add functionality to check if a Nakamoto block has been correctly signed with the Signers (Stackers) WSTS signature associated with the aggregate public key.
Applicable issues