lightning-dev

Combined summary - BOLT #3: Shouldn't timeout be included in the script of "Offered HTLC Outputs" for the local node?

Combined summary - BOLT #3: Shouldn't timeout be included in the script of "Offered HTLC Outputs" for the local node?

In this email thread, Ugam Kamat seeks clarification on the BOLT #3 protocol for Lightning Network.

He expresses confusion about whether the timeout should be included in the script of "Offered HTLC Outputs" for the local node. Pierre responds that the HTLC-Timeout transaction is timelocked with locktime=cltv_expiry. Nadav also joins the discussion and shares a pull request he opened to clarify this issue. Ugam, still unsure, explains his thought process involving offering the HTLC output, signing the commitment transactions, broadcasting them to the main chain, and spending the third output using 0 0 in the witness stack. According to Ugam's understanding, this would send the outputs to the P2WSH with to_self_delay. Pierre reiterates that the HTLC-Timeout transaction is indeed timelocked with locktime=cltv_expiry. Ugam realizes his mistake and apologizes for his misunderstanding. He thanks Pierre and Nadav for their help and clarification on the matter.This email exchange highlights the complexity of the Lightning Network protocol and emphasizes the importance of clear communication and collaboration among developers. It also showcases the collaborative nature of the lightning-dev mailing list, where developers can seek and provide assistance to ensure a better understanding of the protocol.

Discussion History

0
Ugam KamatOriginal Post
June 5, 2019 15:51 UTC
1
June 5, 2019 16:05 UTC
2
June 5, 2019 16:30 UTC
3
June 5, 2019 16:32 UTC
4
June 5, 2019 16:37 UTC
5
June 5, 2019 16:45 UTC