Bitcoin developers have released Bitcoin Core 31.1, a maintenance-focused update. The new version includes performance improvements as well as bug fixes. The focus of the update is a vulnerability affecting node operators and database-related hardware overhead.
Security vulnerability closed
developer team,
The new version fixes an IP address leak when using the -privatebroadcast feature.
he stated. This issue could unintentionally reveal the node’s real IP address on the open internet in the configuration that users use for privacy purposes.
Bitcoin Core is known as one of the most common clients used to run full nodes on the Bitcoin network. With the correction, the aim of node operators to remain anonymous is supported, while accidental disclosure of open network IP addresses is prevented.
Database error was increasing disk load
Version 31.1 was not limited to just security patches. The update also fixed an issue that was causing excessive disk operations on the leveldb side. The team fixed a bug where the chainstate database, which holds chain state, repeatedly wrote large portions of itself during normal operation.
This issue was causing unnecessarily high disk reads and writes during normal use.
The bug in question could create unnecessary hardware pressure, especially on constantly running nodes. With the fix, the reduction in disk reading and writing load may contribute to more efficient use of system resources.
Mini dictionary: LevelDB is a lightweight key value database used to store data within Bitcoin Core. Chainstate, on the other hand, keeps data that allows the node to keep track of the current state of the chain, such as unspent transaction outputs.
Maintenance was also done on the wallet side
The update also includes maintenance changes to the wallet infrastructure. The developer team added an improvement to the system that includes the final BDB page LSN check during the migration process. Also included in this release is a fix for using outpoint in input size estimation.
Although these steps do not offer major innovations that are directly reflected in the end user interface, they contribute to making the wallet operation more consistent. Such regulations, especially at the infrastructure level, are important in reducing incompatibilities that may occur in the future.
Node needs to be completely shut down for update
Developers recommend that node operators update their systems without delay to benefit from security and database improvements. Before new binaries are installed, the worker node needs to be completely shut down.
This process is considered critical to maintain data integrity during installation. The team particularly emphasizes the complete shutdown step, as leaving the old session open during the update process may cause unexpected problems.
