Bitcoin Core 32 Quietly Changes How Wallets Build PSBTs — Multisig Users Should Notice

Add TechGaged as your preferred source on Google

See more TechGaged stories across Google News and Discover.

Add

Bitcoin Core 32 is approaching release with a set of wallet changes that could matter far more to serious self-custody users than the version number suggests.

The second release candidate, v32.0rc2, changes PSBT-creating RPCs to use Partially Signed Bitcoin Transaction version 2 by default. It also adds new tools for exporting watch-only wallets and working with hierarchical deterministic keys.

The build remains a release candidate and is not intended for production wallets holding real funds. But the changes show where Bitcoin Core’s wallet stack is heading.

PSBT v2 becomes the new default

PSBTs are the format widely used to pass unsigned or partially signed Bitcoin transactions between software wallets, hardware devices and multiple signers. They are especially important in multisig setups where no single device should hold every key required to spend.

Bitcoin Core 32 changes the default behavior of RPCs that create PSBTs so they produce version 2 rather than the older format. PSBT v2 makes the transaction structure more explicit and easier for software to modify without repeatedly rebuilding the entire unsigned transaction.

For ordinary users, nothing suddenly changes on-chain. PSBT is a coordination format used before a transaction is broadcast. The significance is in interoperability between signing tools, custodians and multisig software.

Watch-only export gets a dedicated path

The release candidate also introduces exportwatchonlywallet, which can create a watch-only copy of a descriptor wallet without exporting its private keys.

That is useful for setups where an online machine needs to monitor balances and construct transactions while signing remains isolated on another device. Keeping private keys away from the internet is one of the core reasons sophisticated Bitcoin users separate transaction construction from transaction authorization.

Additional RPCs, including derivehdkey and addhdkey, are intended to make HD-key workflows and multisig coordination easier to manage directly through Bitcoin Core.

The important point is that Bitcoin Core 32 is not a flashy consensus upgrade. It is improving the machinery around self-custody, offline signing and multi-party control — areas that become increasingly important as larger amounts of BTC move into institutional and long-duration storage.

Users should still wait for a final production release before upgrading critical systems. Release candidates exist specifically to find problems before the software is treated as stable.

Source: Bitcoin Core releases.

The post Bitcoin Core 32 Quietly Changes How Wallets Build PSBTs — Multisig Users Should Notice appeared first on TechGaged.com.