302 sats \ 2 replies \ @xz 27 Aug \ on: "To force close or not to force close, This is the question." - LND & ThunderHub lightning
Answers.
  1. No. I think it's a case of both nodes having to be able to communicate to set the fee-rate. If one channel partner is unreachable, there is no way that the other partner can be guarenteed to close the channel within the accepted parameters of both nodes fee policies.
  2. Thunderhub, doesn't know for sure what the state of channels are (reachable/unreachable) at the time before you submit a request to either unilaterally or cooperatively close.
If you try to doit when a channel is unreachable, it'll assume it is and let you attempt to propse a fee-rate and then attempt to execute it. But you'll receive an error like:
UnexpectedCloseChannelErrorr. unable to gracefully close channel while peer is offline (try force closing it instead): channel link not found
i.e, it just won't allow it. You'd have to force close and accept the unknown fee-rate estimation.
write
preview
31 sats \ 1 reply \ @Wumbo OP 27 Aug
Thanks for the info.
reply
141 sats \ 0 replies \ @xz 27 Aug
No problem. I was just in exactly the same predicament, close or not to. I haven't FC in a long time and avoid it as much as possible. Just jacks up the overall fee.
I hear that the fee negotiation process has been refined a little in later versions of LND.
If you run LND, you can set the node's fee policy from conservative to economical in lnd.conf it supposedly would help on negotiating a lower fee-rate. As I understand.
[Bitcoind]
bitcoind.estimatemode=ECONOMICAL
reply