Hello #nostriches,
Did I miss anything other than badges?
I spent most of my day fixing one of my nodes today. Lesson learned; don't run lightning node with a pruned Bitcoin node.
👇
#[0]
Hello #nostriches,
Did I miss anything other than badges?
I spent most of my day fixing one of my nodes today. Lesson learned; don't run lightning node with a pruned Bitcoin node.
👇
#[0]
Explain why please 🙏
Lnd with all cool tools does not support pruned nodes at all (per BTCpay docs).
c-lightning claims to support but a lot of stars need to align for that to work. The problem is c-lightning keeps requesting a block that has been pruned. I had to use rescan option to give it a block number to start scanning.
It has been working for couple of weeks. Today after a backup and restart, it ignored the rescan height and got stuck. magically came back, but lost my confidence for prod setting.
Side note: it is important to backup your lightning channels to prevent losing the funds.
Unlike lnd, c-lightning doesn't seem to make that easy.
TLDR; due to pruned node, I had to cancel backup cron job which would restart BTCpay after backup, and c-lightning might not recover.