< ja>
nickler: i am thinking of trying to get debian to upgrade their secp256k1 version: https://sources.debian.org/src/libsecp256k1/ i was thinking of maybe mentioning some security improvements to speed up the process. according to the benchmarks by gmaxwell it looks like it is now much faster on ARM, is that right? are there other improvements i could be mentioning in my request?
< ja>
also, which ABI changes have there been? secp256k1 is built without ECDH on debian. i assume there have been backwards-incompatible ABI changes since 2017 outside experimental modules?
< ja>
if that is right, only experimental would be able to upgrade, but that would be something, since it is on a version from 2019-03-31
< ja>
ah you can reply in #secp256k1 if you like
< luke-jr>
ja: only in 2018 IIRC
< luke-jr>
at the latest, it didn't change after 2018-10-18 iirc
< luke-jr>
newest libsecp256k1 made ECDH non-experimental too
< luke-jr>
(as of like 10 days ago)
< sipa>
ja: probably better to wait until we have an actual release
< ja>
sipa: ok, i'll be watching the 1.0 milestone, thanks
< ja>
luke-jr: ok, since it changed in 2018, that still means that buster,bullseye,sid,stretch cannot upgrade to the latest commit since it wouldn't be ABI compatible. so they will just be left on their versions from 2016 and 2017
< ja>
i guess there weren't any really bad problems anyway, so it isn't so bad?
< luke-jr>
ja: well, if they didn't build ECDH, then it doesn't affect them…
< luke-jr>
ja: non-ECDH may have changed since then too - I didn't look at those
< ja>
ah, i thought you talked about a different change
< bitcoin-git>
[bitcoin] jonatack opened pull request #20279: doc: fix getchaintxstats fields in release-process.md (master...release-process-getchaintxstats-fix) https://github.com/bitcoin/bitcoin/pull/20279