-
Notifications
You must be signed in to change notification settings - Fork 224
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
tendermint: use k256::ecdsa::VerifyingKey as Secp256k1 key #900
tendermint: use k256::ecdsa::VerifyingKey as Secp256k1 key #900
Conversation
Hmm, these build failures seem unrelated?
|
a3a2bed
to
26d4a17
Compare
Codecov Report
@@ Coverage Diff @@
## master #900 +/- ##
======================================
Coverage 69.7% 69.8%
======================================
Files 200 200
Lines 16326 16326
======================================
+ Hits 11391 11398 +7
+ Misses 4935 4928 -7
Continue to review full report at Codecov.
|
Opened #901 to deal with the |
See #873 for background. This changes the type re-exported as `tendermint::public_key::Secp256k1` from a `k256::EncodedPoint` to a `k256::ecdsa::VerifyingKey`. The main distinction this provides is validating the public key (i.e. making sure it provides a valid solution to the secp256k1 curve equation), whereas `EncodedPoint` provides no validation of the public key. If there were ever a `Signature::Secp256k1` variant added, this would also make it easy to perform signature verification.
26d4a17
to
501204c
Compare
@tarcieri is it worth perhaps adding a |
@thanethomson added in 768019d |
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.
Thanks @tony-iqlusion! 🙏
See #873 for background.
This changes the type re-exported as
tendermint::public_key::Secp256k1
from ak256::EncodedPoint
to ak256::ecdsa::VerifyingKey
.The main distinction this provides is validating the public key (i.e. making sure it provides a valid solution to the secp256k1 curve equation), whereas
EncodedPoint
provides no validation of the public key.If there were ever a
Signature::Secp256k1
variant added, this would also make it easy to perform signature verification.