Bitcoin Core 32 in testing: fees, PSBT and preparing for change

As checked on 29 September 2026, Bitcoin Core's testing guide lists 32.0rc2 as the current release candidate. The schedule targets 10 October for the final version, rather than committing to it. This is an opportunity to test compatibility before a routine upgrade, not an announcement that the final version is already available. Testing guide (Opens in a new tab) | Schedule (Opens in a new tab)

PSBT: test the entire signing process

According to the draft release notes, the commands createpsbt, walletcreatefundedpsbt, converttopsbt and psbtbumpfee create PSBT version 2 by default, with the option to specify a version using psbt_version. Draft release notes (Opens in a new tab)

For compatibility testing, we recommend working through the entire process: creation, transfer to the signing tool, signing and completion. Do not stop at the first program successfully exporting a file. Record what happens in the next tool in the chain, so a gap is not discovered only during a real operation. The wallet guide provides background on how responsibilities are divided between tools.

Fee estimation: an error is also a result to handle

The draft describes combining a block-based estimate with one based on pending transactions. The combined mode returns the lower of the two when both succeed. If the new estimate is unavailable, an error may be returned; there is also an option to select the block-based estimate explicitly. Draft release notes (Opens in a new tab)

For testing, this means checking missing data and error responses as well as a valid fee figure. The description does not promise consistent savings or a particular confirmation time. The guide to fees and confirmations provides further context.

How to prepare a useful test

The project's guide includes experiments in a regtest environment and stresses that it does not cover every possibility. Use it as a starting point and add scenarios reflecting the operations your system actually performs. Official guide (Opens in a new tab)

A suggested testing framework: record the current version and the expected result for each operation; run the same operation in a separate environment; compare the result and error handling. Do not use customer funds or real seed phrases for a compatibility experiment.

What to check again before upgrading

Reread the release notes and upgrade instructions for the version that is actually published. Findings about a release candidate are no substitute for the final document. This article aims to focus preparation on practical questions, not to recommend that every wallet user install test software.