Setting fee sats/vbyte for closing channel miscalculates actual fee rate

[abinition]

Upon closing a channel, (I) selected 50 sats/vbyte, but when transaction was viewed on mempool, it showed 24.4 sats/vbyte. Afterwards, tried doing a "force close" which added a CPFP, this increased fee rate to 47.5 sats/vbyte. Hope it confirms.

Devs should check the math calculation for channel close and apply the correct fee amount from what is selected on web interface.

Hard to reproduce without opening and then closing channels, which costs $$.

Original transaction is ec14e99da2e158bd6aacb4b74292fec1e663453108e5d5d5b9495bacdfd94d88

[saubyk]

Hi @abinition RTL just passes the value user provides in the UI to the API.

Was it a cooperative close or a force close when you first attempted?

[anafaskrowten]

Hi @abinition RTL just passes the value user provides in the UI to the API.

Was it a cooperative close or a force close when you first attempted?

Is this feature in RTL only for LND nodes? I'm running both LND and CLN and both using RTL 0.15.4-beta and the CLN one does not have any place to collect a fee rate.

[saubyk]

CLN one does not have any place to collect a fee rate

Needs further investigation as to why this decision was made. cc: @ShahanaFarooqui