Bitcoin Core, the top software client for running a Bitcoin node, is scheduled to enter its v32 feature freeze on Thursday, Aug. 20. The deadline shifts the release line to bug fixes and gives new v32 features their final normal window before the project’s October release target.
The v32 milestone listed 17 items open and 79 closed on Aug. 17, putting the work at 82% complete. Those 17 entries span feature pull requests, bug reports, build and logging work, a private-broadcast test failure, and the release-schedule ticket itself. GitHub publishes no blocker ranking for the queue, so the raw count says more about unfinished scope than release risk.
Under the proposed schedule, source-language translation strings also freeze on Thursday. Maintainers then aim to split the 32.x branch and issue v32.0rc1 on Sept. 10, while new v33 work resumes on the master branch. The target for tagging v32.0 is Oct. 10.
The Bitcoin Core v32 freeze changes what can still enter the release. A feature pull request that misses Thursday moves beyond the normal v32 route, while qualifying fixes can still be reviewed during the run to rc1. An open milestone entry can represent release administration, a bug that remains eligible after the freeze, or unfinished feature code facing Thursday’s cutoff.
Two open changes already show integration friction. A proposal to let operators reject unencrypted v1 outbound clearnet connections and a change to limit simultaneous HTTP clients both carry a “Needs rebase” label. That label means the patches no longer apply cleanly, leaving their priority and eventual inclusion unresolved.
Wallet-related work carries a direct compatibility consequence. An open descriptor-wallet fix proposes preserving access to existing Miniscript wallets when a recomputed descriptor identifier differs from the stored record, following a reported upgrade-related load failure. A separate Aug. 12 report described a wallet error after an upgrade from v29.2 to v31.1. That single case establishes the reported failure, while its prevalence, cause, and release priority remain unknown.
The fee-estimation proposal would use mempool data only to lower the existing block-policy recommendation, aiming to reduce overpayment while retaining the estimator’s higher safety bound. Private-broadcast work focuses on controlling rebroadcast-related state growth; a separate v1 retry-test failure remains in the milestone.
Thursday will determine which feature changes clear the v32 gate and which continue toward v33. Bug fixes remain eligible during the release-candidate cycle. The schedule covers Bitcoin Core software packaging and testing; consensus-rule activation sits outside the documented v32 release plan.
