You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: