Skip to content
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

Switch from cffi libsecp256k1 to ironclad secp256k1 #15

Open
kilianmh opened this issue Apr 28, 2024 · 1 comment
Open

Switch from cffi libsecp256k1 to ironclad secp256k1 #15

kilianmh opened this issue Apr 28, 2024 · 1 comment

Comments

@kilianmh
Copy link

Since this commit sharplispers/ironclad@4c689d0 Ironclad supports libsecp256k1. It would be more convenient to not depend on external libraries with cffi but use cl-native code. If you need some help I can try to assists (even though my cryptographic knowledge is also limited).

@rodentrabies
Copy link
Owner

rodentrabies commented May 28, 2024

Thanks for the suggestion. I'd still want the default to be the CFFI bindings to the C library for security purposes, but having the ironclad implementation as fallback is definitely convenient. I'll work on it at some point.

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

No branches or pull requests

2 participants