Appendix

Note that there might be things I want to add on to, or fix. If you want to get the most recent version of this article, please check the github-gist which has all the changes. The Guide where you got a Lightning close-transaction and can't get the channel closed

Change-Log

  • Typo: Terminal 2 monitoring of two strings via boolean OR only works with an uppercase -E: sudo tail -f .lnd/logs/bitcoin/mainnet/lnd.log | grep -E 'PUBKEYOFCHANNELPARTNER|CHANNELPOINT:VOUT'
  • Tuning: Increasing your bitcoin-mempool size to 2000 might be a bit of an overkill. If your hanging tx is not older than 2 weeks, 600MB will suffice for now
  • Spending: CPFP child does not necessarily need 2x the sat-fee, try with your effective sat/vbyte target first, and bump if it's too low: lncli wallet bumpclosefee --sat_per_vbyte 50 CHANPOINT:VOUT and check the effective-fee rate. LND might have improved their method, so it auto-calculates everything for you
  • ☂️ footnotes: If you enounter a tty-error for lncli or bitcoin-cli, adjust the call with -it like this: ~/umbrel/scripts/app compose lightning exec -it lnd lncli