From: Dan Gould <d@ngould•dev>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
dave@dtrt•org
Subject: Re: [bitcoin-dev] BIP for Serverless Payjoin
Date: Sun, 13 Aug 2023 12:50:32 +0000 [thread overview]
Message-ID: <92588478-9239-4D85-89E5-B6EDE3068FCF@ngould.dev> (raw)
In-Reply-To: <mailman.5.1691928003.16386.bitcoin-dev@lists.linuxfoundation.org>
Thanks for weighing in Dave,
> On Aug 13, 2023, at 8:00 AM, bitcoin-dev-request@lists•linuxfoundation.org wrote:
>
>
> The way BItcoin users currently use BIP21 URIs and QR-encoded BIP21 URIs, posting them where evesdroppers can see
>
> …
>
> I don't think it would be practical to change that expectation, and I think a protocol where evesdropping didn't create a risk of funds loss would be much better than one where that risk was created.
>
> dave@dtrt•org
The BIP has changed to adopt a DH cryptosystem where the receiver only shares a public key in the BIP 21 as part of the pj= endpoint since Adam posted comments. I agree enabling the simplest asynchronous experience while, as I gather you’re thinking, keeping the UX expectation that leaked BIP 21 URIs pose no risk for loss of funds is the right set of tradeoffs.
Dan
next parent reply other threads:[~2023-08-13 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1691928003.16386.bitcoin-dev@lists.linuxfoundation.org>
2023-08-13 12:50 ` Dan Gould [this message]
[not found] <mailman.130337.1691684480.956.bitcoin-dev@lists.linuxfoundation.org>
2023-08-11 17:03 ` [bitcoin-dev] BIP for Serverless Payjoin (AdamISZ) Dan Gould
2023-08-11 22:04 ` symphonicbtc
2023-08-12 1:05 ` Christopher Allen
2023-08-12 21:20 ` [bitcoin-dev] BIP for Serverless Payjoin Dan Gould
2023-08-13 9:22 ` Christopher Allen
2023-08-09 17:32 Dan Gould
2023-08-10 15:37 ` AdamISZ
2023-08-10 15:46 ` AdamISZ
2023-08-13 6:58 ` David A. Harding
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=92588478-9239-4D85-89E5-B6EDE3068FCF@ngould.dev \
--to=d@ngould$(echo .)dev \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(echo .)org \
/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