Author: Bastien TEINTURIER 2020-10-05 11:46:12
Published on: 2020-10-05T11:46:12+00:00
The recent discussions around channel jamming have brought to light the importance of configuring channel parameters carefully. Certain parameters that are set only once at channel creation could benefit from being configurable throughout the lifetime of the channel, such as max_htlc_value_in_flight_msat, max_accepted_htlcs, htlc_minimum_msat, and htlc_maximum_msat. Although nodes can currently update these unilaterally through forwarding heuristics, it would be better to inform peers about the limits put in place to avoid unnecessary cycles of add/commit/revoke/fail messages. The suggestion is to add tlv records in `commitment_signed` to notify channel peers that there will be changes made in the values of these fields. Bastien asks whether anyone opposes this idea, if other fields should become dynamic as well, and if a new message is required instead of using extensions of `commitment_signed`.
Updated on: 2023-06-03T02:15:42.038412+00:00