2

When i was at LNConf, one of the devs of c-lightning (IIRC) told me that there is a custom, manual way to agree between two nodes on channel closing fees.

Can anyone elaborate how this is possible? I am operator of two cln nodes, i would like to close channel between these nodes with minimum possible fee, because i am not in hurry.

Are there some side-effects of doing so?

Improve this question

1 Answer 1

Reset to default
1

Just use lightning-cli close id the implementation will first try to do a mutual close. Both lightning nodes will use the fee estimator from Bitcoind to suggest fees. If they don't agree there is a communication protocol defined in the BOLTs that they will eventually find a local agreement between themselves. This protocol is described under the section closing negotiation in BOLT 02 c.f.: https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md#closing-negotiation-closing_signed

Obviously both nodes need to be online and peered before you call the close command otherwise the node will do an expensive force close. Also it makes sense to wait until fees in the mempool are low if you can do that.

Improve this answer
5
  • Hi, Rene! Thank you for fast answer! But this is not the option i am looking for. I want to avoid the use of bitcoind fee estimator and force let's say 1sat/b fee. As mentioned dev told me there is no way to do so with default calls (to be precise he said "this is not implemented in default setup"). I am looking for that custom configuration of node so i can force specific fee as i can do when lightning-cli fundchannel id amount fee
    – baysx
    Nov 18, 2019 at 13:52
  • the point of doing so is exactly what you described, but in reverse order. I dont want to wait until mempool clears to perform tx. i just want to broadcast it and lay back, so it will be included, when mempool clears. so i dont need to monitor state of mempool
    – baysx
    Nov 18, 2019 at 13:55
  • just some additional info: when you open a channel, your node is the only side involved in opening tx, so you can choose the fee yourself. When closing channel, there's multisig tx, that is the reason why you cannot set custom fee (because other part may not agree on low fee). But in case both nodes are co-operative, this should be possible.
    – baysx
    Nov 18, 2019 at 14:42
  • Then I guess you should open a feature request in the clightning github and potentially also on the lightning-rfc. It should be possible to just agree on a low fee but I guess it also needs an amendment to the fee negotiation. Technically the fee is paid by the funder but unfortunately that won't help
    – Rene Pickhardt
    Nov 18, 2019 at 14:43
  • github.com/ElementsProject/lightning/issues/3270 github.com/lightningnetwork/lightning-rfc/issues/702
    – baysx
    Nov 18, 2019 at 17:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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