mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 5: require to fail incoming HTLCs if HTLCs time out on chain.

Browse Source 
We talked about this below in the Rationale:

    The fulfillment of an on-chain HTLC delivers the `payment_preimage`
    required to fulfill the incoming HTLC...
    Otherwise, it needs to send the `update_fail_htlc` (presumably with
    reason `permanent_channel_failure`) as detailed in [BOLT
    02](https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md#forwarding-htlcs).

But we didn't actually *say* you MUST fail incoming HTLCs after reasonable
depth!

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2017-09-22 15:31:32 +09:30
parent 465a4cddaf
commit fc9900c101
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
05-onchain.md
View File

@ -227,7 +227,9 @@ the payment preimage from the transaction input witness.
If the HTLC output has *timed out* and not been *resolved*, the node
MUST *resolve* the output. If the transaction is the node's own
MUST *resolve* the output and MUST fail the corresponding incoming
HTLC (if any) once the resolving transaction has reached reasonable
depth. If the transaction is the node's own
commitment transaction, it MUST *resolve* the output by spending it
using the HTLC-timeout transaction, and the HTLC-timeout
transaction output MUST be *resolved* as described in "On-chain HTLC