● Breaking the link between UTXOs and unannounced channels: Bastien Teinturier posted to the Lightning-Dev mailing list about changing what data is added to a BOLT11 invoice for payments sent to unannounced channels—channels that aren’t advertised to the LN network and which usually don’t route payments for other users. The proposed change would remove information from an invoice that could be used to identify the channel’s deposit UTXO, replacing it with a one-time per-invoice keypair and a secret that’s derived from the keypair and routed as part of the onion-encrypted payment. This would require special support from both the spender and the peer who’s able to route to the unannounced channel, but other nodes along the routing path would not need to change their implementation. Teinturier requested feedback on the proposal, including any suggestions for how to eliminate the need to include an encrypted secret in the payment.

● Layered commitments with eltoo: Anthony Towns described a potential modification to his previous anyprevout proposal (a variation of SIGHASH_NOINPUT) that could simplify eltoo-based LN channels. As currently proposed, eltoo-based LN implementations would need to ensure they don’t accept a payment whose refund timeout occurs before the payment’s unilateral-close delay, otherwise a paying node will be able to reclaim its payment before the receiving node has a chance to use its adaptor signature (“point lock”) to legitimately claim the payment. This differs from current-style LN payments where the timeout and the delay may be chosen independently.