From: Salvatore Ingala <salvatore.ingala@gmail•com>
To: Sjors Provoost <sjors@sprovoost•nl>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Who uses or wants to use PSBTv2 (BIP370)
Date: Fri, 17 Jan 2025 10:45:44 +0100 [thread overview]
Message-ID: <CAMhCMoGONKFok_SuZkic+T=yoWZs5eeVxtwJL6Ei=yysvA8rrg@mail.gmail.com> (raw)
In-Reply-To: <6FDAD97F-7C5F-474B-9EE6-82092C9073C5@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi Sjors,
The Ledger Bitcoin app uses PSBTv2 since version 2.0.0 in 2021 [0], quite
possibly the first adopter - although for somewhat unusual reasons.
Working with embedded devices with just a few kb of RAM, even sending the
entire PSBT is not generally feasible.
Therefore, the client instead sends a 'merkleized' commitment to the entire
PSBT at the beginning of the signing process.
This enables the device to obtain random access to the PSBT by querying the
client (who provides the data - and the Merkle proof - on demand).
In PsbtV0, the unsigned transaction is a binary blob, which was a huge
headache because the device had to parse it while streaming it (and
therefore, no RAM access to the individual transaction fields is possible).
PsbtV2 fixed this by having the transaction already 'parsed' into
individual fields.
The companion client libraries of the Ledger Bitcoin app support both
versions, and PsbtV0 is converted to PsbtV2 on the fly.
Broader support would certainly be useful.
Best,
Salvatore Ingala
[0] https://www.ledger.com/blog/bitcoin-2
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMhCMoGONKFok_SuZkic%2BT%3DyoWZs5eeVxtwJL6Ei%3DyysvA8rrg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2022 bytes --]
next prev parent reply other threads:[~2025-01-17 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 9:16 Sjors Provoost
2025-01-17 9:45 ` Salvatore Ingala [this message]
2025-01-17 10:38 ` Kalle Rosenbaum
2025-01-17 13:02 ` Salvatore Ingala
2025-01-17 10:01 ` Kalle Rosenbaum
2025-01-17 14:53 ` [bitcoindev] " Andrew Toth
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='CAMhCMoGONKFok_SuZkic+T=yoWZs5eeVxtwJL6Ei=yysvA8rrg@mail.gmail.com' \
--to=salvatore.ingala@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--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