Author: Johnson Lau 2018-12-21 16:21:42
Published on: 2018-12-21T16:21:42+00:00
In an email exchange between Christian Decker and Johnson Lau on December 21, 2018, the two discussed the use of OP_CSV (BIP112) in a 2-of-2 branch. Lau argued that it was not necessary to restrict the BIP68 relative locktime since both parties needed to agree on it. Decker agreed, admitting to forgetting about BIP68, but noted that it would save them a few bytes.However, with taproot, the use of BIP68 actually saves more than just a few bytes. For each update, three signatures are made: one SIGHASH_ALL spending the setup TXO with no locktime, one NOINPUT spending a previous update TXO with absolute locktime, and one NOINPUT spending the latest update TXO with relative locktime. The first and third signatures can be signed directly with the scriptPubKey without revealing the hidden taproot script. The second signature is only necessary if someone publishes an outdated update transaction and will reveal the taproot script.
Updated on: 2023-05-20T18:55:36.597198+00:00