From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Dan Gould <d@ngould•dev>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP for Serverless Payjoin
Date: Sun, 13 Aug 2023 02:22:47 -0700 [thread overview]
Message-ID: <CACrqygDZ=JYs=G5J=KqN_S88rz_vW8mTwja4jMw=jRJVQ6UbGQ@mail.gmail.com> (raw)
In-Reply-To: <ACC80254-1AE2-4B6E-8D5C-A3C3FACCA6EA@ngould.dev>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Sat, Aug 12, 2023 at 2:20 PM Dan Gould <d@ngould•dev> 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 implementation.
>
There is some progress here, including our reference library in Typescript
for dCBOR and UR-based Envelope, but hopefully we will expand soon to offer
it in reference libraries, though some will have to be wasm of our rust
code.
I've heard that there are some wallets using URs written Javascript, but
they have not announced open source libraries yet.
-- Christopher Allem
[-- Attachment #2: Type: text/html, Size: 1119 bytes --]
next prev parent reply other threads:[~2023-08-13 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] <mailman.5.1691928003.16386.bitcoin-dev@lists.linuxfoundation.org>
2023-08-13 12:50 ` Dan Gould
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='CACrqygDZ=JYs=G5J=KqN_S88rz_vW8mTwja4jMw=jRJVQ6UbGQ@mail.gmail.com' \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=d@ngould$(echo .)dev \
/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