Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
BTC Bitcoin Core released version 31.1 to fix IP address disclosure vulnerability
Bitcoin Core has released version 31.1, which is a maintenance update that fixes a security vulnerability that leaks IP addresses through the privatebroadcast feature. Node operators running earlier versions should upgrade as soon as possible.
What Bitcoin Core 31.1 fixes
Bitcoin Core 31.1 version resolves a flaw in the privatebroadcast mechanism that may expose the IP address of a node operator. The Bitcoin Core project officially disclosed this vulnerability on June 6, 2026. According to official disclosures, the vulnerability allows attackers to associate users \'transaction broadcasts with their IP addresses, undermining the privacy protections that privatebroadcast is supposed to provide.
This fix is included in the v31.1 version on GitHub, and this version also includes some other minor improvements and bug fixes, which are typical features of minor updates.
Why this is crucial for the Bitcoin network
Bitcoin Core is a reference implementation that drives the vast majority of full nodes on the Bitcoin network. The vulnerabilities in the software, especially those that affect user privacy, are of great significance to the ecosystem.
IP address disclosure is a serious problem because it can allow third parties to associate on-chain transactions with real-world identities. For node operators who rely on privacy as a security measure, unpatched systems represent an ongoing risk.
Such vulnerabilities will not affect the integrity of the Bitcoin protocol itself or the blockchain. Consensus rules, transaction finality and online settlement will not be affected. The problem is limited to the software layers run by individual node operators.
This disclosure continues the trend of increasing attention to the security of Bitcoin infrastructure. Earlier this year, CZ warned cryptocurrency developers to check keys, and Jameson Lopp pointed out a covert witch attack on Bitcoin nodes, highlighting the growing attention given to node-level threats.
What should node operators do next
Operators of any Bitcoin Core node running earlier than version 31.1 should review the release notes and upgrade as soon as possible. The update is available through bitcoincore.org and the standard download channels in the project\'s GitHub repository.
After upgrading, operators should verify that the running version is 31.1 by checking the output of bitcoind --version or the debugging console in Bitcoin-Qt. Confirming that updates are applied correctly is a basic but necessary step.
Operators should also monitor node logs to pay attention to whether there is abnormal node behavior in the days after the upgrade. Although the fix closes the path for IP leakage, the IP address may have been exposed during running the vulnerable version.
The recent memory upgrade to the Bitcoin Test Network is an independent development, but these two updates together reflect the proactive maintenance of Bitcoin\'s core infrastructure in the second half of 2026.
Disclaimer : This article is for information reference only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risks. Before making a decision, be sure to study it yourself.
