<p>I'm looking to prune a bitcoind node that will be used by LND.</p>
<p><a href="https://github.com/lightningnetwork/lnd/commit/410b30b9caaf59a78a29d8b924e14395b7daa59d" rel="nofollow noreferrer">https://github.com/lightningnetwork/lnd/commit/410b30b9caaf59a78a29d8b924e14395b7daa59d</a>
From the LND commit recently by Kixunil.</p>
<pre><code>Note that since version 0.13 pruned nodes are supported
although they cause performance penalty and higher network usage.
</code></pre>
<p>I ideally would want to delete all block data before ~March 2018.</p>
<ol>
<li>What are the bitcoin-cli cmd(s) to prune Bitcoind while txindex is enabled?</li>
<li>Is it possible to avoid the potential &quot;<code>performance penalty and higher network usage</code>&quot;?</li>
</ol>
<p>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)?</p>

CC BY-SA 4.0
2021-08-13T03:15:51.957Z
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
<bitcoind><lightning-network><pruning><txindex>
Pruned Bitcoind Backend for LND with txindex enabled for version > v0.13.0
Michael Tidwell
# Pruned Bitcoind Backend for LND with txindex enabled for version > v0.13.0

(Asked by: username_0 on 2021-08-13)

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.

What are the bitcoin-cli cmd(s) to prune Bitcoind while txindex is enabled?
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)?

**Tags:** bitcoind, lightning-network, pruning, txindex

> **Comments:**
> **username_0**: 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?  

---

## 0 answers

