📅 Original date posted:2021-06-28
📝 Original message:Hi Salvatore,
On 6/28/21 6:03 AM, Salvatore Ingala wrote:
> Hi Andrew,
>
> I just have a small suggestion on this proposal.
>
> On Tue, 22 Jun 2021 at 23:29, Andrew Chow via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> | Taproot Leaf Script
>> | <tt>PSBT_IN_TAP_LEAF_SCRIPT = 0x15</tt>
>> | <tt><control block></tt>
>> | The control block for this leaf as specified in BIP 341. The control
>> block contains the merkle tree path to this leaf.
>> | <tt><script> <8-bit uint></tt>
>> | The script for this leaf as would be provided in the witness stack
>> followed by the single byte leaf version.
>
> So far, all the defined PSBT types had a relatively short keydata (not much bigger than a couple of pubkeys).
> I think that is a desirable property to keep, as it is often a reasonable assumption that dictionary keys are not very large.
> The control block as per BIP 341 can be up to 33 + 32*128 = 4129 bytes long.
>
> Perhaps it would be better to split this into PSBT_IN_TAP_LEAF_SCRIPT and PSBT_IN_TAP_LEAF_CONTROL_BLOCK (both with no keydata)?
A taproot tree can have multiple leaf scripts, and since it is possible that the actual script to be used is not known at the time scripts and control blocks are added to the PSBT, it would not be sufficient to only have two fields with no keydata. It would not be possible to specify multiple leaf scripts.
Furthermore, it is possible to have the same leaf script appear multiple times in the tree. So it is not sufficient to use the leaf hash as the keydata as a script that appears multiple times would only have one control block possible, where in reality it would have more than one.
Thus the only way to allow multiple different leaf scripts, and the same leaf script to appear multiple times, is to use the control block as keydata.
Andrew Chow
> Best,
> Salvatore Ingala
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210628/b423a8cc/attachment.html>;
Andrew Chow [ARCHIVE] /
npub1fg…xak44
2023-06-07 22:55:21
in reply to nevent1q…ulk7
Author Public Key
npub1fgnnmg7f4wzup9hct8nv5pnd9l07wcjqdjku9ax432n4g69v4rgq7xak44Published at
2023-06-07 22:55:21Event JSON
{
"id": "505eda5480bccccb23dc064c1a42004a7c9de19df5cd1ad48092c2c1ae447a4f",
"pubkey": "4a273da3c9ab85c096f859e6ca066d2fdfe762406cadc2f4d58aa75468aca8d0",
"created_at": 1686178521,
"kind": 1,
"tags": [
[
"e",
"1998ce9d04ace2535019f37d7145ee922e0b6bba122df280530581749ee118ab",
"",
"root"
],
[
"e",
"e350971922fb24536b7aab280b96c5637a9f7d2d0fea143d42d5bd40fd1130f2",
"",
"reply"
],
[
"p",
"f86db307ea15ecf745ec5b45e86abbf9755adbc7a6508dca12443cedf6718084"
]
],
"content": "📅 Original date posted:2021-06-28\n📝 Original message:Hi Salvatore,\n\nOn 6/28/21 6:03 AM, Salvatore Ingala wrote:\n\n\u003e Hi Andrew,\n\u003e\n\u003e I just have a small suggestion on this proposal.\n\u003e\n\u003e On Tue, 22 Jun 2021 at 23:29, Andrew Chow via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e | Taproot Leaf Script\n\u003e\u003e | \u003ctt\u003ePSBT_IN_TAP_LEAF_SCRIPT = 0x15\u003c/tt\u003e\n\u003e\u003e | \u003ctt\u003e\u003ccontrol block\u003e\u003c/tt\u003e\n\u003e\u003e | The control block for this leaf as specified in BIP 341. The control\n\u003e\u003e block contains the merkle tree path to this leaf.\n\u003e\u003e | \u003ctt\u003e\u003cscript\u003e \u003c8-bit uint\u003e\u003c/tt\u003e\n\u003e\u003e | The script for this leaf as would be provided in the witness stack\n\u003e\u003e followed by the single byte leaf version.\n\u003e\n\u003e So far, all the defined PSBT types had a relatively short keydata (not much bigger than a couple of pubkeys).\n\u003e I think that is a desirable property to keep, as it is often a reasonable assumption that dictionary keys are not very large.\n\u003e The control block as per BIP 341 can be up to 33 + 32*128 = 4129 bytes long.\n\u003e\n\u003e Perhaps it would be better to split this into PSBT_IN_TAP_LEAF_SCRIPT and PSBT_IN_TAP_LEAF_CONTROL_BLOCK (both with no keydata)?\n\nA taproot tree can have multiple leaf scripts, and since it is possible that the actual script to be used is not known at the time scripts and control blocks are added to the PSBT, it would not be sufficient to only have two fields with no keydata. It would not be possible to specify multiple leaf scripts.\n\nFurthermore, it is possible to have the same leaf script appear multiple times in the tree. So it is not sufficient to use the leaf hash as the keydata as a script that appears multiple times would only have one control block possible, where in reality it would have more than one.\n\nThus the only way to allow multiple different leaf scripts, and the same leaf script to appear multiple times, is to use the control block as keydata.\n\nAndrew Chow\n\n\u003e Best,\n\u003e Salvatore Ingala\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210628/b423a8cc/attachment.html\u003e",
"sig": "d8ccdba8e266cee25f7d444624c95f8ea2fb3a29be2ac821c8c2f57c655193f64645a44b8a7af506053a10441e94dfc123ba6b4f0fb106d49dba887ca6e36ae6"
}