Author: Jim Posen 2018-04-13 22:10:16
Published on: 2018-04-13T22:10:16+00:00
The proposal suggests that both parties should use the maximum delay if either one asks for it. However, the issue can be resolved by making sure that both parties have to wait the same amount of time regardless of who publishes the commitment. The suggestion is to add a new section called "Symmetric CSV Delay" to the brainstorming part of the wiki. This would require the full CSV delay on the remote output of all commitment transactions and act as an incentive for both parties to mutually close rather than waiting for the other side to close unilaterally. It would also serve as punishment to misbehaving or unresponsive nodes that force the other endpoint to go to chain.
Updated on: 2023-05-24T23:14:34.030190+00:00