Bitcoin Core 32 Update: What Changes for Bitcoin Users and Nodes?

Bitcoin Core 32.0 is entering its final testing stage, marking another important software update for the Bitcoin network. The new version focuses mainly on improving how Bitcoin nodes process data, estimate transaction fees and interact with wallets and signing tools. 

It also includes several security fixes and storage improvements. Importantly, Bitcoin Core 32.0 does not change Bitcoin’s consensus rules, meaning it is a software upgrade rather than a network fork. For most everyday users, the changes will happen largely behind the scenes.

Key Takeaways

• Bitcoin Core 32.0 introduces a more responsive mempool-based fee estimator alongside the existing block-policy approach.

• Parallel previous-output fetching can make block validation and node synchronisation faster.

• PSBT v2 becomes the default for several commands, while important security and storage improvements are also included.

When Will Bitcoin Core 32.0 Be Released?

source by AI

BTC Core 32.0 has reached the final release-candidate testing phase. The first release candidate, Bitcoin Core 32.0rc1, was tagged on 14 September 2026, beginning the final testing window before the stable version. 

The stable release is targeted for 10 October 2026, around 12:58 UTC. Once the new version becomes stable, the older 29.x release series is expected to stop receiving security updates.

For node operators, this means planning an upgrade is becoming increasingly relevant. However, Bitcoin Core 32.0 is not a mandatory protocol upgrade in the same sense as a hard fork or soft fork.

Nodes can upgrade independently because the release does not introduce new consensus rules. Bitcoin blocks and transactions that were valid under the existing rules remain subject to the same consensus framework.

The main motivation for upgrading is therefore related to performance, compatibility, security and improved functionality rather than a change to how Bitcoin itself operates.

Read Also: How to Buy Bitcoin (BTC) Safely in 2026

What Are the Main Changes in Bitcoin Core 32.0?

One of the most noticeable improvements is the change to Bitcoin Core's fee estimation system.

Smarter Bitcoin Fee Estimation

Bitcoin Core 32.0 adds a mempool-based fee estimator alongside the existing block-history and block-policy estimator. By default, estimatesmartfee will use both approaches and return the lower fee when both estimates are considered valid.

This can make fee recommendations more responsive when network congestion begins to decline. Instead of relying primarily on historical block information, the new approach can respond more quickly to what is happening in the mempool.

Importantly, the new estimator is not designed to simply recommend increasingly lower fees. It will not raise or lower the recommendation beyond the limits of the block-policy estimator when that estimator is valid.

Applications and developers can also choose which estimation method they want to use through the new fee_rate_estimator parameter. The available approaches include block_policy, mempool_policy and the combined default.

For wallets and services using Bitcoin Core's fee guidance, this could result in more efficient fee recommendations during periods when network activity falls.

Faster Block Validation

Bitcoin Core 32.0 also improves block verification through parallel prefetching of previous transaction outputs, commonly known as prevouts.

Instead of handling all required data sequentially, Bitcoin Core can fetch relevant previous outputs in parallel. This is particularly useful when information needs to be retrieved from disk rather than already being available in memory.

The default configuration uses eight worker threads, with the option to increase this to 16. Operators can also disable the feature by setting.

The biggest benefits are expected during situations such as initial synchronisation or block validation involving substantial disk activity. Nodes with data already cached in memory may see a smaller improvement.

For operators running nodes on slower storage or systems with limited RAM, the change could reduce validation delays and make catching up with the network more efficient.

PSBT v2 Becomes the Default

Bitcoin Core 32.0 also changes the default PSBT version for several commands.

Partially Signed Bitcoin Transactions (PSBTs) are widely used in Bitcoin wallet and signing workflows, particularly when transactions need to be created and signed across multiple devices or applications.

Four commands will now default to PSBT version 2:

• createpsbt

• walletcreatepsbt

• converttopsbt

• psbtbumpfee

Developers can still request a different version using the psbt_version argument where necessary.

This is primarily an interoperability and wallet-software change rather than a consensus modification. Wallet developers and services that interact with Bitcoin Core should therefore test their signing workflows against the new defaults before moving production systems to the new version.

Read Also: Bitcoin (BTC) Price Prediction in the Next 100 Years

Security and Storage Improvements for Bitcoin Nodes

source by AI

Security is another major part of Bitcoin Core 32.0.

