On Mon, Oct 23, 2023 at 11:10:56AM +, ZmnSCPxj wrote:
> Hi all,
>
> This was discussed partially on the platform formerly known as twitter, but
> an alternate design goes like this:
>
> * Add an `nExpiryTime` field in taproot annex.
I would strongly suggest making it nExpiryHeight, and
On 10/20/23 7:43 PM, Peter Todd wrote:
On Fri, Oct 20, 2023 at 09:55:12PM -0400, Matt Corallo wrote:
Quite the contrary. Schnorr signatures are 64 bytes, so in situations like
lightning where the transaction form is deterministically derived, signing 100
extra transactions requires just 6400
On 2023-10-21 18:49, Nadav Ivgi via bitcoin-dev wrote:
Could this be addressed with an OP_CSV_ALLINPUTS, a covenant opcode
that requires _all_ inputs to have a matching nSequence, and using `1
OP_CSV_ALLINPUTS` in the HTLC preimage branch?
This would prevent using unconfirmed outputs in the
Hi all,
This was discussed partially on the platform formerly known as twitter, but an
alternate design goes like this:
* Add an `nExpiryTime` field in taproot annex.
* This indicates that the transaction MUST NOT exist in a block at or above
the height specified.
* Mempool should put txes
