mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-22 16:18:11 +00:00
Edited ch14_applications.adoc with Atlas code editor
This commit is contained in:
parent
3b55e7a0d5
commit
91d96e13c1
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user