From: Salvatore Ingala <salvatore.ingala@gmail.com>
To: Andrew Chow <achow101-lists@achow101.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Fields for PSBT
Date: Mon, 28 Jun 2021 21:56:37 +0200 [thread overview]
Message-ID: <CAMhCMoFD+W-13JFKuF5GnbO2V6htNM3U-rs1ELqEEeV5jF_VpQ@mail.gmail.com> (raw)
In-Reply-To: <912b172b-009d-9d5f-32d8-189e7fbe7646@achow101.com>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 461 bytes --]
next prev parent reply other threads:[~2021-06-28 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 21:22 [bitcoin-dev] Taproot Fields for PSBT Andrew Chow
2021-06-28 10:03 ` Salvatore Ingala
2021-06-28 16:04 ` Andrew Chow
2021-06-28 19:56 ` Salvatore Ingala [this message]
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
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=CAMhCMoFD+W-13JFKuF5GnbO2V6htNM3U-rs1ELqEEeV5jF_VpQ@mail.gmail.com \
--to=salvatore.ingala@gmail.com \
--cc=achow101-lists@achow101.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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