pull down to refresh

  1. Yes. And many nodes are also using shit ton of automated scripts that could trigger a FC. Are many reasons why was triggered and is quite hard to find out from your side.
    Could be too long pending HTLCs, too many pending HTLCs, you are running on Tor and even that you see your node online, is still do not broadcast in fast time your channels status.... etc
    You could check with
lncli pendingchannels

to see more details about that FC

  1. Recommendations? Read my guides, I wrote a lot about nodes:
    https://darthcoin.substack.com/p/recommendations-for-ln-users
    https://darthcoin.substack.com/p/lightning-node-maintenance
    https://darthcoin.substack.com/p/lightning-routing-fees-experiment
    ... etc
  2. WT is used more to protect your node when is offline and you cannot broadcast the correct state of your channels. If your node is online it will broadcast anyways the real status of your channels. But remember: IF you use another state of your channels (old backup of channels.db) and you came back online with that old status, then you will be the one punished (if the peer is using a WT).
    WTs are only "fact checkers" of the last state of a channel.

Where is lncli pendingchannels meant to be run from?

I am getting "command not found" message when I run it.

reply

deleted by author

deleted by author