CryptoSlate
Bitcoin Core has merged a privacy fix into its 32.x development branch addressing behavior that could let an observer link a node's private-broadcast connections to its ordinary peer activity. The patch separates how the software handles discouragement of misbehaving peers across private-broadcast connections versus standard connections, a change that reached the main branch on September 25 and was backported to 32.x on October 1. The corresponding patch for the 31.x release line remains open as of October 8, leaving users on the current stable release 31.1 awaiting the fix until a 31.2 ships.
Why it matters
Private broadcast is an opt-in feature used through sendrawtransaction, which routes transactions through dedicated, short-lived connections to Tor or I2P peers. The privacy concern is that when a node discourages one of those private peers, the same handling could also disconnect ordinary connections sharing that peer's address, or visibly alter the node's behavior in a way an outside observer could correlate. Bitcoin Core's earlier 31.1 release notes flagged a separate IP-address leak in which private-broadcast traffic was sometimes routed over clearnet instead of the privacy network. The newer patch closes a different gap, observable effects of peer handling rather than the routing path itself.
The patch keeps misbehaving private peers disconnected while excluding them from regular discouragement logic, and conversely prevents discouraging an ordinary peer from taking down private-broadcast connections that share its address. Developers also marked the feature experimental and narrowed its privacy claims to risk reduction rather than full anonymity, an honest framing that matters for users weighing whether to enable it.
Market impact
The Bitcoin Core reference implementation governs how a large share of full nodes on the network behave, and protocol-level privacy changes tend to ripple through wallet software and downstream forks. With private broadcast still disabled by default and explicitly experimental, the immediate market effect is contained.
Frequently asked questions
-
What does the Bitcoin Core privacy fix actually change?
The fix separates discouragement logic so that punishing a private-broadcast peer no longer affects ordinary connections sharing its address, and vice versa, closing a side channel that could link the two kinds of activity.
-
Why is the v31 backport still open if v32 already has the fix?
The 31.x backport received reviewer approval on October 6 and carries a 31.2 milestone, but no release date has been set. The 32.x branch already contains the merged change from October 1.
-
Is private broadcast enabled by default in Bitcoin Core?
No. Private broadcast is opt-in and disabled by default. Developers have also marked it experimental and narrowed its privacy claims to risk reduction rather than full anonymity.
-
How is this different from the earlier IP-address leak fix in 31.1?
The 31.1 release notes documented a routing bug where private-broadcast traffic sometimes went over clearnet instead of the configured privacy network. The newer patch addresses observable effects of peer-handling logic, not the routing path itself.
-
What should users on Bitcoin Core 31.1 do in the meantime?
Users on the 31.1 stable release wait for the 31.2 backport to ship. Those running 32.x test candidates, currently rc3, can already pick up the fix through the development branch.
Glassnode
WatcherGuru
WuBlockchain
TheBlock
CoinDesk