Privacy bug for Bitcoin Core 31.0 dey expose sender IP under certain conditions
New privacy bug for Bitcoin Core 31.0 fit show di sender IP address of person wey send transaction to di receiving peer if certain network conditions balance.
Di Bitcoin Core 31.0 privacy bug dey affect small group of users wey dey run Bitcoin Core 31.0 with -privatebroadcast on, dey broadcast via sendrawtransaction RPC, fit reach Tor for outbound connections, still fit make direct IPv4/IPv6 outbound connections, and dey use BIP324 v2 transport without turning am off.
Di issue spoil di intended privacy of "private broadcast" during fallback path. If v2 handshake fail, Bitcoin Core go try again with v1 transport, wey fit bypass Tor and expose di sender clearnet IP to di peer. Onion/I2P peers no dey affected di same way.
E no put private keys, wallet balances, or Bitcoin consensus for risk, na network privacy problem e be, not one exploit wey go drain funds.
Workarounds till dem fix am for Bitcoin Core 31.1: turn off -privatebroadcast, turn off v2 transport (-v2transport=0), or route all outbound P2P traffic through Tor (for example -proxy=127.0.0.1:9050). Di people wey sensitive about privacy wey enable Bitcoin Core 31.0 privacy protections to avoid IP linkage na dem get highest exposure.
Neutral
Na one na privacy wahala for Bitcoin Core network, no be consensus bug or exploit wey fit comot people money. Usually dat one dey limit direct market yawa because holders no dey risk to lose coins immediately, and e no mean say all exchanges go dey unstable.
But privacy failure fit make privacy-sensitive traders change wetin dem dey do short-term (for example, dem fit change node settings, or change how dem dey relay/broadcast temporarily). Similar tins wey don happen before — privacy model regressions or transport-layer bugs — dey usually cause local worry rather than big sell-off, unless e join with bigger security incident.
Short-term, expect small “headline risk”: privacy-focused communities fit react quick, and developers/operators fit rush to apply workarounds while dem dey wait for Bitcoin Core 31.1.
Long-term, if dem deliver 31.1 fix well and people adopt am, the impact go fade. Market stability more likely go follow macro/ETF flows than this narrow Bitcoin Core 31.0 privacy bug.