Bitcoin Core v32 Enters Release Candidate Testing

Bitcoin Core has moved its next major software version into release-candidate testing, giving node operators, wallet developers and infrastructure providers an opportunity to evaluate v32.0 before the stable build is finalized. The project tagged v32.0rc1 on September 14 and subsequently opened a coordinated community-testing process. The release candidate is test software rather than a production upgrade that Bitcoin users or node operators are required to install.

Bitcoin Core’s current release schedule targets October 10 for the final v32.0 tag, but developers explicitly describe that date as an “aim.” Additional bugs found during testing could lead to more release candidates and move the stable release later. The concrete milestone today is the RC testing cycle, not the availability of Bitcoin Core 32.0 as a finished stable release.

Parallel Database Reads Target Faster Validation

One of v32.0’s main performance changes allows block validation to prefetch previous transaction outputs from the chainstate database in parallel while connecting blocks. Bitcoin Core introduces a new -prevoutfetchthreads setting with eight worker threads by default and support for up to 16. The optimization targets validation workloads that would otherwise wait for previous-output data to be read from disk, rather than changing Bitcoin’s consensus rules.

The release also makes the transaction index more storage-efficient. A fully rebuilt -txindex is expected to occupy less than half the previous disk space, although existing nodes must rebuild the index to obtain those savings. The change improves node-side storage efficiency while leaving the blockchain’s transaction history and validation rules unchanged. That distinction resembles other client-level software updates, where node performance improvements can ship independently of a network-wide protocol fork.

Bitcoin Core v32.0 also expands its RPC surface. A new exportwatchonlywallet command creates a wallet file containing public descriptors, transactions and address-book information without exporting private keys, while getopenrpcinfo exposes a machine-readable description of available RPC methods. Those additions primarily improve wallet administration and software integration rather than introducing new functionality at Bitcoin’s consensus layer.

Privacy and Network Handling Receive Separate Changes

Privacy-related work in v32.0 centers on networking rather than Silent Payments. The draft release notes describe a fix for a potential IP-address leak affecting transactions submitted through sendrawtransaction with private broadcasting enabled under a specific Tor and P2P v2 fallback scenario. That fix strengthens an existing private-broadcast mechanism, but it should not be confused with implementing BIP352 Silent Payments in the Bitcoin Core wallet.

The P2P layer also moves outgoing transaction relay toward a global backlog designed to reduce memory and CPU usage during periods of heavy transaction activity. Meanwhile, automatically created Tor hidden services can use proof-of-work defenses when supported by the local Tor daemon. These are client networking and resource-management changes, not modifications to what constitutes a valid Bitcoin transaction or block.

That separation matters because Bitcoin infrastructure changes occur at several different layers. A wallet migrating funds into a newer Bitcoin address format reflects wallet and transaction-format usage, while software-security problems can remain isolated to individual tooling, as seen when a compromised crypto SDK exposed private keys without compromising its underlying blockchain. Bitcoin Core v32.0 likewise changes node software behavior without activating new Bitcoin consensus rules.

Bitcoin Core is now asking testers to run the candidate across different operating systems and integrations and report issues through the project’s GitHub process. The next concrete milestone is the planned October 10 stable tag, provided release-candidate testing does not uncover bugs requiring another RC or a revised schedule. Until that tag is published, v32.0 remains software under evaluation rather than the latest stable Bitcoin Core release.