One notable fix addresses a walletnotify vulnerability affecting non-Windows systems. The issue could potentially allow command execution when specially crafted wallet names were processed using the %w placeholder.

The update changes how wallet names are handled and also rejects relative paths containing . or .., reducing the potential for this type of exploitation.

Bitcoin Core 32.0 also addresses a memory-exhaustion issue identified during auditing and testing of the newer HTTP server. Multiple unauthenticated REST connections could potentially cause memory usage to increase rapidly.

Additional RPC improvements are included as well. For example, getblockchaininfo provides better progress reporting for background validation associated with AssumeUTXO.

Lower Storage Requirements for txindex

There is also good news for operators concerned about disk space.

After a complete rebuild, the transaction index (txindex) in Bitcoin Core 32.0 is expected to require more than 50% less disk space.

Existing indexes remain compatible, so operators do not necessarily have to rebuild immediately. However, those who want to benefit from the reduced storage requirement will need to rebuild their transaction index after upgrading.

This could be particularly useful for services and long-term node operators that maintain transaction indexes and want to reduce their storage footprint.

Read Also: Bitcoin Price Prediction 2030 - What Is the Highest

What Does Bitcoin Core 32.0 Not Change?

Despite the number of improvements, Bitcoin Core 32.0 does not change Bitcoin's consensus rules.

That distinction is important.

The upgrade does not change which blocks or transactions are considered valid by Bitcoin's consensus system. It also does not change Bitcoin's block-time target or issuance schedule.

In other words, Bitcoin Core 32.0 is primarily about improving the software used to interact with and operate the Bitcoin network. 

The gains come from better fee estimation, data handling, validation performance, wallet functionality and security rather than changes to Bitcoin's underlying monetary policy.

For regular Bitcoin users, the impact may therefore be subtle. Someone using a third-party wallet may not notice any major difference unless the wallet incorporates the updated Bitcoin Core functionality.

Node operators and developers, meanwhile, have more reasons to pay attention to the release.

Read Also: Bitcoin (BTC) Price Prediction and Analysis for September

What Should Bitcoin Users and Node Operators Do?

Node operators can begin by testing the release candidate on a non-critical system rather than immediately replacing a production node.

Before the stable release, operators should review their configuration, check software compatibility and plan an upgrade around the 10 October target.

Wallet developers should specifically test the new fee-estimation behaviour and PSBT v2 defaults. Applications that require precise control can use fee_rate_estimator and psbt_version where appropriate.

For ordinary Bitcoin users, there is generally less to do. If your wallet or node software provides an update notification, installing the stable version after release can provide access to the latest security and performance improvements.

As always, users should download software only from trusted sources and verify release information before installing an update.

Read Also: BTC Price Prediction Challenge: Guess and Win BTC

Conclusion

Bitcoin Core 32.0 is a substantial software improvement focused on making Bitcoin infrastructure more efficient, responsive and secure without changing Bitcoin's consensus rules. 

Smarter fee estimation, faster block validation, PSBT v2 defaults, security fixes and potential txindex storage savings could benefit different parts of the Bitcoin ecosystem. 

While everyday users may notice few immediate changes, developers and node operators should pay closer attention to compatibility and upgrade planning. 

For users looking to trade Bitcoin and other digital assets alongside staying informed about network developments, Bitrue provides a convenient platform designed to make crypto trading easier and safer.

FAQ

What is Bitcoin Core 32.0?

Bitcoin Core 32.0 is a new version of the Bitcoin Core software used by Bitcoin nodes. It introduces improvements to fee estimation, block validation, wallet functionality, security and storage efficiency.

Does Bitcoin Core 32.0 create a Bitcoin fork?

No. Bitcoin Core 32.0 does not introduce consensus-rule changes, so the upgrade is not a network fork. Nodes can upgrade independently.

When is Bitcoin Core 32.0 expected to be released?

The stable release is targeted for 10 October 2026, following the release-candidate testing phase that began with Bitcoin Core 32.0rc1 on 14 September 2026.

What is changing with Bitcoin transaction fee estimation?

Bitcoin Core 32.0 adds a mempool-based fee estimator alongside the existing block-policy estimator. The default combined approach can provide more responsive fee recommendations when network congestion changes.

Do regular Bitcoin users need to upgrade?

Users who operate their own Bitcoin Core node should plan to upgrade to the stable release for ongoing security support and compatibility. Users relying on third-party wallets may not need to take any direct action unless their wallet provider releases an update.

Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.