Most lightning implementations I came across don't officially support pruned full node.

  • Why is pruned mode implementation a challenge?
  • What risk am I taking when I run lnd with pruned bitcoind?

Pruned nodes don't have the ability to make a full index of all transactions in the chain, which makes implementation of tools like Lightning difficult or impossible. There's no risk particularly, a pruned node has the same security properties as a normal one, it just doesn't have historical transaction data necessarily.

  • 1
    There is no reason that lightning should need access to a non-pruned node, and AFAIK c-lightning doesn't. Regardless, any requirement for non-pruning is an implementation specific limitation. – G. Maxwell Dec 22 '18 at 2:27
  • "Notice that currently pruned nodes are not supported and may result in lightningd being unable to synchronize with the blockchain." from c-lightning README. – sanket1729 Dec 22 '18 at 2:58
  • I was to mark this as accepted, but this has a downvote; I will wait for corrections. – sanket1729 Dec 22 '18 at 4:35
  • c-lightning technically works with pruned nodes, the problem however is that if the node prunes the blocks before c-lightning was able to process them (for example by letting bitcoind run and lightningd is off for a long time), then c-lightning will not be able to catch up with the blockchain. If you can ensure that c-lightning is also running together with bitcoind, I see no problem with it and we have a number of users that are running it like this – cdecker Dec 22 '18 at 11:44
  • The support mentioned in the readme is just to say that we don't want masses of people spamming the issue tracker with pruned node issues :-) – cdecker Dec 22 '18 at 11:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.