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
Turns out we will try to send feerate updates that we cannot at all afford right now. Val caught it in review at #985 (comment) and it seems the chanmon_consistency fuzzer has also found it (or something related).
The text was updated successfully, but these errors were encountered:
I think you should replicate d3af49e to limit outbound fee updates, even if we assume our fee estimator is always more "reasonable" than the counterparty one.
We could do that (I think a simpler approach would be to limit upwards fee increase to eg 25% per $TIME_PERIOD), but independently, we don't limit it at all and can overrun our own reserve value!
I think a simpler approach would be to limit upwards fee increase to eg 25% per $TIME_PERIOD
Right, though such solution would let max_dust_htlc_exposure bypass when real-world fees overflow 25% per $TIME_PERIOD, especially that $TIME_PERIOD isn't fixed for HTLC's CLTV
Turns out we will try to send feerate updates that we cannot at all afford right now. Val caught it in review at #985 (comment) and it seems the chanmon_consistency fuzzer has also found it (or something related).
The text was updated successfully, but these errors were encountered: