From: Andrew Toth <andrewstoth@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: Who uses or wants to use PSBTv2 (BIP370)
Date: Fri, 17 Jan 2025 06:53:52 -0800 (PST) [thread overview]
Message-ID: <30737859-573e-40ea-9619-1d18c2a6b0f4n@googlegroups.com> (raw)
In-Reply-To: <6FDAD97F-7C5F-474B-9EE6-82092C9073C5@sprovoost.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1863 bytes --]
BIP375 Sending Silent Payments with PSBTs uses PSBTv2, specifically the PSBT_OUT_SCRIPT
field.
For silent payments, the output script is not known at the time of
creation, so it's not possible to create an unsigned transaction with an
output script as required in v0.
On Friday, January 17, 2025 at 4:17:49 AM UTC-5 Sjors Provoost wrote:
> Dear list,
>
> It's been a few years since BIP370 was proposed [0]. It's a backwards
> compatible change to the PSBT standard defined by BIP174 [1]. Its main
> benefit is the ability to add new inputs and outputs to a transaction.
>
> There's a Bitcoin Core pull request #21283 implements support [2], but has
> seen very little review so far. Being able to test it against other
> implementation would aid in review.
>
> So which projects are using PSBTv2 or would very much like to?
>
> So far I've learned that Core Lightning uses it. They convert it back to
> v0 when interacting with Bitcoin Core, which they find suboptimal [3].
>
> Feel free to answer here on Stack Exchange [4].
>
> Kind regards,
>
> Sjors Provoost
>
> [0] https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki
> [1] https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
> [2] https://github.com/bitcoin/bitcoin/pull/21283
> [3] https://github.com/bitcoin/bitcoin/pull/21283#issuecomment-2597171643
> [4]
> https://bitcoin.stackexchange.com/questions/125384/who-uses-or-wants-to-use-psbtv2-bip370
--
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/30737859-573e-40ea-9619-1d18c2a6b0f4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4053 bytes --]
prev parent reply other threads:[~2025-01-17 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 9:16 [bitcoindev] " Sjors Provoost
2025-01-17 9:45 ` Salvatore Ingala
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 ` Andrew Toth [this message]
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=30737859-573e-40ea-9619-1d18c2a6b0f4n@googlegroups.com \
--to=andrewstoth@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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