The Frontier

Pais proposes a standard for QR-based signing payloads to improve air-gapped workflows for Miniscript wallets, addressing issues like multi-wallet support on a single device and descriptor selection during PSBT signing.

Adi Man's MCCV proof-of-concept uses only CTV or Template Hash to build a reactive vault, where pre-computed transaction trees let users claw back funds if hot keys are compromised, trading script complexity for security.

The MCCV design requires duplicating the vault's state machine to avoid cycles in CTV, making computation intensive; a vault supporting a million operations can take tens of minutes to pre-compute.

Adi Man suggests CheckSigFromStack could enable cyclical state machines in vaults without massive pre-computation, reducing states from millions to hundreds, but introduces concerns about deleted keys and key reuse.

Roastbeef proposes upgrading BIP324's encrypted transport with post-quantum MLKEM, debating hybrid versus pure PQ key exchange and methods to maintain traffic indistinguishability from random bytes.

Murch argues PQ upgrades for peer-to-peer traffic like BIP324 are easier than on-chain consensus changes, as they are not space-constrained and allow new protocol versions, though man-in-the-middle attacks remain a simpler threat than decrypting.

Roastbeef outlines a post-quantum Lightning design requiring multiple cryptographic primitives - MLKEM for transport, MLDSA for off-chain signatures, SLHDSA for on-chain scripts - since no single PQ solution replaces ECC's multifunctional node key.

A routing node with 1,000 channels updating every 10 minutes would exhaust SLHDSA-128-24's 16 million signature limit in about four months, highlighting a key reuse constraint for post-quantum Lightning.

Jeremy Rubin argues BIP54's ban on 64-byte stripped transactions blocks future use cases like time-locked miner donations, pay-to-anchor outputs, transaction sponsorship, and post-quantum key reuse schemes.

AJ counters that proposed 64-byte use cases can be padded with an OP_NOP to become 65 bytes, avoiding the ban, and many are economically equivalent to anyone-can-spend outputs.

Core Lightning v26.06 deprecates the Pay plugin in favor of XPay, which uses the AskRené plugin and minimum cost flow algorithms for improved multipath payment routing, and adds a payer proof implementation for Bolt 12 offers.

A Bitcoin Core fix prevents session ID collisions when running 'walletprocesspsbt' twice for Musig2 nonce generation, now incorporating the public nonce hash into the session ID to allow retries without failure.

Bitcoin Core now allows migration of pre-2011 legacy wallets that lack a best block locator record, requiring a full chain rescan to find relevant transactions.

LND removes support for creating Tor v2 onion services, which have been obsolete since October 2021, though it retains ability to verify and rebroadcast old peer announcements containing such addresses.

A RustBitcoin fix enforces that a block's coinbase input must contain the 32-byte witness reserved value if the coinbase output includes a witness commitment, even if the block has no SegWit transactions.