Author: CJP 2016-02-09 19:48:59
Published on: 2016-02-09T19:48:59+00:00
In a post by Rusty Russell, he clarifies that all outputs to A in A's commit transaction must be delayed via OP_CSV, including HTLC outputs. The "HTLC Receiver Redeemscript" is structured as R-VALUE & OP_CSV & SIG-PAYEE OR HTLC-TIMEOUT & SIG-PAYER OR REVOCATION-B & SIG A. Rusty then goes on to explain a hypothetical scenario involving Alice and Eve where Eve becomes unresponsive on one channel after sending the R value to Alice on both channels. Alice has to broadcast her commit transaction containing the HTLC before the CLTV of the HTLC times out. It is crucial for Alice's CSV delay to be set at less than a day to ensure that she can claim the HTLC funds. However, this means that Alice's node must be up and running and connected to the Bitcoin network within 0.5 days remaining in the time window. Rusty suggests longer delays are better to catch the use of revoked commit transactions, while shorter HTLC timeout increments are better to lock up funds for shorter periods. This is important since systems can fail, and manual intervention may be needed to restore them, thus avoiding downtime/DoS attack -> theft escalation.
Updated on: 2023-05-23T18:22:04.906413+00:00