-
Notifications
You must be signed in to change notification settings - Fork 0
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
Schnorr stuff is based on old secp256k1 #1
Comments
Thank you very much @ysangkok |
@ysangkok I hope you can help me out a bit. when running "stack test" I receive this output:
However "stack build" works just fine. the "tests" part of my package.yaml file is this:
As you can see, I added extra-lib-dirs (I compiled secp256k1 from source), however the linker doesn't seem to find it. Any suggestions on how to solve this? Thanks in advance. |
when compiling from source, you need to add the extra flags |
Ensure that you don't have an old version of libsecp256k1 laying around. I don't wanna investigate more, since I don't work in cryptocurrency any more and I think it is already a disproportionate part of the Haskell ecosystem. |
This is not for some cryptocurrency shitcoin. Anyway, thanks for your hints @ysangkok. |
As you can see from the PR, the schnorr bindings were made against the BIP340 spec as it was around March 2020. The spec and implementation were since changed, some symbols probably have different names, that's why you got linking errors. To make it work, you should diff the commit mentioned in the PR with the upstream secp256k1 that you want this library to target. Then you can know how to adjust the bindings.
The text was updated successfully, but these errors were encountered: