October 10, 2026
Target release date for Bitcoin Core 32.0 4
8 threads
Default parallel database threads for block checking 4
3 MB
Memory usage after REST server patch, down from 3.2 GB 4

Bitcoin Core 32.0 Release Cycle

Bitcoin Core developers have initiated the final testing cycle for the next major software update, version 32.0 4. The first release candidate for this version was tagged on September 14, 2026, with developers aiming for a final release on October 10, 2026 45. This update does not alter Bitcoin's consensus rules, but it introduces several performance enhancements, security patches, and wallet-related modifications 45. Node operators and developers are encouraged to test the release candidates to ensure stability before the official launch 45.

Performance and Fee Estimation Upgrades

To accelerate block verification, Bitcoin Core 32.0 introduces parallel processing when retrieving transaction data from the database 45. The software will utilize eight processing threads by default to fetch data, reducing disk-read wait times when a node is synchronizing with the blockchain 4.

Additionally, the update modifies how transaction fees are estimated 4. Currently, the software estimates fees based on transactions confirmed in previous blocks 4. Version 32.0 adds a second estimator that analyzes unconfirmed transactions waiting in the mempool 4. By comparing both estimators, the software can recommend lower fees when network conditions support it, rather than relying solely on historical block data 4.

Security Patches and Memory Fixes

The upcoming release addresses a command injection vulnerability that has existed since version 24.0 on non-Windows operating systems 4. Under specific conditions, an authenticated user with wallet-creation permissions could execute arbitrary commands on the host machine by assigning a specially crafted name to a wallet 45. This exploit required the node operator to have enabled the walletnotify feature, which triggers external commands during wallet transactions 45. Version 32.0 mitigates this by treating wallet names strictly as literal text 4.

Developers also resolved a memory-exhaustion vulnerability in the node's new HTTP server 45. Discovered by contributor Matthew Zipkin using Moonshot AI's Kimi K3 model, the flaw allowed data to accumulate in memory faster than the server could process it, potentially causing an out-of-memory crash 45. Although initially thought to only affect authenticated clients, further review by GitHub user jeanpablojp revealed that unauthenticated REST connections could also trigger the leak 45. In testing, 16 unauthenticated connections caused a node's memory usage to surge from 46 MB to about 3 GB in roughly a minute 4. Following a patch merged on September 5, 2026, a 90-second test resulted in only 3 MB of memory growth 45.

Wallet and Transaction Format Adjustments

Bitcoin Core 32.0 updates the default format for four commands used to generate partially signed Bitcoin transactions (PSBTs) to PSBT version 2 45. While applications can still request the older format, services relying on these commands must ensure compatibility with the new default 4.

The release also incorporates several bug fixes from recent development 1. PR #35445 resolves a compatibility issue introduced in version 31.0, where existing descriptor wallets using "h-style" hardened derivation markers failed to load 1. This bug occurred because a previous change, #31734, altered how internal descriptor identifiers were calculated, leading the software to incorrectly flag the wallets as corrupted 1. The fix treats stored identifiers as links between records rather than values to recompute 1.

Furthermore, PR #36076 ensures that the combinepsbt command does not discard an input's requested signature hash type when merging transactions 1. PR #35975 addresses a wallet crash that occurred when calling bumpfee on two malleated versions of the same transaction, ensuring that bumping one version marks all variants as replaced 1.

What is not yet established

  • Whether testing feedback will delay the targeted October 10, 2026 release date.
  • The exact performance impact of the parallel database threads on various hardware configurations.

Frequently asked questions

What security vulnerabilities does Bitcoin Core 32.0 fix?

It fixes a command injection flaw in non-Windows systems using walletnotify since version 24.0, and a memory exhaustion vulnerability in the new HTTP/REST server 45.

How does the new fee estimation work?

In addition to historical block fee data, version 32.0 introduces a second estimator that looks at unconfirmed transactions in the mempool to recommend lower fees when congestion clears 4.

Sources

  1. Bitcoin Optech — Bitcoin Optech Newsletter #423 (2026-09-18) https://bitcoinops.org/en/newsletters/2026/09/18
  2. Delving Bitcoin — Bounds on chain length with BIP-54 timewarp fixes (2026-09-17) https://delvingbitcoin.org/t/bounds-on-chain-length-with-bip-54-timewarp-fixes/2899
  3. Delving Bitcoin — PQLN: Post-Quantum Security for the Bitcoin Lightning Network's Off-Chain Surfaces (2026-09-16) https://delvingbitcoin.org/t/pqln-post-quantum-security-for-the-bitcoin-lightning-networks-off-chain-surfaces/2893
  4. CoinDesk — Bitcoin Core 32 enters final testing with faster validation, fee changes and security fixes (2026-09-16) https://www.coindesk.com/tech/2026/09/16/bitcoin-core-32-enters-final-testing-with-faster-validation-fee-changes-and-security-fixes
  5. Decrypt — Bitcoin Core Software Update Aims for Speed and Security Patches (2026-09-16) https://decrypt.co/378430/bitcoin-core-software-october-update

This brief is for information and education. It is not financial advice or a recommendation to buy or sell.