CryptoSlate
Bitcoin Core v32.0rc1 was tagged on Sept. 14 with a verified signature, kicking off a 26-day RC window that targets an Oct. 10 final release. The candidate is prerelease software, not a production upgrade, and crucially does not activate any new consensus rules. Four RPCs default to PSBTv2 in this version, while the largest performance change adds parallel prefetching of transaction outputs during block connection (default 8 workers, configurable up to 16).
Why it matters
The update carries real performance and compatibility gains rather than a token-level shock. Parallel block-output prefetch cuts validation time on disk-bound hardware, and the rebuilt transaction index uses less than half the disk space of the previous format. Wallet teams that create, convert or fee-bump PSBTs need to trace those flows through their downstream parsers and signers, while fee handling gets a new default path that combines block-policy and mempool estimators and can error if either component fails. The HTTP server rewrite broadens the test surface further: an 8,192-byte header limit, a default ceiling of 16 RPC connections, new REST cache controls and immediate disconnection of unauthorized client addresses.
Market impact
The disruption risk is concentrated in operational breakage, not in consensus. Older node versions cannot read the new transaction index format, which means a downgrade triggers another rebuild that can run hours. Privacy-focused operators also need to reproduce failure paths around the Tor fallback fix, the 10,000-entry queue and the 1,000-attempt relay limit. With the final tag still only an aim, the practical work of the RC window is exposing these edge cases against the 31.1 baseline before the Oct. 10 deadline.
Frequently asked questions
-
When is Bitcoin Core v32.0 expected to release?
The v32.0rc1 candidate was tagged Sept. 14 with a verified signature, with Oct. 10 listed as the aim for the final v32.0 tag, leaving a 26-day RC window.
-
Does Bitcoin Core v32 activate new consensus rules?
No. The v32 release is a software update that changes default RPC behavior and performance settings, but does not signal a new consensus-rule activation.
-
What wallet-facing changes ship in Bitcoin Core v32?
Four RPCs default to PSBTv2, while other interfaces remove deprecated fields or reject arguments older versions tolerated. Teams creating, converting or fee-bumping PSBTs should trace those flows through downstream parsers and signers.
-
What is the biggest performance change in Bitcoin Core v32?
Parallel prefetching of transaction outputs during block connection, defaulting to 8 workers and supporting up to 16. Operators can compare disk-bound validation across settings to gauge CPU, memory and storage-latency tradeoffs.
-
What happens if an operator downgrades from Bitcoin Core v32?
The rebuilt transaction index uses less than half the disk space, but older releases cannot read the new format. A downgrade triggers another rebuild that can last hours.
Crypto News
TheBlock
WuBlockchain
CoinDesk
Glassnode
Crypto Capital Venture