Edited 03_how_ln_works.asciidoc with Atlas code editor

3 years ago · 3510499781
parent 7f8d7d497b
commit 3510499781
1 changed files with 1 additions and 1 deletions
--- a/03_how_ln_works.asciidoc
+++ b/03_how_ln_works.asciidoc
@ -697,7 +697,7 @@ Finally, when the channel is closed, a transaction is made on the Bitcoin networ

 On the Lightning Network, a user can only send as much bitcoin as currently exists on their side of a particular channel to a channel partner. For instance, if a user owns one channel with 0.4 BTC on their side, and another channel with 0.2 BTC on their side, then the maximum they can send with one payment is 0.4 BTC. This is true regardless of how much bitcoin the user currently has in their Bitcoin wallet.

-((("multipart payments (MPP)")))Multipart payments (MPP) is a feature which, in the preceding example, allows the user to combine both their 0.4 BTC and 0.2 BTC channels to send a maximum of 0.6 BTC with one payment. AMPs are currently being tested across the Lightning Network and are expected to be widely available and used by the time this book is completed. For more detail on MPP, see <<mpp>>.
+((("multipart payments (MPP)")))Multipart payments (MPP) is a feature which, in the preceding example, allows the user to combine both their 0.4 BTC and 0.2 BTC channels to send a maximum of 0.6 BTC with one payment. MPPs are currently being tested across the Lightning Network and are expected to be widely available and used by the time this book is completed. For more detail on MPP, see <<mpp>>.

 If the payment is routed, every routing node along the routing path must have channels with capacity at least the same as the payment amount being routed. This must hold true for every single channel that the payment is routed through. The capacity of the lowest-capacity channel in a path sets the upper limit for the capacity of the entire path.