Bitcoin Developers Advance TCP Hole Punching and BIP-54 Testing

Bitcoin developers are testing new networking and consensus mechanisms, including TCP hole punching to expand home node reachability and an updated activation roadmap for the BIP-54 consensus cleanup soft fork, according to Bitcoin Optech Newsletter #430 ¹. At the time of writing, $BTC traded at $75,870, down 4.7% over the past 24 hours.

Work on TCP hole punching resumed after the default activation of NAT-PMP port mapping in Bitcoin Core 30.0 failed to make enough home nodes reachable, developer 0xB10C reported ¹. The technique allows two nodes behind routers to initiate simultaneous connections to bypass NAT restrictions, expanding the pool of reachable honest peers and making it harder for attackers to monopolize outbound connection slots ¹. However, developer Anthony Towns noted that an attacker broadcasting roughly 10,000 addresses could flood the mechanism, arguing that inbound connections might increase attack surfaces for home users ¹. Other proposals, including coordination via a node's internal Tor service or a listening-node message board, remain under review ¹.

BIP-54 Timeline and Covenants

On consensus rules, developer Antoine Riard posted that discussion continues over the BIP-54 consensus cleanup soft fork, with an activation timeline potentially realistic in the second half of 2027 if the developer community reaches consensus ¹. The proposal, previously discussed as a consensus cleanup soft fork, is undergoing testing in Bitcoin Core pull request #35793 on regtest, alongside cross-client interoperability checks in btcd ¹. A rule prohibiting witness-stripped transactions of exactly 64 bytes remains the primary disputed point, while updated proofs in Lean by Pieter Wuille established mathematical bounds on chain length under proposed timestamp limits ¹.

Concurrently, Luke Carriere introduced a draft specification on Delving Bitcoin to standardize spending policies enforced by co-signers emulating covenants ¹. The framework aims to unify interoperability across distinct protocols like blinded co-signers and Discreet Log Contract oracles by enforcing base rules onchain via taproot script while reserving co-signer policies for offchain conditions ¹. Separate prototypes for opt-in chain split replay protection using a new witness version annex were also published by Sjors Provoost ¹.