mirror of
https://github.com/lightning/bolts.git
synced 2025-02-23 14:40:41 +01:00
BOLT 7: there's no htlc_expiry, it's called cltv_expiry.
Closes: #325 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
parent
1cb19fab70
commit
8618c8a74e
1 changed files with 1 additions and 1 deletions
|
@ -315,7 +315,7 @@ of *relaying* payments, not *sending* payments. When making a payment
|
|||
`B` -> `C` (announced by `B`) and `C` -> `D` (announced by `C`) will
|
||||
come into play. When building the route, amounts and expiries for HTLCs need
|
||||
to be calculated backward from the destination to the source. The initial
|
||||
exact value for `amount_msat` and minimal value for `htlc_expiry`, which are
|
||||
exact value for `amount_msat` and minimal value for `cltv_expiry`, which are
|
||||
to be used for the last HTLC in the route, are provided in the payment request
|
||||
(see [BOLT #11](11-payment-encoding.md#tagged-fields)).
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue