From 91d96e13c1a5437b711bd9e386a50b256b7859b9 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 18:35:54 +0000 Subject: [PATCH] Edited ch14_applications.adoc with Atlas code editor --- ch14_applications.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch14_applications.adoc b/ch14_applications.adoc index e0f852a7..dbf469f5 100644 --- a/ch14_applications.adoc +++ b/ch14_applications.adoc @@ -1103,7 +1103,7 @@ refund if the channel was closed or the routed payment((("payment channels", "Li ==== Lightning Network Transport and Pathfinding -All communications +All ((("payment channels", "Lightning Network", "pathfinding", id="payment-channel-ln-path")))((("Lightning Network", "pathfinding", id="lightning-path")))((("pathfinding in Lightning Network", id="path-lightning")))communications between LN nodes are encrypted point-to-point. In addition, nodes have a long-term public key that they use as an identifier and to authenticate each other. @@ -1187,7 +1187,7 @@ Doesn't it get shorter, allowing them to deduce the path size and their position? To prevent this, the packet size is fixed and padded with random data. Each node sees the next hop and a fixed-length encrypted message to forward. Only the final recipient sees that there -is no next hop. To everyone else it seems as if there are always more +is no next hop. To everyone else it seems as if there are always ((("payment channels", "Lightning Network", "pathfinding", startref="payment-channel-ln-path")))((("Lightning Network", "pathfinding", startref="lightning-path")))((("pathfinding in Lightning Network", startref="path-lightning")))more hops to go. ==== Lightning Network Benefits