MIME-Version: 1.0
References: <795f917b-3883-1827-f39b-35123b500f36@achow101.com>
 <CAMhCMoF7N4BuXDz1cSDBLi5zH8c06uZ3T3gc750azFH3JagcNw@mail.gmail.com>
 <912b172b-009d-9d5f-32d8-189e7fbe7646@achow101.com>
In-Reply-To: <912b172b-009d-9d5f-32d8-189e7fbe7646@achow101.com>
From: Salvatore Ingala <salvatore.ingala@gmail.com>
Date: Mon, 28 Jun 2021 21:56:37 +0200
Message-ID: <CAMhCMoFD+W-13JFKuF5GnbO2V6htNM3U-rs1ELqEEeV5jF_VpQ@mail.gmail.com>
To: Andrew Chow <achow101-lists@achow101.com>
Content-Type: multipart/alternative; boundary="000000000000ce291205c5d8e332"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Fields for PSBT
Precedence: list

--000000000000ce291205c5d8e332
Content-Type: text/plain; charset="UTF-8"

Hi Andrew,

Thanks for the clarification, I was indeed reading it under the mistaken
assumption that only one leaf would be added to the PSBT.

En passant, for the less experienced readers, it might be helpful if the
key types that are possibly present multiple times (with different keydata)
were somehow labeled in the tables.

Best,
Salvatore Ingala

--000000000000ce291205c5d8e332
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Andrew,</div><div><br></div><div>Thanks for the cl=
arification, I was indeed reading it under the mistaken assumption that onl=
y one leaf would be added to the PSBT.</div><div><br></div><div>En passant,=
 for the less experienced readers, it might be helpful if the key types tha=
t are possibly present multiple times (with different keydata) were somehow=
 labeled in the tables.</div><br><div>Best,</div><div>Salvatore Ingala<br><=
/div></div>

--000000000000ce291205c5d8e332--