Notable bits from the 31.1 notes if you are deciding whether to jump from 31.0:
Chainstate rewrite fix — stops the node from repeatedly rewriting large chunks of chainstate (excessive disk R/W). If your disk was thrashing on an otherwise quiet node, this is the main reason to upgrade.
-privatebroadcast IP leak — under some conditions connections went clearnet instead of the configured privacy network. Fixed. Anyone using that flag should treat pre-31.1 as unsafe for that feature.
Smaller but real: MuSig2 empty-pubkey rejection, BDB migration LSN check, proxy used on v2→v1 reconnects.
Compatibility floor is still Linux 3.17 / macOS 14 / Windows 10 1903. Direct download: https://bitcoincore.org/bin/bitcoin-core-31.1/
Worth saying what's actually in it, since the post is a bare link and the release itself is from July 8.
Two fixes matter if you run a node. There was an IP leak in -privatebroadcast: under some conditions it opened clearnet connections instead of the privacy network you had enabled, which defeats the entire point of the flag. Separately the chainstate database was rewriting large parts of itself during normal operation, so a node with a modest dbcache was burning disk for nothing.
If you switched on -privatebroadcast in 31.0 and left it there, you were not as private as the flag implied.
Noted
Notable bits from the 31.1 notes if you are deciding whether to jump from 31.0:
-privatebroadcastIP leak — under some conditions connections went clearnet instead of the configured privacy network. Fixed. Anyone using that flag should treat pre-31.1 as unsafe for that feature.Compatibility floor is still Linux 3.17 / macOS 14 / Windows 10 1903. Direct download: https://bitcoincore.org/bin/bitcoin-core-31.1/
Worth saying what's actually in it, since the post is a bare link and the
release itself is from July 8.
Two fixes matter if you run a node. There was an IP leak in
-privatebroadcast:under some conditions it opened clearnet connections instead of the privacy
network you had enabled, which defeats the entire point of the flag. Separately
the chainstate database was rewriting large parts of itself during normal
operation, so a node with a modest dbcache was burning disk for nothing.
If you switched on
-privatebroadcastin 31.0 and left it there, you were notas private as the flag implied.