Author: Matt Corallo 2019-12-16 01:27:59
Published on: 2019-12-16T01:27:59+00:00
The Lightning Network is constantly exploring ways to improve its performance while maintaining security and privacy. One area of focus is the signing commitment transactions, which involve a lot of round trips and can affect latency. To address this, the Lightning Network is considering using fast-forwards or explicit 2-of-2 for commitment and MuSig for mutual close.Another area of exploration is the use of pointlocked timelocked contracts (PTLCs) to switch to payment point+scalar. There are two types of PTLCs: scriptless and revocable. The scriptless PTLCs require a complete MuSig ritual to sign the timelocked branch, which increases the latency of adding new PTLCs. On the other hand, the revocable PTLCs enable faster addition of new PTLCs but require a backout transaction that must be signed by both parties before broadcasting the first transaction.However, the decision to use either a purely scriptless PTLC construction or a tapscripted timelock branch and a keypath pointlocked branch for PTLCs is affected because we need revocable PTLCs, not plain PTLCs. This is because the Poon-Dryja mechanism requires that all outputs of Poon-Dryja must be made revocable. Revocable outputs always have a CSV-requirement before the output can be spent by whoever "should" own the output, according to the contract details.Overall, the Lightning Network is exploring different options to optimize its performance while maintaining security and privacy. It is important to note that further discussions may be necessary before selecting particular options to implement and evaluate in alpha software.
Updated on: 2023-05-23T02:41:31.295798+00:00