Contents
TCP hole punching for home nodes
0xB10C resumed work on an experimental specification and implementation for TCP hole punching in Bitcoin Core 2. Most home nodes only make outbound network connections 2. Bitcoin Core version 30.0 enabled NAT-PMP port mapping by default, but the change did not make as many nodes reachable as developers expected 2. TCP hole punching allows two home nodes behind routers to initiate connections simultaneously so each router permits incoming traffic 2. This method serves as a best-effort supplement to traditional port forwarding 2. 0xB10C evaluated four existing designs before proposing a new approach that operates without a central coordinator 2. Under this design, a node broadcasts its reachable address and a temporary public key using a new addr v2 format 2. Peer pairs derive matching candidate connection lists and execution times from a shared secret combined with data from each new block 2.
Anthony Towns stated that an attacker advertising roughly 10,000 addresses could match honest nodes early 2. Towns suggested that nodes should instead establish short-lived connections to random peers to reduce risks 2. Towns also asked whether recent TCP and protocol flaws mean home users are safer when they refuse inbound connections entirely 2. Jonathan Harvey-Buschel noted data showing honest nodes are less reachable than attacker-controlled nodes 2.
Standardized spending policies for co-signers
Luke Carriere published a proposal on Delving Bitcoin to standardize spending policies for co-signers that emulate covenants 2. Existing designs, such as blinded co-signers or chain code delegation, use proprietary spending policies 2. This lack of standard rules prevents wallets built for one protocol from using co-signers or oracles built for another 2. Carriere declined to request a BIP number for his draft, asking if this layer is appropriate for standardization 2. Policies must leave script to enforce anything script can handle, restricting co-signer rules to logic script cannot execute 2. Wallets must preserve at least one spending path that does not depend on a co-signer 2. Co-signers must accept oracle attestations formatted under DLC specifications so existing oracles operate without modifications 2.
A complete policy consists of five components 2. The output defines the taproot descriptor for the underlying funds 2. The co-signer group specifies participating signers and the required signature threshold 2. Templates specify permitted transactions with exact output structures 2. Conditions define pre-requisites that must be true before a template receives a signature 2. Profiles declare verification modes, evidence formats, and accountability mechanisms 2. PREDGE noted that the statement-v0 evidence profile lacks a finality flag 2. Without a finality flag, a co-signer might execute on a provisional attestation that gets modified later 2. Tehiyadu noted that policy hashes must commit to exact verifier semantics to prevent implementations from interpreting identical bytes differently 2. Carriere confirmed he would add a finality flag and specify verifier rules 2.
BIP54 consensus cleanup and time warp fix
Antoine Riard posted an update on the consensus cleanup soft fork known as BIP54 2. The rule forbidding transactions with a witness-stripped size of exactly 64 bytes remains the most contested proposal 2. Developers are reviewing pull request #35793 in Bitcoin Core, which implements BIP54 rules on regtest without mainnet activation 2. Riard stated that developers could realistically discuss activation in the second half of 2027 if the community achieves consensus by that time 2. Riard also evaluated how fixing the time warp bug affects future consensus changes 2. Fixing the time warp bug limits timestamp manipulation rather than removing it entirely 2.
A forward blocks proposal using the remaining 7,200-second window could lower difficulty by roughly 0.60% per retarget period 2. This window would increase the block production rate by about 0.60%, which falls far short of original expansion goals 2. Riard stated that forward blocks are unsound because validators must process transactions twice for single transaction fees 2. Unupgraded nodes would also have to download the additional data 2. Riard plans to submit a short footnote to BIP54 detailing these points 2.
Post-quantum transition proposals and BIP300 censorship
James Tagg published five draft BIPs for Quantum Secure Asset Verification and Escrow, known as QSAVE 2. QSAVE offers a post-quantum migration framework that does not burn unmigrated funds 2. Once activated as a soft fork, any input not listed on a post-quantum registry is marked as unmigrated 2. Unmigrated inputs must satisfy their original locking script and provide a second factor 2. The second factor can be a zero-knowledge proof or a post-quantum binding committed before a designated cutoff 2. If an unmigrated input lacks the second factor, all spendable outputs must be directed to recovery outputs 2. Recovery outputs can be held by decentralized custodians operating an offchain recovery process 2. The proposed process permits custodial funds to earn a conservative 0.5% return allocated to charity 2.
Separately, bitKingAE proposed a proof-of-decay mechanism to shrink post-quantum exposed outputs like early P2PK coins 2. Under that proposal, output balances decay on a set schedule every 50,000 blocks after a grace period ends 2. Vinicius Cestari objected that quantum attackers could wait until grace periods end to drain outputs before decay occurs 2. In another discussion, Ori Newman analyzed drivechains withdrawal safety under BIP300 2. Newman showed that a miner with 26% of total hashrate can censor withdrawal bundles indefinitely by broadcasting ALARM messages 2. An attacker with 26% of hashrate lowers bundle scores, leaving them at an expected score of 12,624 after 26,300 blocks 2. That total fails to reach the 13,150 score needed for bundle approval 2. Newman suggested removing downvote options to restore a 51% honest majority requirement 2.
What is not yet established
- Whether TCP hole punching will be integrated into a future release of Bitcoin Core
- Whether serialization for co-signer spending policies will use JSON or TLV format
- Whether BIP54 will achieve community consensus for mainnet activation by 2027
Frequently asked questions
How does TCP hole punching assist home Bitcoin nodes?
It allows two nodes behind routers to connect simultaneously so routers permit incoming traffic, increasing reachable honest peers 2.
What threshold of hashrate can censor BIP300 withdrawal bundles?
A miner controlling 26% of hashrate can indefinitely censor a withdrawal bundle by broadcasting ALARM downvotes in every mined block 2.
Sources
- Bitcoin Optech — Bitcoin Optech Newsletter #430 Recap Podcast (2026-11-10) https://bitcoinops.org/en/podcast/2026/11/10
- Bitcoin Optech — Bitcoin Optech Newsletter #430 (2026-11-06) https://bitcoinops.org/en/newsletters/2026/11/06
Revision history
Published