×

Bitcoin Core v32.0rc1: Wallet Defaults and October 10 Target

Bitcoin Core v32.0rc1 is a test version of the software that powers the Bitcoin network, and it changes how the built-in wallet behaves by default ahead of a targeted October 10 final release. The headline change is a new set of wallet defaults, though several details still need official confirmation.

Bitcoin Core is the main software most computers use to run the Bitcoin network. A release candidate, like v32.0rc1, is a near-final test build. Developers publish it so people can try it before the real version ships. For related coverage, see KULR Sells Remaining 764 Bitcoin for Roughly $58.6 Million.

The official Bitcoin Core repository lists a release entry titled v32.0rc1: Bitcoin Core 32.0 release candidate 1. In plain terms, this is a practice run, not the finished product. For related coverage, see DeFi Bridge Hack: 25 Cents in Bitcoin, 46 Billion Fake BTC.

This matters for everyday holders too. If you keep a little Bitcoin on an exchange like Coinbase, this update touches the underlying network software rather than your account, so there is no action for you today. For related coverage, see ARMA Heads to Wednesday Markup Amid US Bitcoin Reserve Debate.

Bitcoin Core v32.0rc1 sets the stage for v32.0

Think of a release candidate as a dress rehearsal. Bitcoin Core v32.0rc1 is meant to be tested, then finalized as version 32.0 if no serious problems appear.

The clearest change involves the wallet defaults, meaning the settings the software uses automatically unless you choose otherwise. These defaults sit inside Bitcoin Core's own wallet tools, not third-party apps.

Bitcoin's software updates rarely move price directly, unlike company purchases such as when Strive bought 469 Bitcoin to grow its holdings. This release is about plumbing, not buying or selling.

Wallet default changes are the focus of the release candidate

The official draft release notes name the specific defaults that change. Four wallet commands, createpsbt, walletcreatepsbt, converttopsbt, and psbtbumpfee, will default to creating version 2 PSBTs.

A PSBT, or Partially Signed Bitcoin Transaction, is a shared draft of a transaction. Multiple people or devices can sign it in turn, like passing around a document that several people must approve before it is final.

The same four commands add an optional psbt_version argument. That lets the person calling the command pick which PSBT version to create, so version 2 is the default but not forced.

Fee handling also changes. The estimatesmartfee command now combines the existing block policy estimator with a new mempool fee-rate estimator, and when both work, it returns the lower result.

The wallet uses this combined estimate by default. Callers can still choose block_policy explicitly to get the previous fee-estimator behavior, so the old method remains available.

There is a catch. The combined estimate needs both estimators to succeed, and it can return an error while the mempool loads, when too few recent blocks have been seen, or when the mempool looks unhealthy.

The release also adds a new exportwatchonlywallet command. It exports public descriptors, transactions, and address-book data from a descriptor wallet without private keys, and restorewallet can import that file on another node.

One older feature goes away. The draft notes remove deployments.taproot from getdeploymentinfo, advising apps to assume Taproot has been active since Core v24.0 or to check TAPROOT in script_flags, available since v31.0.

Beyond these named items, the deeper details stay unconfirmed. The research brief does not spell out every affected wallet workflow, and it does not establish effects on existing funds, security, or required user action. Some reports warn of temporary disruption across popular wallet apps, but that claim is unverified, and no named app has been confirmed as affected. Draft release notes can also change before launch.

October 10 remains the target for the final release

The finished version 32.0 is targeted for October 10, according to the supplied headline. A target is a goal, not a guarantee, and the date is not the same as a completed launch.

No fetched official schedule confirms this date, so treat it as a plan that could shift. The release candidate being available now does not mean the final version is ready or suitable for everyone.

Bitcoin's price sat around $76,161 in mid-September, down about 3.6% on the day. That snapshot is background only, with no link to this software release, and Bitcoin has traded below its recent 30-day high lately.

The practical takeaway is simple. If you use Bitcoin Core's wallet directly, watch the final v32.0 release notes for the confirmed date and the new wallet defaults. If you only hold a little Bitcoin on an app or exchange, there is nothing you need to do now.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.