Thanks for weighing in Dave,
> On Aug 13, 2023, at 8:00 AM, bitcoin-dev-requ...@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 chang
On Sat, Aug 12, 2023 at 2:20 PM Dan Gould wrote:
> am somewhat concerned that some payjoin implementations are written in
> JavaScript and would benefit most from a v2 upgrade in order to support
> receiving, but no JavaScript ur library exists yet. Perhaps one could be
> bound from the rust imp
On August 10, 2023 5:37:54 AM HST, AdamISZ via bitcoin-dev
wrote:
>Hi Dan,
>A couple more more thoughts:
>
>> Out of band, the receiver of the payment, shares a bitcoin URI with the
>> sender including a pj= query parameter describing the relay
>> subdirectory endpoint and psk= parameter wit
Blockchain Commons UR seems to be the most elegant choice since QRs are
commonplace. This suggestion, along with Adam’s to reconsider DH over symmetric
crypto would let us encode a pub key directly in the `pj=` endpoint rather than
with a separate am somewhat concerned that some payjoin impleme
On Fri, Aug 11, 2023 at 3:29 PM symphonicbtc via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Quick little nit I noticed as well, are you sure base64 encoding is the
> best choice for the psk in the URI? You may find that having to urlencode
> the special characters in base64 it i
info/bitcoin-dev
> > or, via email, send a message with subject or body 'help' to
> > bitcoin-dev-requ...@lists.linuxfoundation.org
> >
> > You can reach the person managing the list at
> > bitcoin-dev-ow...@lists.linuxfoundation.org
> >
> > When
he person managing the list at
> bitcoin-dev-ow...@lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of bitcoin-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: BIP for Serverless Payjoin (AdamISZ)
>
&
Sorry for yet another message but:
It just occurred to me that while timing correlation itself might not be much
(in usual circumstances, there are tons of other transactions), it's, as usual
with metadata, the intersection of more than one thing that could hurt: I know
when the tx happens (say
Hi Dan,
A couple more more thoughts:
> Out of band, the receiver of the payment, shares a bitcoin URI with the
> sender including a pj= query parameter describing the relay
> subdirectory endpoint and psk= parameter with base64 encoded
> 256-bit secret key.
You're sending the symmetric secret
Hi all,
The Serverless Payjoin idea has come a long way toward formal specification of
a Payjoin version 2. In the spirit of BIP 2, I’m sharing an intermediate draft
of the BIP here before opening a draft on GitHub for the BIP editors, and
before this exact specification has a complete referenc
10 matches
Mail list logo
