From 7b6221a5812e74caeadf088fdb7b848fcf27d8ff Mon Sep 17 00:00:00 2001 From: Owen Gunden Date: Fri, 10 Sep 2021 14:55:05 -0400 Subject: [PATCH] fix typo (#808) --- 10_onion_routing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10_onion_routing.asciidoc b/10_onion_routing.asciidoc index 3df10c7..558ebce 100644 --- a/10_onion_routing.asciidoc +++ b/10_onion_routing.asciidoc @@ -138,7 +138,7 @@ Alice will start building the hop data from the end of the path backwards: Dina, ===== Final node payload for Dina -Alice first builds the payload that will be delivered to Dina. Dina will not be constructing an "outgoing HTLC", because Dina is the final node and payment recipient. For this reason, the payload for Dina is different that all the others (uses all zeros for the `short_channel_id`), but only Dina will know this since it will be encrypted in the innermost layer of the onion. Essentially, this is the "secret letter to Dina" we saw in our physical envelope example. +Alice first builds the payload that will be delivered to Dina. Dina will not be constructing an "outgoing HTLC", because Dina is the final node and payment recipient. For this reason, the payload for Dina is different than all the others (uses all zeros for the `short_channel_id`), but only Dina will know this since it will be encrypted in the innermost layer of the onion. Essentially, this is the "secret letter to Dina" we saw in our physical envelope example. The hop payload for Dina must match the information in the invoice generated by Dina for Alice and will contain (at least) the following fields in Type-Lenth-Value (TLV) format: