Bitcoin Core developers have merged a privacy fix into the software's 32.x code branch, CryptoSlate reported. The fix concerns private broadcast, an optional feature that is switched off by default.
When a user turns private broadcast on, transactions submitted with the sendrawtransaction command are sent through short-lived, dedicated connections to peers on privacy networks such as Tor or I2P. The flaw was in how the software handles peers that misbehave, meaning other nodes it is connected to. According to reviewers, this handling could leave outside observers a clue linking the private connections to the node's ordinary activity.
The patch keeps the two kinds of connections apart. Private peers that misbehave are still disconnected, but they are no longer processed through the normal discouragement rules. Penalizing an ordinary peer also no longer cuts private connections that share the same address.
Users of the current stable release, 31.1, still have to wait. A separate request to bring the fix to the 31.x branch remains open and is tagged for version 31.2, but that does not set a release date. Version 32.0 is still at the test-candidate stage. Developers have also labeled private broadcast experimental and now describe its privacy benefit as reducing risk rather than removing it.
Why it matters for beginners
Most people never change these settings, and the issue only affects nodes that switched private broadcast on. It is still a useful look at how open-source software gets fixed in public, step by step. If you run a node and rely on this feature, remember that it is experimental, and install updates only from official release channels once a fixed version is published.
Source
Finvane summary of reporting by CryptoSlate. Facts and figures come from the original report; the wording is ours.
Read the original report: Bitcoin Core’s privacy fix reaches v32 code while the v31 patch remains open ↗For education only, not financial advice. Crypto assets are volatile and you can lose money.