Optech #430: hole punching for home nodes is disputed, a draft standardises co-signer policies
Bitcoin Optech's newsletter #430, published on 6 November, leads with a continued discussion about TCP hole punching, a way to let Bitcoin nodes behind home routers accept connections. Home nodes usually only connect outwards, and the newsletter notes that turning on NAT-PMP port mapping by default in Bitcoin Core 30.0 did not make many more of them reachable. With hole punching, two home nodes open connections to each other at the same moment so that each router lets the other's traffic in.
The proposal under discussion needs no coordinator: a node announces a punchable address and a temporary public key in a new addr v2 type, and pairs of nodes derive candidates and timing from a shared secret and each new block. Anthony Towns objected that an attacker could flood the scheme, estimated that one advertising about 10,000 addresses would be an early match for most honest nodes, and asked whether recent TCP and protocol vulnerabilities make refusing inbound connections the safer default for home users. Jonathan Harvey-Buschel cited data that honest nodes are less reachable than attacker-controlled ones and preferred coordination through a node's own Tor service. The discussion is ongoing.
The second item is a draft BIP by Luke Carriere to standardise the spending policies enforced by co-signers that emulate covenants, so that a wallet built for one design can use a co-signer or oracle built for another. Its principles: whatever script can enforce stays in script, a spending path without any co-signer must always exist, and co-signers accept oracle attestations in the DLC format. Reviewers asked for a finality flag on one evidence profile and for the policy hash to commit to exact verifier semantics, and Carriere agreed. In the consensus section, Antoine Riard wrote that the 64-byte transaction rule remains the most contested part of the BIP54 cleanup soft fork and, speaking for himself, that activation could realistically be considered in the second half of 2027 if the community agrees.

What it means
Both main items are about trust boundaries: who a home node ends up talking to, and how much a co-signer is allowed to decide. The always-available path without a co-signer is the line that keeps the second one from becoming custody.