Commitment delay asymmetry



Summary:

In BOLT 3, commitment transactions require the to_local output to be time-locked with OP_CSV while the to_remote is a simple P2WPKH. However, this creates incentives for a party that goes offline and forces a unilateral close to not be penalized, while only the broadcasting party is. This becomes problematic in both normal operation and attack scenarios, such as when the other party does not send an update_fail_htlc after it expires. In these cases, a rational node might decide to become unresponsive instead of broadcasting the commitment, with the hope that the other party publishes instead. To address this issue, Jimpo suggests time-locking the to_remote output by the to_remote_delay, making the consequence of an on-chain settlement symmetric. This change would turn the game from chicken to a tragedy of the commons. Further analysis of this proposal can be found in the links provided for chicken and tragedy of the commons.


Updated on: 2023-05-24T23:12:42.314929+00:00