The feerates command returns the feerates that CLN will use.
The feerates will be based on the recommended feerates from the backend.
The backend may fail to provide estimates, but if it was able to provide
estimates in the past, CLN will continue to use those for a while.
CLN will also smoothen feerate estimations from the backend.
style is either of the two strings:
perkw - provide feerate in units of satoshis per 1000 weight.
perkb - provide feerate in units of satoshis per 1000 virtual bytes.
Bitcoin transactions have non-witness and witness bytes:
Non-witness bytes count as 4 weight, 1 virtual byte.
All bytes other than SegWit witness count as non-witness bytes.
Witness bytes count as 1 weight, 0.25 virtual bytes.
Thus, all perkb feerates will be exactly 4 times perkw feerates.
To compute the fee for a transaction, multiply its weight or virtual bytes
by the appropriate perkw or perkw feerate
returned by this command,
then divide by 1000.
There is currently no way to change these feerates from the RPC.
If you need custom control over onchain feerates,
you will need to provide your own plugin
that replaces the bcli plugin backend.
For commands like lightning-withdraw(7) or lightning-fundchannel(7) you
can provide a preferred feerate directly as a parameter,
which will override the recommended feerates returned by feerates.
The feerates command returns the feerates that CLN will use. The feerates will be based on the recommended feerates from the backend. The backend may fail to provide estimates, but if it was able to provide estimates in the past, CLN will continue to use those for a while. CLN will also smoothen feerate estimations from the backend.
style is either of the two strings:
Bitcoin transactions have non-witness and witness bytes:
Thus, all perkb feerates will be exactly 4 times perkw feerates.
To compute the fee for a transaction, multiply its weight or virtual bytes by the appropriate perkw or perkw feerate returned by this command, then divide by 1000.
There is currently no way to change these feerates from the RPC. If you need custom control over onchain feerates, you will need to provide your own plugin that replaces the
bcliplugin backend. For commands like lightning-withdraw(7) or lightning-fundchannel(7) you can provide a preferred feerate directly as a parameter, which will override the recommended feerates returned by feerates.