There is an updated pull request by ar-jan against master on the void-packages repository https://github.com/ar-jan/void-packages electrum-409 https://github.com/void-linux/void-packages/pull/28305 [WIP] Update Electrum to 4.0.9 #### General - [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements) #### Have the results of the proposed changes been tested? - [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me - [ ] I generally don't use the affected packages but briefly tested this PR This depends on #28272. Using package [libbitcoin-secp256k1](https://github.com/void-linux/void-packages/tree/master/srcpkgs/libbitcoin-secp256k1) as dependency might be possible, but: it is based on this release: https://github.com/libbitcoin/secp256k1/releases/tag/v0.1.0.13 with the last commit included dating to December 2016. Electrum currently [uses](https://github.com/spesmilo/electrum/blob/master/contrib/make_libsecp256k1.sh) a commit from from June 2020 from https://github.com/bitcoin-core/secp256k1. Remaining issues: - Using `libbitcoin-secp256k1` it builds and runs OK (tested opening and creating wallets), but I don't know if the outdated libsecp256k1 could be problematic with other functionality. So instead I've tried using the `make_libsecp256k1.sh` from Electrum. This works locally on my x86_64, but I'm not sure how to do this correctly for all architectures/compilers. - Also, the library must be available at `/usr/lib/libsecp256k1.so.0`, how should that work if someone also has `libbitcoin-secp256k1` installed which uses the same library path? - Difference between libbitcoin/secp256k1 and its upstream bitcoin-core/secp256k1? Possible to provide the bitcoin-core/secp256k1 version instead in Void? A patch file from https://github.com/void-linux/void-packages/pull/28305.patch is attached