mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-02-22 14:22:46 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 5: Homogenize Local/Remote Commitment

Browse source 
Make them look similar, choosing the best parts of each
This commit is contained in:
Orfeas Stefanos Thyfronitis Litos 2019-04-05 16:15:19 +01:00 • committed by Christian Decker
parent 7cb708da20
commit b9aa458852
1 changed files with 12 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
05-onchain.md
View file

@ -207,15 +207,15 @@ can be ignored.
## HTLC Output Handling: Local Commitment, Local Offers
Each HTLC output can only be spent by either a local offerer, by using the HTLC-timeout
transaction after it's timed out, or a remote recipient, if it has the payment
preimage.
Each HTLC output can only be spent by either the *local offerer*, by using the
HTLC-timeout transaction after it's timed out, or the *remote recipient*, if it
has the payment preimage.
There can be HTLCs which are not represented by an output: either
There can be HTLCs which are not represented by any outputs: either
because they were trimmed as dust, or because the transaction has only been
partially committed.
The HTLC has *timed out* once the depth of the latest block is equal to
The HTLC output has *timed out* once the depth of the latest block is equal to
or greater than the HTLC `cltv_expiry`.
### Requirements
@ -370,16 +370,17 @@ will be unable to salvage the HTLCs.
## HTLC Output Handling: Remote Commitment, Local Offers
Each HTLC output can only be spent by the *offerer*, after it's timed out, or by
the *recipient*, if it has the payment preimage.
Each HTLC output can only be spent by either the *local offerer*, after it's
timed out, or by the *remote recipient*, by using the HTLC-success transaction
if it has the payment preimage.
There can be HTLCs which are not represented by any outputs: either
because the outputs were trimmed as dust, or because the remote node has two
*valid* commitment transactions with differing HTLCs.
The HTLC output has *timed out* once the depth of the latest block is equal to
or greater than the HTLC `cltv_expiry`.
There can be HTLCs which are not represented by any outputs: either
because the outputs were trimmed as dust or because the remote node has two
*valid* commitment transactions with differing HTLCs.
### Requirements
A local node: