Bitcoin Core 32 Enters Final Testing With October Target

The v32.0rc1 candidate introduces parallel database reads to accelerate block validation. While this optimization shortens the time a node requires to process incoming data, it does not alter Bitcoin's underlying proof-of-work consensus or the 10-minute target for block production. Because Bitcoin Core functions as optional node software, operators retain full discretion over whether to upgrade, avoiding the complex coordination required for protocol-level forks.

Wallet management receives a significant update as four commands shift to PSBT version 2 by default. This newer format improves transaction flexibility, allowing participants to update transaction components without requiring a complete unsigned package. To maintain compatibility with existing infrastructure, the software continues to support the legacy PSBT format for services not yet updated to the new standard.

Security remains a primary focus of this cycle, with patches addressing specific vulnerabilities in wallet naming conventions and unauthenticated HTTP requests. Developers identified a memory-related flaw where unauthenticated activity could cause usage to spike to 3.2 gigabytes; the fix reduces this footprint to approximately 3 megabytes. These improvements arrive as institutional interest in Bitcoin infrastructure grows, highlighted by the recent formation of the Bitcoin Security Consortium, which includes participants like BlackRock and Fidelity.