Bitcoin Core Feature Freeze Nears as Rebase Conflicts Stall Unencrypted Connection Proposal

Bitcoin Core maintainers will close the merge window for the 29.x release series on Thursday, locking in the feature set that will ship to node operators worldwide. The freeze marks the transition from active development to stabilization, and this cycle the queue carries an unusual bottleneck: a rebase conflict on the most visible networking proposal in years.

The unencrypted connection proposal — formally a BIP-324 implementation that would allow v2 P2P transport without encryption — has accumulated merge conflicts against upstream changes in the net processing layer. Maintainers noted in the project's pull-request tracker that the conflicts touch peer-handling logic altered by separate refactors landed since the proposal was first opened. Resolving them requires rebasing across three moving targets, and the clock is now measured in days.

What triggered the move The feature freeze is a scheduled milestone, not an emergency. Every major release follows the same cadence: a merge window opens after the prior release branches, maintainers triage pull requests for consensus impact, and the freeze date is published weeks in advance. This cycle the window opened in late May. The unencrypted transport proposal entered review in early June but stalled when net-processing refactors rewrote the same code paths it modifies.

What the order book shows The proposal's author submitted a partial rebase last week that resolved two of three conflict zones. The remaining zone involves the peer eviction logic, where a separate PR introduced a new scoring heuristic. Maintainers estimate a clean rebase and re-review would take at least five working days — pushing past Thursday's cutoff. No alternative path has been proposed.

What insiders are saying Core maintainer Pieter Wuille commented on the pull request that the proposal's design remains sound but the mechanical burden of rebasing against concurrent refactors has become the blocker. He emphasized that missing the freeze does not kill the proposal — it defers it to the 30.x cycle, which opens its merge window roughly six months later. The project's release manager, Michael Ford, confirmed the freeze date is firm and that no exceptions are planned for consensus-adjacent networking changes.

What the filing actually says The Bitcoin Core repository's release process document states that after feature freeze, only bug fixes, documentation updates, and non-consensus refactors may be merged. The unencrypted transport proposal modifies peer handshake logic, which the project classifies as consensus-adjacent because it changes how nodes negotiate protocol capabilities. That classification keeps it on the frozen side of the line.

Historical precedent for this pattern In the 27.x cycle, a similar rebase conflict on the addrman refactor delayed a peer-reputation improvement by one release. The 28.x cycle saw a mempool policy change miss the freeze after a late-stage design review surfaced edge cases. Both features shipped in the subsequent cycle without incident. The pattern suggests the unencrypted transport proposal will likely land in 30.x, barring a breakthrough rebase this week.

What it implies for supply pressure Node operators running 28.x will not receive v2 transport until they upgrade to 30.x, assuming the proposal merges then. Adoption curves for prior networking upgrades show 50% node uptake within three months of release. The delay does not affect consensus rules, block validation, or miner economics directly. It does extend the period during which a portion of the network remains on v1 handshake semantics, which leak peer metadata to passive observers.