Bitcoin Core has tagged release candidate v32.0rc1, opening a compatibility test window that runs to the planned final tag on Oct. 10. The build changes default wallet and RPC behavior, including a shift to PSBTv2 on four RPCs, and node operators and wallet providers now have a limited window to test before it ships.
Bitcoin Core v32.0rc1 carries a verified signature dated Sept. 14, and the project's release schedule lists Oct. 10 as the target for the final v32.0 tag. That leaves node operators, wallet providers and services built on Bitcoin Core's RPC interfaces a 26-day window to test the candidate before it becomes production software.
The tag is a release candidate, not a final build, and it does not activate any new consensus rule. One change tied to the still-draft BIP 323 alters how the software treats signaling bits and unknown-deployment warnings, but the proposal itself remains in draft status.
Wallets and fee estimation face the compatibility risk
Four RPCs will default to PSBTv2, while other interfaces drop deprecated fields or reject arguments that older versions accepted. Teams that create, convert or fee-bump PSBTs need to trace those transactions through their parsers and signers before the final tag ships.
Fee handling needs the same scrutiny. The default estimatesmartfee path now combines block-policy and mempool estimators. It can return a lower estimate or error if either component fails, so operators should test sparse or unhealthy mempool conditions and confirm their fallbacks still work.
Faster block validation comes with a rollback cost
The candidate's largest performance change is parallel prefetching of transaction outputs during block connection, defaulting to eight workers and supporting up to 16, or it can be disabled. A rebuilt transaction index uses less than half the disk space of the current one, but older releases cannot read the new format, so downgrading can trigger another rebuild lasting hours.
The HTTP server rewrite adds an 8,192-byte header limit, a default ceiling of 16 RPC connections, and immediate disconnection of unauthorized client addresses, changes that can surface in reverse proxies, health checks and client pools rather than the node itself.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
