Bitcoin Core v32.1 Released

Users operating on outdated releases will no longer receive updates or security patches, emphasizing the importance of transitioning to the latest software to maintain network reliability and security. The development team encourages users to report any software bugs through the GitHub issue tracker, ensuring continuous improvement and responsiveness to community feedback.

The release introduces a comprehensive suite of new features, performance enhancements, bug fixes, and updated translations. Security remains a priority, with the security policy guiding vulnerability disclosures and the imminent public announcement of three resolved medium or high severity issues from version 30.0. Compatibility extends to contemporary operating systems, including Linux Kernel 3.17+, macOS 14+, and Windows 10 (version 1903)+. While Bitcoin Core may run on other Unix-like platforms, official support and testing are limited to these recommended environments, and deployment on unsupported systems is discouraged.

Peer-to-peer networking enhancements focus on resilience and efficiency. Integration with Tor hidden services now supports proof-of-work defenses when compatible Tor daemons are detected, bolstering resistance against certain attacks. Outgoing transaction relays utilize a global backlog for rate-limiting, replacing per-peer limits to better manage memory and computational resources during periods of high activity. This behavior is configurable via the -txsendrate parameter. Measures have been implemented to prevent potential leaks of originator IP addresses in specific private broadcast scenarios involving protocol fallback and Tor usage. The private-broadcast queue is restricted to 10,000 entries, and each transaction sent privately is capped at 1,000 attempts, requiring manual intervention thereafter.

Networking protocols continue to evolve, with I2P support phasing out legacy ElGamal encryption and full removal scheduled by version 34. Nodes reliant on deprecated cryptography will face increasing isolation. CJDNS support is under review, affected documentation has been streamlined, and configuration steps simplified due to minimal adoption. Peer connectivity receives an upgrade with the default maximum number of automatic peer connections raised from 125 to 200, facilitating more robust inbound access for block-relay-only peers without compromising safeguards against excessive connections.

Mempool management and remote procedure call (RPC) interfaces exhibit notable refinements. Deprecated Replace-by-Fee (RBF) arguments are eliminated unless specifically enabled; legacy fields in RPC responses are likewise excluded by default, decluttering outputs. New RPC fields provide granular transaction size metrics and improved diagnostics for non-standard transaction inputs. The dumptxoutset RPC can efficiently stream output to named pipes, optimizing UTXO set processing. Fee estimation through estimatesmartfee now integrates block and mempool policies for nuanced, real-time results, with persistent data storage and configurable detail levels.

Wallet functionality benefits from expanded RPC capabilities, featuring commands such as addhdkey, exportwatchonlywallet, and derivehdkey to streamline hierarchical key management, facilitate multi-signature setup, and enable watch-only wallet export. Enhanced interface messages clarify fee selection logic and restrict hazardous wallet naming practices. Experimental status has been lifted from send and sendall RPCs, while obsolete commands are deprecated or excised for improved reliability. Notification handling within wallets sees strengthened placeholder replacement mechanisms, further securing user operations.

Graphical interface improvements introduce direct creation of watch-only wallets through an accessible menu, align replaceability settings with overarching wallet configurations, and eliminate now-redundant options. Migration processes are refined, and compatibility extends to building with Qt 6.8.4, enhancing the overall user experience.

Mining operations and inter-process communication (IPC) interfaces have been overhauled for greater transparency and error reporting. Mining template submissions now return explicit rejection reasons and debugging details, properly handle duplicate submissions, and validate block template options rigorously. Logging granularity is increased through a dedicated mining category. REST API endpoints adopt differentiated cache-control headers, distinguishing immutable from dynamic responses to optimize client caching.

At the infrastructure level, transaction index handling has been optimized to consume less disk space, preserving backward compatibility for existing deployments and providing guidance for reclaiming storage via index rebuilding. The HTTP server stack transitions from Libevent to a bespoke implementation, enforcing stricter RFC compliance and immediately disconnecting unauthorized RPC clients to strengthen security.

It is worth noting that nodes running this new release, such as the x86_64 Linux instance hosted at anyone.eu.org, have experienced multiple restarts since upgrading to 32.1, indicating that monitoring and community feedback remain essential as users deploy this update across diverse environments.