Hi Johan,
Thanks a lot for the comments, and the independent implementation!
> - For the opcode parameter ordering, it feels unnatural for the two
> tweaks (data, taptree) to be separated by the internal key. A more
> natural ordering of parameters IMO would be (of course this is all
>
@moonsettler
When anyone receives a coin (either as payment or as part of a swap) they
need to perform a verification of all previous signatures and
corresponding backup txs. If anything is missing, then the verification
will fail. So anyone 'breaking the chain' by signing something
incorrectly
Hi John,
On 2023-08-06 16:35, John Light via bitcoin-dev wrote:
is there ever a case where using OP_RETURN
to embed data actually results in fewer bytes onchain than
embedding the same data using the segwit/taproot witness space
Yes, a
Hi all,
The Serverless Payjoin idea has come a long way toward formal specification of
a Payjoin version 2. In the spirit of BIP 2, I’m sharing an intermediate draft
of the BIP here before opening a draft on GitHub for the BIP editors, and
before this exact specification has a complete
