Thanks, Michael, for writing this up. I agree that it's good to archive
events like, for example, soft-fork activations in an ML post.
All bigger pools have now included multiple P2TR spends in their blocks.
I have a few comments on what happened at F2Pool and to some extend also
at AntPool.
On Wednesday, November 24th, 2021 at 7:44 AM, Sjors Provoost via bitcoin-dev
wrote:
> Hi Andrew,
>
> I'm confused why PSBT_IN_TAP_BIP32_DERIVATION and
> PSBT_OUT_TAP_BIP32_DERIVATION
> contain not just the derivation path for the xonlypubkey, but also the
> tapleaf merkle path.
>
> First I
I may be misunderstanding the question, but it seems essential data for the
finalizer role, which may not know such information on its own.
On Wed, Nov 24, 2021 at 11:15 PM Sjors Provoost via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi Andrew,
>
> I'm confused why
Hi Andrew,
I'm confused why PSBT_IN_TAP_BIP32_DERIVATION and PSBT_OUT_TAP_BIP32_DERIVATION
contain not just the derivation path for the xonlypubkey, but also the tapleaf
merkle path.
First I thought it was perhaps necessary in order for a signer to guess which
script leaves it can sign with its
