Lightning over taproot with PTLCs



Summary:

In a recent email thread, Lloyd Fournier mentioned that using revocable signatures enables scorched earth punishments. In response, aj suggested the idea of simulating eltoo's behavior in which Alice's justice transaction would pay A+P + max(0, B'-B)*0.1 to Alice and B-f - max(0, B'-B)*0.1 to Bob if Bob posts an earlier state with (A', B') and P'. They also discussed the use of "k" to distinguish inflight payments (htlcs/ptlcs) and RP/2/k notation which implies musig(A/2/n/i/2/k,RB2(n,i)/2/k). Furthermore, aj explained that scriptless PTLC was not used due to the need to share "k+1" nonce pairs in advance of every inflight tx update. They also noted the drawback of option_static_remotekey not being supported but compensated for it by allowing balances to be recovered with only the channel setup data even if all revocation data is lost. Additionally, they emphasized the importance of minimizing the amount of information any third parties could glean by deriving every possible address differently.


Updated on: 2023-05-23T16:17:22.411563+00:00