Strengthening Bitcoin Privacy: The New Connection-Linking Fix
Bitcoin Core developers are reinforcing the network's privacy architecture by addressing a vulnerability that could potentially expose the identity of users broadcasting private transactions. The latest update, recently merged into the version 32 source code, aims to prevent external observers from correlating dedicated private connections with a node’s standard network activity, further hardening the software against de-anonymization risks.
Securing the Private Broadcast Path
The vulnerability centers on the privatebroadcast option, an opt-in feature used to submit raw transactions through dedicated, short-lived connections via Tor or I2P. Previously, Bitcoin Core’s "discouragement" mechanism—a system that disconnects misbehaving nodes—could inadvertently signal a link between a user's private and ordinary network connections. If a peer address was discouraged on a private channel, the software might also disconnect standard connections to that same address. These shared effects provided a visible clue to outside observers, allowing them to link private transaction activity to a specific node's public IP or identity.
Implementation and Version Status
The new patch successfully isolates these behaviors by separating how the software handles peer discouragement across different connection types. Under the new logic:
- Private-broadcast peers are excluded from normal discouragement handling.
- Misbehaving private peers are disconnected without affecting ordinary connections.
- Discouraging a standard peer no longer triggers the disconnection of a private-broadcast connection sharing the same address. While this fix is already integrated into the 32.x development branch, it has not yet reached the stable 31.1 release. A separate proposal to backport the fix to the 31.x branch is currently open under the 31.2 milestone. Developers continue to categorize the private broadcast feature as experimental, emphasizing that while these updates significantly reduce correlation risks, they are part of an ongoing effort to refine the protocol's privacy guarantees.
