Private Broadcast May Reveal Sender IP Address in Bitcoin Core 31.0

What happened

Users of -privatebroadcast are advised to apply one of the workarounds below until 31.1 is released. Affected users This bug affects users where all the following are true: The node is running Bitcoin Core 31.0 and -privatebroadcast is set.

Wallet RPCs ( sendtoaddress , sendall , etc.) do not use private broadcast and are not affected. BIP324 v2 transport is not disabled with -v2transport=0 .

Impact When private broadcast selects an IPv4 or IPv6 peer that advertises support for v2 (BIP324) transport, the initial connection is routed through the Tor proxy as expected. The v1 retry is not routed through the Tor proxy and instead connects directly to the peer over IPv4 or IPv6, exposing the originator’s IP address to the recipient.