Author: ZmnSCPxj 2019-03-20 08:07:00
Published on: 2019-03-20T08:07:00+00:00
In the Lightning-dev mailing list, ZmnSCPxj raised a question regarding the proposal of "must have a non-SIGHASH_NOINPUT" rule. He asked how it would work with watchtowers and said that as he understood it, the current plan for eltoo watchtowers would be to store both `SIGHASH_NOINPUT` signatures from both sides in the blob sent to the watchtower. He further questioned, if one of the signatures MUST be non-`SIGHASH_NOINPUT`, how does the watchtower create such a non-`SIGHASH_NOINPUT` signature? Rusty Russell replied stating that future segwit versions may choose to relax the rule. ZmnSCPxj suggested that "the must have a sig that commits to the input tx" seems like it should be pretty safe, not too expensive, and keeps taproot's privacy benefits in the cases where we end up needing to use NOINPUT.
Updated on: 2023-06-13T17:41:34.185125+00:00