This is related to lightning/bolts#904
Since c-lightning already supports warning messages, we should do this right now.
When c-lightning receives a warning during quick close (usually because the peer doesn't agree with the fee_range c-lightning sent), we really should not disconnect. If we stay connected and the node operator reads the warning message, they can reuse the close API to change the fee_range to something that the peer will agree with, and the mutual close is able to make progress.
But right now since c-lightning disconnects, on reconnection it will re-send the same fee_range automatically so it will instantly disconnect again, not giving the node operator an opportunity to update the fee_range.
This is related to lightning/bolts#904
Since c-lightning already supports warning messages, we should do this right now.
When c-lightning receives a warning during quick close (usually because the peer doesn't agree with the
fee_rangec-lightning sent), we really should not disconnect. If we stay connected and the node operator reads the warning message, they can reuse thecloseAPI to change thefee_rangeto something that the peer will agree with, and the mutual close is able to make progress.But right now since c-lightning disconnects, on reconnection it will re-send the same
fee_rangeautomatically so it will instantly disconnect again, not giving the node operator an opportunity to update thefee_range.