Bitcoin Core 31.1 Patches IP Leak in Private Broadcast and Critical Disk Usage Bug

Bitcoin Core 31.1 Patches IP Leak in Private Broadcast and Critical Disk Usage Bug

N
News Editor 01
2026-07-24 02:05:18
Bitcoin Core 31.1 fixes an IP leak when using -privatebroadcast and a LevelDB bug causing excessive disk I/O. Wallet migration checks are improved. Full node shutdown required before update.

The Bitcoin Core development team has released version 31.1, addressing two high-priority issues: an IP address leak in the -privatebroadcast feature and a LevelDB bug that triggered abnormally high disk read/write operations. Node operators are urged to upgrade as soon as possible, with the critical reminder that the running node must be fully shut down before installing new binaries.

Private broadcast IP leak fixed

According to the team, when users enabled the -privatebroadcast option to hide the source of their node's announcements, their actual public IP could still be exposed on the open internet, defeating the privacy measure. Bitcoin Core is the most widely used client for running full nodes on the Bitcoin network. This flaw meant operators seeking anonymity were at risk of being identified. The 31.1 update eliminates that exposure completely.

LevelDB disk write amplification bug removed

On the performance side, the new version squashes a bug in LevelDB, the lightweight key-value store underpinning Bitcoin Core. The chainstate database, which tracks the blockchain's current state, was repeatedly rewriting large segments during normal operation, causing unnecessary spikes in disk I/O. For nodes running continuously over long periods, this could create significant hardware strain. With the fix, disk read/write demands should drop considerably, allowing more efficient resource usage.

Wallet stability upgrades

Version 31.1 also brings maintenance changes to the wallet infrastructure: strengthened checks for the last BDB page LSN during migration, and a corrected outpoint usage calculation in input size estimation. These improvements may not deliver flashy new features, but they reduce the risk of compatibility or functionality issues down the line, making wallet operations more consistent.

Full shutdown required before updating

Developers emphasize that the node must be completely shut down before applying the new binaries. Leaving previous sessions open during installation can lead to data integrity problems. Operators are encouraged to upgrade promptly to benefit from the privacy, stability, and performance fixes.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
6900

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.