News Bitcoin basics Wallets and security
Bitcoin Core 32.1 arrives: changes and the skipped 32.0
The Bitcoin Core project announced version 32.1 on 27 October 2026, making it the first public release in the 32 series. Developers say version 32.0 was tagged in the code repository but never fully released because of last-minute issues. The update combines a new fee estimator with privacy and security fixes and operational changes, while moving version 29 and older outside the maintenance window.
Checked on 5 November 2026.
This is an update to software that operates nodes and includes a wallet. It is not a new coin or a requirement for every bitcoin holder to take action. Someone using another app or a hardware wallet may not run Bitcoin Core at all. The first question is which software they operate and which services depend on it.
A version tag is not a completed release
The official release notes (Opens in a new tab) explain that 32.0 was tagged but never fully announced or released. A tag identifies a particular point in the source repository. That differs from completing distribution, including testing, installation files and an announcement to users. There is no missing public release that users need to locate before installing 32.1.
The project's announcement is dated 27 October, while the GitHub release entry displays 28 October. These are dates on different publication channels, rather than evidence that one necessarily invalidates the other. For readers who followed the Bitcoin Core 32 release candidate, this marks the move from testing to a public release.
Fee estimation also considers transactions waiting now
The estimatesmartfee command now combines the existing block-policy estimator with a new estimator based on the mempool, the collection of pending transactions. Under the default combined behaviour, the lower of the two estimates is returned. The new estimator can therefore reduce the result relative to the older mechanism, rather than raise it above that estimate.
Operators needing the previous behaviour can explicitly select block_policy. Other options include mempool_policy and auto. These settings determine how an estimate is calculated. They are not a network commitment to confirm a transaction by a particular time, because congestion and the mix of waiting transactions can change after the estimate is produced.
The distinction also matters to users who never read code: an estimate is a software recommendation based on available information; confirmation happens when a transaction is included in a block. Total fees also depend on transaction size. Our guide to bitcoin fees and confirmations explains why a lower estimate need not indicate a fault, and why a long wait does not by itself mean funds have disappeared.
Two fixes with specific conditions
The privacy fix concerns transactions sent using sendrawtransaction with privatebroadcast enabled. Under certain conditions, a v2 connection attempted through Tor could fail, with the subsequent v1 retry connecting directly. That could reveal the sender's IP address. The change addresses this fallback path.
The release notes describe cumulative conditions, including a configured Tor service, permission for direct IPv4 or IPv6 connections and a peer advertised as supporting v2 that does not actually support it. This does not mean every bitcoin transaction exposed an IP address. Nor does installing the update guarantee complete anonymity. The fix addresses a specific way the chosen privacy route could be bypassed.
A second fix affects non-Windows systems. An authenticated RPC caller permitted to create wallets could execute commands as the node process account, when walletnotify was configured, through special characters in a wallet name. The updated handling treats the name literally. Those permission and configuration requirements are part of the finding; it is not a claim that any internet user could drain any wallet.
More connections, and a smaller index after rebuilding
The default maxconnections setting rises from 125 to 200. A new inboundrelaypercent setting limits the share of incoming slots used by transaction-relaying peers, with a default of 50%. The number of automatic outgoing connections is unchanged, and an operator's explicit maxconnections value is not automatically replaced with 200.
The txindex transaction index has also changed. Developers say a rebuilt index occupies less than half its previous disk space. Existing indexes do not shrink automatically when the software is installed. Rebuilding can take hours, and the new format has consequences for anyone returning to an older release. The saving concerns this particular index, not the size of the entire blockchain.
Libevent has also been replaced with a custom HTTP server. Ordinary users may notice little, but operators connecting tools through RPC should check compatibility because some HTTP edge cases are handled differently. An update can affect the connections between systems even when a node's main functions remain familiar.
What to check before upgrading
Supported and tested operating systems begin at macOS 14, Windows 10 version 1903 and Linux kernel 3.17. The project maintains three major series, so version 29 and earlier are now classified as end of life. Operators should also check wallet compatibility, backups and connected applications rather than treating a version number as the entire upgrade plan.
Downloads should be reached through the project website, with signatures and hashes checked using its instructions. The software should be shut down completely before its files are replaced. Updating a node does not require giving a download website a private key or recovery words. These are software and self-custody practices, applying to operators in Israel as elsewhere.