Skip to content

Conversation

obycode
Copy link
Contributor

@obycode obycode commented Oct 9, 2025

Implementing #6554.

@jcnelson
Copy link
Member

Why are we dropping libsecp256k1 in favor of the one from RustCrypto? The former has been extensively audited and is used by Bitcoin.

Add tests for `secp256k1-verify` and `secp256k1-recover?` while adding
tests for this new function.
@obycode obycode marked this pull request as ready for review October 10, 2025 21:41
@obycode obycode requested review from a team as code owners October 10, 2025 21:41
@obycode
Copy link
Contributor Author

obycode commented Oct 10, 2025

Why are we dropping libsecp256k1 in favor of the one from RustCrypto? The former has been extensively audited and is used by Bitcoin.

The thought was that since we're pulling in the RustCrypto crate for secp256r1, we may as well also replace the k256 crate as well with this Rust-native solution that seems to be well-vetted and audited as well. libsecp256k1 is a wrapped C library.

@obycode obycode linked an issue Oct 10, 2025 that may be closed by this pull request
@obycode obycode requested review from jcnelson and kantai October 10, 2025 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Clarity-4] secp256r1

2 participants