2

I'm looking to prune a bitcoind node that will be used by LND.

https://github.com/lightningnetwork/lnd/commit/410b30b9caaf59a78a29d8b924e14395b7daa59d From the LND commit recently by Kixunil.

Note that since version 0.13 pruned nodes are supported
although they cause performance penalty and higher network usage.

I ideally would want to delete all block data before ~March 2018.

  1. What are the bitcoin-cli cmd(s) to prune Bitcoind while txindex is enabled?
  2. Is it possible to avoid the potential "performance penalty and higher network usage"?

Edit: txindex is not compatible with pruned nodes in the generic sense. If you know a use case won't require older blocks, is there a way to get the best of both worlds (meaning txindex enabled and removing old blocks)?

Improve this question
2
  • Not sure about 2nd question. Pruning and txindex are not compatible so you can remove txindex=1 and add prune=N in bitcoin.conf where N >550 and is size in MiB. Take backups to avoid any issues.
    – user103136
    Aug 13, 2021 at 3:13
  • 2
    AFAIK, txindex=1 helps performance with LND. If we know lightning nodes aren't going to need the first ~8 or so years of blocks, do we really need to hold on to them? Possible to not suffer the penalties of txindex being off for this use case?
    – Michael Tidwell
    Aug 13, 2021 at 3:15

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.