Bitcoin Core feature freeze nears as rebase issues hit unencrypted-connection proposal

The queue mixes feature proposals, bugs and release administration, so the count alone does not identify what could delay October.

Bitcoin Core v32 shown as a locked release gate surrounded by 17 open issues, an Aug. 20 deadline, and remaining feature categories.
Image by CryptoSlate
2 min read

Quick Take

  1. The Aug. 20 freeze moves new v32 features out of the normal window; bug fixes can still be reviewed toward rc1.
  2. The 17 open items span features, bugs, build work, testing, and release administration—not a blocker ranking.
  3. Two open changes need a rebase; a descriptor-wallet fix targets access issues after an identifier mismatch.

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.

Why developers are calling latest Bitcoin code “malware”
Related Reading

Why developers are calling latest Bitcoin code “malware”

Bitcoin Core’s v30 update widens on-chain data use, splitting the community over innovation vs. bloat.
Oct 13, 2025 · Oluwapelumi Adejumo

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.

Bitcoin Core v32 timeline showing 17 open and 79 closed milestone items, an Aug. 20 feature freeze, Sept. 10 branch and release candidate target, and Oct. 10 tag aim

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.

CryptoSlate Daily Brief

Daily signals, zero noise.

Market-moving headlines and context delivered every morning in one tight read.

5-minute digest 100k+ readers

Free. No spam. Unsubscribe any time.

You’re subscribed. Welcome aboard.

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.

Who decides what's in the next Bitcoin block without MEV?
Related Reading

Who decides what's in the next Bitcoin block without MEV?

Bitcoin MEV, the quiet kind: how miners pick winners in your mempool.
Nov 10, 2025 · Liam 'Akiba' Wright

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.

This “quantum-safe” Bitcoin idea removes Taproot’s key-path — and raises fees on purpose
Related Reading

This “quantum-safe” Bitcoin idea removes Taproot’s key-path — and raises fees on purpose

If it ever activates, it’s opt-in and slow, because Bitcoin’s real constraint is coordination, not cryptography.
Feb 13, 2026 · Gino Matos
$64,056.50 +1.23% 24 hour change
1H +0.09% 24H +1.23% 7D -0.01%
30D -0.10% 60D +2.38% 90D -16.43%

Bitcoin is +1.23% over the past 24 hours and currently sits at rank #1 by market cap.

Market cap $1.29T
Volume (24h) $18.09B +113.10%
Circ. supply 20.07M
FDV $1.35T
Crypto Market Summary

Where the broader market sits right now

Right now, the total crypto market is valued at $2.19T with $47.13B in 24-hour volume. Bitcoin dominance sits at 58.66%. Explore the market

Global market cap $2.19T
24H market volume $47.13B
Bitcoin dominance 58.66%