flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-07 16:06:26 +00:00
Code Issues Releases Wiki Activity

further edits

Browse Source
This commit is contained in:
Shannon Appelcline 2020-10-14 09:38:15 -10:00 committed by GitHub
parent 4ec7631dea
commit 8cb60b7999
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
19_1_Generate_a_Payment_Request.md
View File

@ -3,15 +3,15 @@
> :information_source: **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
This section describes how payments work on the Lightning Network, and how to create a payment request, or _invoice_. It depends on your having a second Lightning node, as described in [Accessing a Second Lightning Node](18_2__Interlude_Accessing_a_Second_Lightning_Node.md). These examples will use an LND node as its secondary node, to further demonstrate the possibilities of the Lightning Network. To differentiate between the nodes in these examples, the prompts will be shown as `c$` for the c-lightning node and `lnd$` as the LND node. If you want to reproduce this steps you should [install your own secondary LND node](18_2__Interlude_Accessing_a_Second_Lightning_Node.md#creating-a-new-lnd-node).
This section describes how payments work on the Lightning Network, how to create a payment request, or _invoice_, and finally how to make sense of it. Issuing invoices depends on your having a second Lightning node, as described in [Accessing a Second Lightning Node](18_2__Interlude_Accessing_a_Second_Lightning_Node.md). These examples will use an LND node as its secondary node, to further demonstrate the possibilities of the Lightning Network. To differentiate between the nodes in these examples, the prompts will be shown as `c$` for the c-lightning node and `lnd$` as the LND node. If you want to reproduce this steps, you should [install your own secondary LND node](18_2__Interlude_Accessing_a_Second_Lightning_Node.md#creating-a-new-lnd-node).
> :book: ***What is an Invoice?** 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 variety of means to the paying user. All payment requests are single use. Lightning invoices use bech32 encoding, which is already used by Segregated Witness for Bitcoin.
## Creating an Invoice
To create a new invoice on c-lightning you should use the `lightning-cli --network=testnet invoice` command.
To create a new invoice on c-lightning you would use the `lightning-cli --network=testnet invoice` command.
Here's how it would work with c-lightning, using arguments of an amount (in msatoshis), a label, and a description.
Here's how it would work with c-lightning, using arguments of an amount (in millisatoshis), a label, and a description.
```
c$ lightning-cli --network=testnet invoice 100000 joe-payment "The money you owe me for dinner"
{
@ -22,7 +22,7 @@ c$ lightning-cli --network=testnet invoice 100000 joe-payment "The money you owe
"warning_mpp_capacity": "The total incoming capacity is still insufficient even if the payer had MPP capability."
}
```
However, for this example we're going to instead generate an invoice on an LND node, and then pay it on the c-lightning node. This requires the slightly different `addinvoice` commend. You can use `--amt` argument to indicate amount to be payed and add a description using the `--memo` argument.
However, for this example we're going to instead generate an invoice on an LND node, and then pay it on the c-lightning node. This requires LND's slightly different `addinvoice` commend. You can use `--amt` argument to indicate amount to be paid and add a description using the `--memo` argument.
```
lnd$ lncli -n testnet addinvoice --amt 10000 --memo "First LN Payment - Learning Bitcoin and Lightning from the Command line."
@ -32,12 +32,14 @@ lnd$ lncli -n testnet addinvoice --amt 10000 --memo "First LN Payment - Learning
"add_index": "1"
}
```
Note that these invoices don't directly reference the channel you create: it's necessary for paying, but not for requesting payment.
Note that these invoices don't directly reference the channel you create: that's necessary for paying, but not for requesting payment. (In fact, you'd often create a channel following the receipt of an invoice, because as you'll see, it contains the node ID.)
## Detailing an Invoice
## Understanding an Invoice
The `bolt11` `payment_request` that you created is made up of two parts: one is human readable and the other is data.
> :book: **What is a BOLT?** The BOLTs are the individual [specifications for the Lightning Network](https://github.com/lightningnetwork/lightning-rfc).
### Reading the Human-Readable Invoice Part
The human readable part of your invoices starts with an `ln`. It is `lnbc` for Bitcoin mainnet, `lntb` for Bitcoin testnet, or `lnbcrt` for Bitcoin regtest).
@ -49,7 +51,7 @@ lntb100u1p0cwnqtpp5djkdahy4hz0wc909y39ap9tm3rq2kk9320hw2jtntwv4x39uz6asdr5ge5hyu
```
The human readable part is `ln+tb+100u`.
`lntb` says that this is a Lightning Network invoice on Testnet.
`lntb` says that this is a Lightning Network invoice for Testnet bitcoins.
`1m` says that it is for 100 bitcoin times the microsatoshi multiplier. There are four (optional) funds multipliers:
@ -62,7 +64,7 @@ The human readable part is `ln+tb+100u`.
### Reading the Data Invoice Part
The rest of the invoice (`1p0cwnqtpp5djkdahy4hz0wc909y39ap9tm3rq2kk9320hw2jtntwv4x39uz6asdr5ge5hyum5ypxyugzsv9uk6etwwssz6gzvv4shymnfdenjqsnfw33k76twypskuepqf35kw6r5de5kueeqveex7mfqw35x2gzrdakk6ctwvssxc6twv5hqcqzpgsp5a9ryqw7t23myn9psd36ra5alzvp6lzhxua58609teslwqmdljpxs9qy9qsq9ee7h500jazef6c306psr0ncru469zgyr2m2h32c6ser28vrvh5j4q23c073xsvmjwgv9wtk2q7j6pj09fn53v2vkrdkgsjv7njh9aqqtjn3vd`) contains a timestamp, specifically tagged data, and a signature. You obviously can't read it yourself, but you can ask `lightning-cli` to do so with the `decodepay` command on c-lightning:
The rest of the invoice (`1p0cwnqtpp5djkdahy4hz0wc909y39ap9tm3rq2kk9320hw2jtntwv4x39uz6asdr5ge5hyum5ypxyugzsv9uk6etwwssz6gzvv4shymnfdenjqsnfw33k76twypskuepqf35kw6r5de5kueeqveex7mfqw35x2gzrdakk6ctwvssxc6twv5hqcqzpgsp5a9ryqw7t23myn9psd36ra5alzvp6lzhxua58609teslwqmdljpxs9qy9qsq9ee7h500jazef6c306psr0ncru469zgyr2m2h32c6ser28vrvh5j4q23c073xsvmjwgv9wtk2q7j6pj09fn53v2vkrdkgsjv7njh9aqqtjn3vd`) contains a timestamp, specifically tagged data, and a signature. You obviously can't read it yourself, but you can ask c-lightning's `lightning-cli` to do so with the `decodepay` command:
```
c$ lightning-cli --network=testnet decodepay lntb100u1p0cwnqtpp5djkdahy4hz0wc909y39ap9tm3rq2kk9320hw2jtntwv4x39uz6asdr5ge5hyum5ypxyugzsv9uk6etwwssz6gzvv4shymnfdenjqsnfw33k76twypskuepqf35kw6r5de5kueeqveex7mfqw35x2gzrdakk6ctwvssxc6twv5hqcqzpgsp5a9ryqw7t23myn9psd36ra5alzvp6lzhxua58609teslwqmdljpxs9qy9qsq9ee7h500jazef6c306psr0ncru469zgyr2m2h32c6ser28vrvh5j4q23c073xsvmjwgv9wtk2q7j6pj09fn53v2vkrdkgsjv7njh9aqqtjn3vd
@ -85,12 +87,11 @@ c$ lightning-cli --network=testnet decodepay lntb100u1p0cwnqtpp5djkdahy4hz0wc909
Here's what most of those elements mean:
1. `currency`: The currency being paid.
1. `created_at`: Time when the invoice was created. This is measured in seconds since 1970.
1. `created_at`: Time when the invoice was created. This is measured in UNIX time, which is seconds since 1970.
1. `expiry`: The time when your node marks the invoice as invalid. Default is 1 hour or 3600 seconds.
1. `payee`: The public key of the person receiving the Lightning Network payment.
1. `payee`: The public key of the person (node) receiving the Lightning Network payment.
1. `msatoshi` and `amount_msat`: The amount of satoshis to be paid.
1. `description`: The user-input description.
1. `min_final_cltv_expiry`: Delta to use for time-lock of CLTV, extended to the final hop.
1. `payment_hash`: The hash of the preimage that is used to lock the payment. You can only redeem a locked payment with the corresponding preimage to the payment hash. This enables routing on the Lightning Network without trusteing third parties by creating a **Conditional Payment** to be filled.
1. `signature`: The DER-encoded signature.
@ -98,11 +99,11 @@ Here's what most of those elements mean:
> :book: ***What is a Hashed Time Locked Contract (HTLC)?*** A Hashed Time Locked Contract is a conditional payment that use hashlocks and timelocks to ensure payment security. The receiver must present a payment preimage or generate a cryptographic proof of payment before a given time, otherwise the payer can cancel the contract by spending it. These contracts are created as outputs from the **Commitment Transaction**.
> :book: ***What is a Commitment Transaction?*** A Commitment Transaction is a transaction that spends the funding transaction. Each peer holds the other peer's signature, meaning that either one can spent his commitment transaction whatever he wants. After each new commitment transaction is created the old one is revoked.
> :book: ***What is a Commitment Transaction?*** A Commitment Transaction is a transaction that spends the original funding transaction. Each peer holds the other peer's signature, meaning that either one can spent his commitment transaction whatever he wants. After each new commitment transaction is created the old one is revoked.
### Checking Your Invoice
There are two crucial elements to check in the invoice. The first, obviously, is the payment amount. The second is the `payee` value, which is the pubkey of the recipient:
There are two crucial elements to check in the invoice. The first, obviously, is the payment amount, which you've already examined in the human-readable part. The second is the `payee` value, which is the pubkey of the recipient (node):
```
"payee": "032a7572dc013b6382cde391d79f292ced27305aa4162ec3906279fc4334602543",
```
@ -174,6 +175,7 @@ lnd$ lncli -n testnet getinfo
}
}
```
However, the `payee` may also be someone brand new, in which case you'll likely need to check with the web site or person who issued the invoice to ensure that it's correct.
## Summary: Generating a Payment Request