lightning-dev

RFC: simplifications and suggestions on open/accept limits.

RFC: simplifications and suggestions on open/accept limits.

Original Postby Pierre

Posted on: November 7, 2018 04:51 UTC

The Lightning Network has set minimum and maximum standards for various aspects of its protocol.

The suggested minimum funding_satoshi for c-lightning is 1000, Eclair requires a 100000 minimum, and lnd has no minimum. However, the author suggests that channels under three times the minimum dust limit should be rejected as too small. This is to prevent unilateral channel closings during network fee spikes. The dust_limit_satoshis is 546 for both c-lightning and Eclair, but can vary in future depending on the min_relay_fee and backlog. max_htlc_value_in_flight_msat is variable for each implementation, with c-lightning giving U64_MAX, Eclair giving 5000000000, and lnd accepting anything above 5 * htlc_minimum_msat. The author suggests removing the max value altogether. All implementations give a 1% channel_reserve_satoshis requirement, which the author agrees should be required. htlc_minimum_msat varies between implementations, with c-lightning allowing up to 0.1% of channel capacity, Eclair accepting any, and lnd accepting any amount above 1000. The author suggests making it zero since relay fees make it non-free anyway. To_self_delay is 144 for all implementations except lnd, which uses a proportional formula. The author suggests using lnd's formula instead. Lastly, max_accepted_htlcs varies between implementations, with c-lightning allowing 483, Eclair allowing 30, and lnd allowing five or more. The author suggests increasing Eclair's limit to 483. The minimum_depth field is only a suggestion, and the author suggests limiting it to three. They also mention other areas of hidden consensus such as who should force close when an error occurs and what the current feerate is, which are being addressed in a new commitment format proposal.