Bitcoin Core developers have released the fourth candidate for version 32.0 as testing continues ahead of the software’s final stable release. The v32.0rc4 build incorporates another set of networking, privacy and RPC fixes discovered during the release-candidate cycle, rather than introducing a new round of major features.
The official v32.0rc4 tag was published on October 12 with a verified signature and follows rc3 after additional fixes were backported into the 32.x branch. Bitcoin Core 32.0 remains a release candidate rather than a stable production release, with developers continuing to request testing across supported operating systems and integrations before finalization.
The development cycle had originally targeted October 10 for the final 32.0 tag, but that date has passed while candidate testing continues. The additional rc4 build illustrates the purpose of the release-candidate process: resolving regressions and edge cases before the stable software is published, rather than treating the original schedule as a fixed activation deadline.
Private Broadcast Receives a Timing-Privacy Fix
One of the more consequential rc4 backports affects Bitcoin Core‘s experimental private-broadcast functionality. The mechanism is designed to reduce information leakage when a node originates a transaction by initially relaying it through a limited set of dedicated peer connections rather than immediately using conventional transaction propagation.
The revised logic ensures that all three initial private-broadcast connections are completed even if the transaction returns to the originating node’s mempool or becomes conflicted before every connection finishes. Developers identified the previous behavior as creating a theoretical timing signal that could help an observer infer whether a particular node originated the transaction.
The change does not make Bitcoin transactions anonymous. Private broadcast remains explicitly experimental and addresses a specific transaction-origin privacy problem rather than hiding transaction amounts, addresses or the public blockchain record. Its security model is therefore better understood as reducing network-layer metadata leakage, not providing comprehensive transaction privacy.
This work extends a broader evolution in Bitcoin Core’s relay behavior. Version 30.0 previously lowered the default transaction relay floor to 0.1 sat/vB, another policy-level change that affected how nodes propagate transactions without changing Bitcoin’s consensus rules. Version 32.0 similarly contains networking behavior that matters at the node-policy layer rather than altering the protocol’s monetary or consensus parameters.
rc4 Fixes Socket and RPC Edge Cases
Another backport caps excessively large finite timeouts passed to Sock::WaitMany. The issue affected configurations such as bitcoin-cli -rpcclienttimeout=0 on macOS, where the software translated the setting into a multiyear timeout that could exceed what the underlying select() implementation accepted. The fix limits the timeout to approximately 24.8 days, preventing the operating-system error while preserving a practically long waiting period.
The candidate also corrects Bitcoin Core’s generated OpenRPC schema so hexadecimal fields can validly contain empty strings. This is primarily a tooling and API-description fix rather than a change to Bitcoin transaction validation. The correction improves compatibility for software consuming Bitcoin Core’s machine-readable RPC specification without modifying the behavior of the underlying RPC methods themselves.
Other backports incorporated before rc4 include HTTP testing refinements and a correction to how bitcoin-util displays the genesis block hash. Together, these changes show that rc4 is predominantly a stabilization build assembled from narrowly scoped fixes identified during testing, not a separate feature release.
Bitcoin Core’s testing issue remains open, and the project’s release process requires further review before the candidate designation is removed. The final 32.0 release will only represent the stable milestone once developers publish the non-RC tag, making rc4 an important testing checkpoint but not the completion of the version 32.0 rollout.