From eaed136c67c732996c3b2c7a78bbbe54301f40df Mon Sep 17 00:00:00 2001 From: Javier Vargas Date: Mon, 20 Jul 2020 22:02:15 +0200 Subject: [PATCH] Update 13_4_Paying_a_Invoice.md --- 13_4_Paying_a_Invoice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13_4_Paying_a_Invoice.md b/13_4_Paying_a_Invoice.md index e4d398c..8312793 100644 --- a/13_4_Paying_a_Invoice.md +++ b/13_4_Paying_a_Invoice.md @@ -6,7 +6,7 @@ Almost all payments made on the Lightning Network require an invoice, which is nothing more than a request for payment made by the recipient of the money and sent by different means to the user who will pay. The format for a Lightning invoice uses bech32 encoding, which is already used for Bitcoin Segregated Witness and all payment requests are single use. -Invoices have two parts: +An invoice is made up of two parts, one is human readable and other is - Human readable part: `ln` + (`lnbc` for Bitcoin mainnet, `lntb` for Bitcoin testnet, and `lnbcrt` for Bitcoin regtest) + data amount