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
Currently the base fee we apply is always the expected cost to
claim an HTLC on-chain in case of closure. This results in
significantly higher than market rate fees [1], and doesn't really
match the actual forwarding trust model anyway - as long as
channel counterparties are honest, our HTLCs shouldn't end up
on-chain no matter what the HTLC sender/recipient do.
While some users may wish to use a feerate that implies they will
not lose funds even if they go to chain (assuming no flood-and-loot
style attacks), they should do so by calculating fees themselves;
since they're already charging well above market-rate,
over-estimating some won't have a large impact.
This commit adds a configuration knob to set the base fee
explicitly, defaulting to 1 sat, which appears to be market-rate
today.
[1] Note that due to an msat-vs-sat bug we currently actually
charge 1000x *less* than the calculated cost.
breakSome(("Prior hop has deviated from specified fees parameters or origin node has obsolete ones",0x1000 | 12,Some(self.get_channel_update(chan).unwrap())));
default_config.own_channel_config.our_htlc_minimum_msat = 1000;// sanitization being done by the sender, to exerce receiver logic we need to lift of limit
default_config.own_channel_config.our_htlc_minimum_msat = 1000;// sanitization being done by the sender, to exerce receiver logic we need to lift of limit
0 commit comments