● Continued discussion about noinput/anyprevout: this proposed sighash flag that would allow LN implementations to use eltoo was discussed again on the Bitcoin-dev and Lightning-dev mailing lists. After summarizing previous discussions, Christian Decker asked several questions: is the idea behind the proposal useful? (Respondents seemed to agree that it was.) Do people want mandatory chaperon signatures? (Respondents seemed moderately opposed.) Do people want mandatory output tagging? (Respondents seemed opposed, some strongly.)

In response to the question about output tagging, C-Lightning contributor ZmnSCPxj proposed an alternative tagging mechanism that would put the tag inside the taproot commitment, making it invisible unless a script-path spend was used. This could allow a spender who was worried about noinput to ensure they didn’t pay noinput-compatible scripts—the original goal behind output tagging—but without the decrease in privacy and fungibility created by output tagging. Several people seemed to express interest in this idea, although it wasn’t clear whether they wanted to see it as part of a proposal or they just preferred it to external output tagging (which, as noted above, was generally opposed by respondents).