You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.
c-lightning has a limit on the max fee a user can pay, in order to prevent the payer from paying a fee several times greater than the actual payment. In particular, the maxfeepercent value has to be between 0 and 100, making impossible to pay a fee greater than the value of the payment.
In RGB, this would slightly affect the payment experience, as it requires the user to (i) send some extra satoshis to the counterparty, even if she does not want to, in order to keep the fee percent between the allowed values and (ii) always have some extra satoshis in the channel, in order to avoid ending up with the tokens blocked due to inability to transfer enough satoshis.
Even if this is a minor issue, I think it would still be good to remove this limit or make it more flexible in an RGB lightning implementation.
The text was updated successfully, but these errors were encountered:
c-lightning has a limit on the max fee a user can pay, in order to prevent the payer from paying a fee several times greater than the actual payment. In particular, the
maxfeepercent
value has to be between 0 and 100, making impossible to pay a fee greater than the value of the payment.In RGB, this would slightly affect the payment experience, as it requires the user to (i) send some extra satoshis to the counterparty, even if she does not want to, in order to keep the fee percent between the allowed values and (ii) always have some extra satoshis in the channel, in order to avoid ending up with the tokens blocked due to inability to transfer enough satoshis.
Even if this is a minor issue, I think it would still be good to remove this limit or make it more flexible in an RGB lightning implementation.
The text was updated successfully, but these errors were encountered: