-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
libsecp256k1 library found but it was built without required module (--enable-module-recovery) #6465
Comments
Why did you close this without saying the fix? |
Ok, so apparently this happens on debian 10, but not on e.g. ubuntu 20.04. Workarounds for users, in order of increasing complexity:
|
For anyone else having this issue, when compiling with |
@nickfarrow You can just add the path to
Run @SomberNight What do you think about phasing out the module-recovery code in the long run? |
Why? libsecp256k1 is a good library. The "recovery" module is optional in it, unfortunately, yes; but is that the sole reason you would want not to require it? Then we would need an alternative or at least a fallback implementation. In the past we used python-ecdsa for this. I would like to minimise crypto code we need to maintain. And libsecp256k1 is probably much more tested and more widely used. Also, for taproot support we will need another optional module from libsecp256k1 ("schnorrsig"), and there is no alternative for that. I think people running from source will just have to make sure to get libsecp with the needed extra modules included. |
The text was updated successfully, but these errors were encountered: