mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-03-15 03:51:23 +01:00
docs: Remove pruned node warning. [skip ci]
This commit is contained in:
parent
6be472eb98
commit
a39e6105e4
1 changed files with 5 additions and 11 deletions
|
@ -20,7 +20,8 @@
|
||||||
- [Prevent data corruption](#prevent-data-corruption)
|
- [Prevent data corruption](#prevent-data-corruption)
|
||||||
- [Don't interrupt `lncli` commands](#dont-interrupt-lncli-commands)
|
- [Don't interrupt `lncli` commands](#dont-interrupt-lncli-commands)
|
||||||
- [Regular accounting/monitoring](#regular-accountingmonitoring)
|
- [Regular accounting/monitoring](#regular-accountingmonitoring)
|
||||||
- [Pruned bitcoind node](#pruned-bitcoind-node)
|
- [The `-txindex` flag](#the--txindex-flag)
|
||||||
|
- [Running multiple lnd nodes](#running-multiple-lnd-nodes)
|
||||||
- [The `--noseedbackup` flag](#the---noseedbackup-flag)
|
- [The `--noseedbackup` flag](#the---noseedbackup-flag)
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
@ -415,21 +416,14 @@ Regular monitoring of a node and keeping track of the movement of funds can help
|
||||||
prevent problems. Tools like [`lndmon`](https://github.com/lightninglabs/lndmon)
|
prevent problems. Tools like [`lndmon`](https://github.com/lightninglabs/lndmon)
|
||||||
can assist with these tasks.
|
can assist with these tasks.
|
||||||
|
|
||||||
### Pruned bitcoind node
|
### The `-txindex` flag
|
||||||
|
|
||||||
Running `lnd` connected to a `bitcoind` node that is running in prune mode is
|
|
||||||
not supported! `lnd` needs to verify the funding transaction of every channel
|
|
||||||
in the network and be able to retrieve that information from `bitcoind` which
|
|
||||||
it cannot deliver when that information is pruned away.
|
|
||||||
|
|
||||||
In theory pruning away all blocks _before_ the SegWit activation would work
|
|
||||||
as LN channels rely on SegWit. But this has neither been tested nor would it
|
|
||||||
be recommended/supported.
|
|
||||||
|
|
||||||
In addition to not running a pruned node, it is recommended to run `bitcoind`
|
In addition to not running a pruned node, it is recommended to run `bitcoind`
|
||||||
with the `-txindex` flag for performance reasons, though this is not strictly
|
with the `-txindex` flag for performance reasons, though this is not strictly
|
||||||
required.
|
required.
|
||||||
|
|
||||||
|
### Running multiple lnd nodes
|
||||||
|
|
||||||
Multiple `lnd` nodes can run off of a single `bitcoind` instance. There will be
|
Multiple `lnd` nodes can run off of a single `bitcoind` instance. There will be
|
||||||
connection/thread/performance limits at some number of `lnd` nodes but in
|
connection/thread/performance limits at some number of `lnd` nodes but in
|
||||||
practice running 2 or 3 `lnd` instances per `bitcoind` node didn't show any
|
practice running 2 or 3 `lnd` instances per `bitcoind` node didn't show any
|
||||||
|
|
Loading…
Add table
Reference in a new issue