Bitcoin Core 32.0 has moved into final testing before its scheduled release on October 10, bringing a set of changes focused on fee estimation, faster validation and security maintenance.

The update alters how nodes estimate transaction fees and process blockchain data, while also addressing two security issues affecting the wallet and the software’s web server.

Fee estimates tuned to current mempool conditions

One of the main changes in version 32.0 is the addition of a second fee estimator that looks at transactions still waiting for confirmation. By taking unconfirmed activity into account, Bitcoin Core can adjust its estimates more quickly when the network becomes congested.

The change is also intended to allow the software to suggest lower fees when conditions permit, rather than relying only on historical confirmation data. That makes fee guidance more responsive to current network conditions.

Faster block and transaction processing

Bitcoin Core 32 also introduces multi-threaded data retrieval for transaction data and block verification. The software will use eight processing threads by default.

According to the update notes, that should speed up the catch-up process for nodes syncing with the chain, improving validation performance as blocks and related transaction data are processed in parallel rather than through a single thread.

Wallet and server vulnerabilities addressed

The release fixes a wallet vulnerability affecting non-Windows systems that has been present since Bitcoin Core 24.0. Under certain conditions, an authenticated user creating a wallet could execute commands on a node.

The issue was addressed by treating wallet names as literal text instead of allowing them to be interpreted as possible command instructions. Bitcoin Core 32 also replaces the project’s web server after a memory-exhaustion vulnerability was identified. Before the fix, handling requests, including through REST, could allow unlimited memory growth.

Wallet format changes and final steps

Beyond the security fixes, the update changes wallet behavior by making PSBT version 2 the default for four commands that create partially signed bitcoin transactions. Older PSBT formats remain available if specifically requested.

With final testing now underway, the next confirmed step is the planned October 10 release. The current testing phase is the last stage before that rollout, giving contributors and operators a chance to verify the new fee logic, performance changes and security patches before the version is published more broadly.

Source: www.coindesk.com