From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Sjors Provoost <sjors@sprovoost•nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Fields for PSBT
Date: Wed, 24 Nov 2021 16:08:18 +0000 [thread overview]
Message-ID: <OkfdZZt7BDS6oE3RU5bosuDuUFnR5oj1alPXP23DQfXXBup61cMCIJj_DUZVi6nXwwCdilVqdj38wL-w7eXwX9HtdSg6FVoF1UevPfD4yCw=@wuille.net> (raw)
In-Reply-To: <E2219CF0-4044-42BC-B782-69DCFF33A5A0@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Wednesday, November 24th, 2021 at 7:44 AM, Sjors Provoost via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> 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 thought it was perhaps necessary in order for a signer to guess which
> script leaves it can sign with its own keys. But you can't really know that without
> actually seeing the script. When a signer looks at a script, it presumably already
> knows the leaf path.
No, that's exactly it. Signers aren't expected to know or understand scripts ahead of time. With a field telling them which keys are present in which leaves, and how those keys are derived, they can sign without fully understanding the script, or needing the ability to parse the relevant script at all. The actual script information is there too of course, for those that do want to analyze it, or factor that into the decision whether to sign or not.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1502 bytes --]
prev parent reply other threads:[~2021-11-24 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 21:22 Andrew Chow
2021-06-28 10:03 ` Salvatore Ingala
2021-06-28 16:04 ` Andrew Chow
2021-06-28 19:56 ` Salvatore Ingala
2021-07-08 20:06 ` Jeremy
2021-11-24 12:44 ` Sjors Provoost
2021-11-24 16:00 ` Greg Sanders
2021-11-24 16:08 ` Pieter Wuille [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='OkfdZZt7BDS6oE3RU5bosuDuUFnR5oj1alPXP23DQfXXBup61cMCIJj_DUZVi6nXwwCdilVqdj38wL-w7eXwX9HtdSg6FVoF1UevPfD4yCw=@wuille.net' \
--to=bitcoin-dev@wuille$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sjors@sprovoost$(echo .)nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox