You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lightning-network-tools/lnd/amp.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,11 @@ For a shard of size two this can be simplified as follows, with k being the prei
30
30
31
31
The information necessary for the recipient node to generate the correct preimages and reveal them to claim their payments is passed on in encrypted form as part of the Onion TLV (Type Length Value). This removes the need for additional interaction between the payer and the payee beyond transmitting a node public key or an invoice.
32
32
33
-
## Get your node ready for AMPs <ahref="docs-internal-guid-0aff8c2e-7fff-3644-f0f2-cf0efff90d43"id="docs-internal-guid-0aff8c2e-7fff-3644-f0f2-cf0efff90d43"></a>
Video: Get AMPed: Making Atomic Multi-Path Payments
35
+
{% endembed %}
36
+
37
+
## Get your node ready for AMPs <ahref="#docs-internal-guid-0aff8c2e-7fff-3644-f0f2-cf0efff90d43"id="docs-internal-guid-0aff8c2e-7fff-3644-f0f2-cf0efff90d43"></a>
34
38
35
39
To be able to make and send Atomic Multi-path Payments, you will need to upgrade your node to [LND 0.13 or above](https://github.com/lightningnetwork/lnd/releases).
Copy file name to clipboardExpand all lines: lightning-network-tools/lnd/run-lnd.md
+21-17Lines changed: 21 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,16 @@ description: >-
8
8
9
9
The Lightning Network Daemon (LND) is a complete implementation of a Lightning Network node. That means that LND is able to perform all actions necessary to participate and interact with all aspects of the Lightning Network and its nodes. It fully complies with all Lightning Network specifications (BOLTs) [as described here](https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction.md). As these specifications are currently rapidly evolving, so is LND.
10
10
11
-
## Part 1: Installation <ahref="docs-internal-guid-ff85e2ff-7fff-ef9c-0f05-8da12a86ea43"id="docs-internal-guid-ff85e2ff-7fff-ef9c-0f05-8da12a86ea43"></a>
11
+
## Part 1: Installation <ahref="#docs-internal-guid-ff85e2ff-7fff-ef9c-0f05-8da12a86ea43"id="docs-internal-guid-ff85e2ff-7fff-ef9c-0f05-8da12a86ea43"></a>
12
12
13
13
There are multiple methods for getting LND running on your machine. Your choice will depend on your requirements, the purpose of the installation, your technical expertise, your hardware, security needs and comfort with various tools.
14
14
15
15
Your requirements and dependencies will vary between installation types, as will the effort to maintain them.
LND generally has low system requirements and performs well on small single-board devices with 2 GiB and a CPU with over 1 GHz quad core, such as a Raspberry Pi. Generally the system requirements for Bitcoind are higher than those for LND. A 64-bit architecture is strongly recommended, as a large (>2GB) `channel.db`on 32-bit systems can lead to a system halt. Due to the frequent read and write operations LND should **not** be run from an SD card, but ideally a high-performing SSD.
@@ -44,15 +48,15 @@ You can use the file manager or command line, but may have to create this direct
44
48
45
49
Congratulations, you have successfully installed LND using the binary release. [Jump to: Configuring LND](run-lnd.md#docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86)
46
50
47
-
### Installing Lightning via Docker <ahref="docs-internal-guid-fe99d99a-7fff-2f7a-022e-4fab339d71f9"id="docs-internal-guid-fe99d99a-7fff-2f7a-022e-4fab339d71f9"></a>
51
+
### Installing Lightning via Docker <ahref="#docs-internal-guid-fe99d99a-7fff-2f7a-022e-4fab339d71f9"id="docs-internal-guid-fe99d99a-7fff-2f7a-022e-4fab339d71f9"></a>
48
52
49
53
For those familiar with Docker, or those interested in easily running a variety of software alongside each other, the Docker installation is a convenient and quick way to get started with lightning.
50
54
51
55
To install LND via Docker you will need `docker`, `make` and `bash` on your system. You can install lnd with the following commands:
You are now able to find the binaries in the directory lnd\<latest-release> for your use. Congratulations, [jump to: Configuring LND](run-lnd.md#docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86)
@@ -65,7 +69,7 @@ Installing LND from source is recommended when using it in development or on tes
65
69
You can find the latest version of Golang [on its official website](https://golang.org/dl/). Make sure to verify the checksum before you install Go.
## Part 2: Configuring LND <ahref="docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86"id="docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86"></a>
93
+
## Part 2: Configuring LND <ahref="#docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86"id="docs-internal-guid-f1be3c4d-7fff-b4f7-e6cd-ce2c32ba2d86"></a>
90
94
91
95
### Bitcoin
92
96
@@ -147,7 +151,7 @@ When starting lnd with neutrino, you will need to set the following flags:`--bit
147
151
148
152
To make your node available as a routing node, you will need to listen to incoming connections. In your [lnd.conf configuration file](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf), include the following lines:
149
153
150
-
`listen=0.0.0.0:9735`\
154
+
`listen=0.0.0.0:9735`\
151
155
`listen=[::1]:9736`
152
156
153
157
This will allow your node to listen on all IPv4 (port 9735) and IPv6 (port 9736) interfaces.
@@ -162,15 +166,15 @@ Be aware of any firewall that might be enabled on your system, for example by us
162
166
163
167
Using a firewall is a great idea, although the ports defined above need to remain accessible:
164
168
165
-
`sudo ufw status`\
166
-
`sudo ufw allow OpenSSH`\
169
+
`sudo ufw status`\
170
+
`sudo ufw allow OpenSSH`\
167
171
`sudo ufw allow 9735`
168
172
169
173
#### Other available configurations
170
174
171
175
There are plenty of options to configure lnd. Have a look at the [sample lnd.conf file here](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf) and read our article on the optimal configuration for your node.
172
176
173
-
## Part 3: Running LND <ahref="docs-internal-guid-9df27c7d-7fff-522a-838a-a42710fe3e75"id="docs-internal-guid-9df27c7d-7fff-522a-838a-a42710fe3e75"></a>
177
+
## Part 3: Running LND <ahref="#docs-internal-guid-9df27c7d-7fff-522a-838a-a42710fe3e75"id="docs-internal-guid-9df27c7d-7fff-522a-838a-a42710fe3e75"></a>
174
178
175
179
Now that we have LND installed and configured with its Bitcoin backend we may start it for the first time.
176
180
@@ -245,8 +249,8 @@ If you are running LND in a docker container, you can upgrade this container as
245
249
246
250
First navigate to the local copy of the lnd github repository, for example with `cd lnd`. Then execute the following commands:
247
251
248
-
`git pull`\
249
-
`git checkout <latest-release>`\
252
+
`git pull`\
253
+
`git checkout <latest-release>`\
250
254
`make docker-release tag=<latest-release>`
251
255
252
256
You can now start lnd again, unlock the wallet and verify you are using the correct version with `lncli version`.
The liquidity of on-chain bitcoin is predictable. Bitcoin exists in the form of UTXOs, which are unspent outputs from a previous transaction. To spend bitcoin, you need to receive or mine them first, but generally, they can be moved by the owner at any time.
12
12
@@ -15,7 +15,7 @@ On-chain bitcoin require multiple confirmations by the Bitcoin network to be con
15
15
Your Lightning node is able to receive and send on-chain bitcoin.
16
16
17
17
*`lncli newaddress` Generate a new Bitcoin address
18
-
*`lncli walletbalance`Check your balance.
18
+
*`lncli walletbalance`Check your balance.
19
19
*`lncli sendcoins` Send Bitcoin from this wallet
20
20
21
21
This command follows the format `lncli sendcoins [command options] addr amt`
This means to route payments through this channel, your node will charge 1,000 milli-satoshi (1 satoshi), plus 1 milli-satoshi per million milli-satoshi (`fee_rate` times one million equals fee\_per\_mil). So when routing a payment of 10,000 satoshi, you will earn 1.01 satoshi in fees. This fee policy is applied to all outgoing payments, meaning you will only earn the fee as it is passed on. The fee policy on the incoming channel is decided by that peer. As a rule of thumb, you decide on the fee policy of your capital.
103
103
@@ -206,3 +206,7 @@ Private channels may also bind your capital. Typically, they are created by paym
0 commit comments