📅 Original date posted:2021-11-24 📝 Original message:On Wednesday, November ...

Pieter Wuille [ARCHIVE] /

npub1tje…tl6r

2023-06-07 23:00:40

in reply to nevent1q…3jkq

📅 Original date posted:2021-11-24
📝 Original message:On Wednesday, November 24th, 2021 at 7:44 AM, Sjors Provoost via bitcoin-dev <bitcoin-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211124/30416f16/attachment-0001.html>;

Author Public Key

npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 23:00:40

Kind type

1 Short Text Note

Event JSON

{ "id": "f76aa5790dd53afc30198233987cba4c47ff5758bdc21f5fa084d0e40de73552", "pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6", "created_at": 1686178840, "kind": 1, "tags": [ [ "e", "23759122835f141a79dade9299fd003a295699882bad00595dc22f6d3c615e0f", "", "root" ], [ "e", "eb304278a3af1da46c819b4664675cf7e68121a274ded99db7148fb5d4cb0438", "", "reply" ], [ "p", "937f10fc4f78d8676348562d9d886843fbb351d99d6c96423fe9970819962e19" ] ], "content": "📅 Original date posted:2021-11-24\n📝 Original message:On Wednesday, November 24th, 2021 at 7:44 AM, Sjors Provoost via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hi Andrew,\n\u003e\n\u003e I'm confused why PSBT_IN_TAP_BIP32_DERIVATION and PSBT_OUT_TAP_BIP32_DERIVATION\n\u003e contain not just the derivation path for the xonlypubkey, but also the tapleaf merkle path.\n\u003e\n\u003e First I thought it was perhaps necessary in order for a signer to guess which\n\u003e script leaves it can sign with its own keys. But you can't really know that without\n\u003e actually seeing the script. When a signer looks at a script, it presumably already\n\u003e knows the leaf path.\n\nNo, 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.\n\nCheers,\n\n--\nPieter\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211124/30416f16/attachment-0001.html\u003e", "sig": "d634d4f59872244f1762aa46859b7eaf3ad9d366c5a03a914f3b88bcb577d83b215d73707011e44ec4509147471e3686561966b80c6de285f43938b9e1f14a4c" }