Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting channel closure fee in manual way #702

bitcoin-software opened this issue Nov 18, 2019 · 1 comment


Copy link

@bitcoin-software bitcoin-software commented Nov 18, 2019

Reffering to this question:

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?

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

Would like to hear your thoughts.


This comment has been minimized.

Copy link

@Roasbeef Roasbeef commented Nov 22, 2019

Seems this issue should live in the c-lightning issue tracker. The way fees are specified for channel closing at the end points is an implementation detail. Most nodes provide an argument when closing a channel to express what your ideal fee is. In the protocol there's a very loosely defined negotiation that should take place between both parties to decide on the final fee. It may be the case that you end up paying a little bit higher than what you specify, depending on how the implementations handle the fee negotiation.

@Roasbeef Roasbeef closed this Nov 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.