From 76761b818c4f123e3412f2f8d2313a34476e605a Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Tue, 3 Oct 2017 12:11:29 +1030 Subject: [PATCH] Typo fix: CTLV -> CLTV. Locktime, not timelock. Found this in my code, too, so pretty sure it's my fault! Signed-off-by: Rusty Russell --- .aspell.en.pws | 3 +-- 04-onion-routing.md | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/.aspell.en.pws b/.aspell.en.pws index eca11b172..845bb7ee9 100644 --- a/.aspell.en.pws +++ b/.aspell.en.pws @@ -245,7 +245,6 @@ Poy talkin Freenode revocationkey -ctlv msat func unencrypted @@ -305,4 +304,4 @@ AAAA SRV TTL URI -cli \ No newline at end of file +cli diff --git a/04-onion-routing.md b/04-onion-routing.md index a4cee05fe..a13b1689e 100644 --- a/04-onion-routing.md +++ b/04-onion-routing.md @@ -553,7 +553,7 @@ outgoing channel: * [`2`:`len`] * [`len`:`channel_update`] -If the ctlv-expiry is too near, we tell them the the current channel +If the cltv-expiry is too near, we tell them the the current channel setting for the outgoing channel: 1. type: UPDATE|14 (`expiry_too_soon`) @@ -591,7 +591,7 @@ If the `cltv_expiry` is too low, the final node MUST fail the HTLC: 1. type: 17 (`final_expiry_too_soon`) -If the `outgoing_cltv_value` does not match the `ctlv_expiry` of the +If the `outgoing_cltv_value` does not match the `cltv_expiry` of the HTLC at the final hop: 1. type: 18 (`final_incorrect_cltv_expiry`)