Merge pull request #5553 from Kixunil/patch-3

Remove warning about pruned nodes
This commit is contained in:
Oliver Gugger 2021-07-23 15:43:31 +02:00 committed by GitHub
commit a427451b75
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 8 deletions

View File

@ -248,13 +248,8 @@ time of writing of this document, there are three available chain backends:
`btcd`, `neutrino`, `bitcoind`. All including neutrino can run on mainnet with
an out of the box `lnd` instance. We don't require `--txindex` when running
with `bitcoind` or `btcd` but activating the `txindex` will generally make
`lnd` run faster.
**NOTE: WE DO NOT FULLY SUPPORT PRUNED OPERATING MODES FOR FULL NODES.** It's
possible to run a node in a pruned mode and have it serve lnd, however one must
take care to ensure that `lnd` has all blocks on disk since the birth of the
wallet, and the age of the earliest channels (which were created around March
2018).
`lnd` run faster. Note that since version 0.13 pruned nodes are supported
although they cause performance penalty and higher network usage.
The set of arguments for each of the backend modes is as follows:

View File

@ -16,6 +16,11 @@ addholdinvoice call](https://github.com/lightningnetwork/lnd/pull/5533).
* [A new build target itest-race](https://github.com/lightningnetwork/lnd/pull/5542)
to help uncover undetected data races with our itests.
# Documentation
* [Outdated warning about unsupported pruning was replaced with clarification that LND **does**
support pruning](https://github.com/lightningnetwork/lnd/pull/5553)
# Misc
* The direct use of certain syscalls in packages such as `bbolt` or `lnd`'s own