-
Notifications
You must be signed in to change notification settings - Fork 264
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
Make the library safer to dynamically link? #657
Comments
It shouldn't be too technically difficult. Upstream is really good about bumping the major soname and renaming the lib whenever they make breaking changes. But I don't know how to do it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IIUC upstream libsecp256k1 packaged in distribution can be dynamically linked to safely and this is used by some projects (Electrum IIRC). Could we make sure this is a possibility with our crate as well? How hard would it be? I guess it can slightly decrease performance in some edge case scenarios but maybe it's worth it? Not having to update an application every time secp256k1 upgrades would be nice. Also could cut down compile times significantly.
The text was updated successfully, but these errors were encountered: