Collabration on libsecp256k1
About me
Maintain the libsecp256k1, Electron Cash and Electrum packages for Fedora Linux.
Goal
Make it easier to include and maintain a common libsecp256k on Fedora and software for Fedora that rely on that library as a shared library.
Bitcoin-ABC
Own fork maintained along the main software.
Source: https://github.com/Bitcoin-ABC/bitcoin-abc/tree/master/src/secp256k1
Bitcoin Unlimited
Own fork maintained along the main software.
https://github.com/BitcoinUnlimited/BitcoinUnlimited/tree/release/src/secp256k1
Electron Cash
Sub-module of a fork from Bitcoin-ABC
https://github.com/Electron-Cash/secp256k1
Bitcoin Verde
An old fork from Bitcoin-core
https://github.com/SoftwareVerde/bitcoin-verde/tree/development/jni/secp256k1
bchd
Only native in Go/built-in
bip-schnorr
Used by bitbox
Only native in Javascript
Hi @jonny, I see the problem and how this setup just begs to get quirky over time, but to get anywhere you might have to propose some kind of solution and then ask the relevant parties about it.
Looking in my package manager from the gentoo distribution, I see that the same issue exist here - each node software package their own. There is a standalone package for
dev-libs/libsecp256k1
listed at v0.0.0_date with the website https://github.com/bitcoin/secp256k1, but I have BU installed but not that package, and ldd does not list any libsecp256k1 links.Given the very high value involved there's a risk that software developers will want to keep things in-house to prevent unwanted changes to it, but I do hope that there'll be some discussion around this at least.