Bitcoin Core feature freeze nears as rebase issues hit unencrypted-connection proposal
Bitcoin Core, the highest software program consumer for working a Bitcoin node, is scheduled to enter its v32 feature freeze on Thursday, Aug. 20. The deadline shifts the discharge line to bug fixes and provides new v32 options their ultimate regular window earlier than the venture’s October launch goal.
The v32 milestone listed 17 objects open and 79 closed on Aug. 17, placing the work at 82% full. Those 17 entries span feature pull requests, bug experiences, construct and logging work, a private-broadcast take a look at failure, and the release-schedule ticket itself. GitHub publishes no blocker rating for the queue, so the uncooked rely says extra about unfinished scope than launch danger.
Under the proposed schedule, source-language translation strings additionally freeze on Thursday. Maintainers then goal to separate the 32.x department and situation v32.0rc1 on Sept. 10, whereas new v33 work resumes on the grasp department. The goal for tagging v32.0 is Oct. 10.
The Bitcoin Core v32 freeze modifications what can nonetheless enter the discharge. A feature pull request that misses Thursday strikes past the traditional v32 route, whereas qualifying fixes can nonetheless be reviewed in the course of the run to rc1. An open milestone entry can symbolize launch administration, a bug that continues to be eligible after the freeze, or unfinished feature code dealing with Thursday’s cutoff.
Two open modifications already present integration friction. A proposal to let operators reject unencrypted v1 outbound clearnet connections and a change to limit simultaneous HTTP clients each carry a “Needs rebase” label. That label means the patches now not apply cleanly, leaving their precedence and eventual inclusion unresolved.
Wallet-related work carries a direct compatibility consequence. An open descriptor-wallet fix proposes preserving entry to present Miniscript wallets when a recomputed descriptor identifier differs from the saved report, following a reported upgrade-related load failure. A separate Aug. 12 report described a pockets error after an improve from v29.2 to v31.1. That single case establishes the reported failure, whereas its prevalence, trigger, and launch precedence stay unknown.
The fee-estimation proposal would use mempool information solely to lower the existing block-policy recommendation, aiming to scale back overpayment whereas retaining the estimator’s larger security certain. Private-broadcast work focuses on controlling rebroadcast-related state growth; a separate v1 retry-test failure stays within the milestone.
Thursday will decide which feature modifications clear the v32 gate and which proceed towards v33. Bug fixes stay eligible in the course of the release-candidate cycle. The schedule covers Bitcoin Core software program packaging and testing; consensus-rule activation sits outdoors the documented v32 launch plan.
The publish Bitcoin Core feature freeze nears as rebase issues hit unencrypted-connection proposal appeared first on CryptoSlate.
