Return-Path: Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id B5D26C013A for ; Sat, 16 Jan 2021 06:15:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id A781A2E1A1 for ; Sat, 16 Jan 2021 06:15:41 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l3zbduyuxSMH for ; Sat, 16 Jan 2021 06:15:39 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) by silver.osuosl.org (Postfix) with ESMTPS id 9EA532035D for ; Sat, 16 Jan 2021 06:15:39 +0000 (UTC) Received: by mail-io1-f43.google.com with SMTP id x21so4349832iog.10 for ; Fri, 15 Jan 2021 22:15:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o0JMgmgtD3Fcz86VJE6yMxny916OcK/4HQ4xqOog0RQ=; b=i4RklPbxj20cE6b9npBMMGkIKBUAihKbKcHAI+v0SLJAkjixgBmjxq9+tRBLRDv5pl 1QOhu2JAtvc6E4wo4k9cCeBkCdvGqOezNsnjg16emdEJjWaV7TCMjQzCwxtr+E8tDruI un+xA/73295NllYZ7Xervl0urneAC6zxkdDxn3XL0uF4ULVmyXDmasrEXQGsf68+1K3Y 69owQt0gZN2s8hDwUwZLeWkcK6++yM8oEW3rH9m/OUtMS1v6CMqoGfM4YGZf52pvAEwS GLXUBuj1+gDfqQukAkV5ANqzUrvPQzfPjv7O3oAE1acDyMzH3B5sXp6E45iPx1FWVcSp MyEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=o0JMgmgtD3Fcz86VJE6yMxny916OcK/4HQ4xqOog0RQ=; b=MhXwY0a9JE60AFfyu6qOYBDOLnisQTjLiIR6Ecb80TH5dOrv9YusVR944QghOQYtuT sGdfwkIiy3NqfICLcXfpEUkRVecm/eJomvVUkYKMylz6fuoXLNNzuHf98yfxRBt6o0p6 CUEB6HYUcdo/UZUchJuYUAw/5Qv1jkbLrEXbx8XgQ+5AabcvmrCPAnzh/HjDQL+iwSrU t1/BaANKhaPdDu3GkhGmlrXvgHntUg19qe6455E/AMwp7IlfFppFvWjpxMmCBd2aSt9l 5B6MsiB5i277ms6YCORwrv9IG5fbRM3CuuoFqBwu4wg8Mv61pWNn7uhqyxDDPNou6Ssy 6hjA== X-Gm-Message-State: AOAM532XPdeo/ambGEX5GYy3bjHBV24eRFWyb4nwSvcBIEDzLMiInZba 6CKKxtxMmMAvnBDYHR6IXfeLt45DwAe0x9sY//FbGzbA X-Google-Smtp-Source: ABdhPJyhE0Gn4fKZuYilNsiKuoShPBifkNPXYx/hYf9uPcO700E+3CwFI4gOkxEIfvhF3mToJlhjAA9SlhfZGxFWVkw= X-Received: by 2002:a02:634b:: with SMTP id j72mr5424543jac.106.1610777738715; Fri, 15 Jan 2021 22:15:38 -0800 (PST) MIME-Version: 1.0 References: <2b8ba39f-8fe9-8800-b8e6-47ca263774d5@riseup.net> In-Reply-To: From: Craig Raw Date: Sat, 16 Jan 2021 08:15:27 +0200 Message-ID: To: dev_f , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000eda97005b8fe6a6e" X-Mailman-Approved-At: Sat, 16 Jan 2021 08:49:37 +0000 Subject: Re: [bitcoin-dev] PayJoin adoption X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2021 06:15:41 -0000 --000000000000eda97005b8fe6a6e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Chris, You can add Sparrow Wallet to the list for Sending :) I think one of the barriers to greater Payjoin adoption is the need for a server endpoint on the receiving side. Ideally, all wallets should be able to conduct Payjoin transactions with each other. This would require a different mechanism to exchange the PSBTs, but otherwise the specification should need no amendment. Samourai has implemented their Soroban protocol to do this over Tor, but as far as I know it's not yet documented. Given Payjoin is fee efficient (much more so than coinjoin) and relatively simple to implement, it appears to hold great promise in disrupting blockchain analysis. I'd love to see a standard that wallets can adopt to receive Payjoin transactions without a server endpoint. Craig On Sat, Jan 16, 2021 at 5:13 AM dev_f via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hey Chris, > > I assume that a major reason for the lack of adoption is the lack of > visibility. > I personally first found out about PayJoin when using BTCPayServer for a > donation > and being told by the site that PayJoin was available ( > https://hrf.org/donate-bitcoin/payjoin/). > The wiki page you created is a good starting point. Bringing up the issue > of implementing > PayJoin directly with the companies / in the respective software repos > seems like it would > be a strong first step for greater adoption. Gets more eyes on it in > general. > (Directly contributing to the software by writing an implementation is > obviously the > most helpful, though clearly harder.) > > As a second option, pushing merchants towards accepting Bitcoin > specifically via > software like BTCPayServer, which already supports PayJoin, might be > immensely > helpful when Bitcoin adoption itself rises. > > Fitti > > Sent with ProtonMail Secure Email. > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original = Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 > > On Saturday, January 16th, 2021 at 1:07 AM, Chris Belcher via bitcoin-dev= < > bitcoin-dev@lists.linuxfoundation.org> wrote: > > > PayJoin is an exciting bitcoin privacy technology which has the > > > > > potential to damage the ability of blockchain surveillance to spy on > > > > > bitcoin users and destroy bitcoin's fungibility. A protocol standard ha= s > > > > > already been defined and implemented by a couple of projects such as > > > > > BTCPayServer, Wasabi Wallet, JoinMarket and BlueWallet. > > > > > I've made a wiki page tracking adoption: > > > > > https://en.bitcoin.it/wiki/PayJoin_adoption > > > > > It is similar to the Bech32 adoption page. > > > > > Recently a UK bitcoin exchange shut down due to new regulations, with > > > > > the owner writing a very interesting and relevant blog post that I'll > > > > > quote here: > > > > > > you=E2=80=99re considered suspicious if you used a marketplace and no= t an > > > > > exchange. Coinjoin counts as high risk. Gambling is high risk. As you > > > > > use entities that are paranoid about keeping their coins clean and > > > > > adhering to all the regulations, your risk scores will continue to > > > > > increase and without you even knowing why, your deposits will become > > > > > rejected, you may be asked to supply documents or lose the coins, your > > > > > account may become suspended without you having any clue what you did > > > > > wrong. And quite possibly you didn=E2=80=99t do anything wrong. But tha= t won=E2=80=99t > > > > > matter. > > > > > > The goal post, the risk score threshold will keep moving along this > > > > > trend until the point where you will be afraid of using your personal > > > > > wallet, donating to someone online, receiving bitcoins from anywhere > > > > > except for regulated exchanges. At that point, crypto will be akin to a > > > > > regular bank account. You won=E2=80=99t have a bitcoin wallet, you will= have > > > > > accounts to websites. > > > > > https://blog.bitbargain.com/post/638504004285054976/goodbye > > > > > If we want bitcoin to fulfill its dream of a permissionless money for > > > > > the internet then we'll have to work on this. What can we do to increas= e > > > > > adoption of PayJoin? > > > > > bitcoin-dev mailing list > > > > > bitcoin-dev@lists.linuxfoundation.org > > > > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000eda97005b8fe6a6e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey Chris,

You can add Sparrow Wallet t= o the list for Sending :)

I think one of the barri= ers to greater Payjoin adoption is the need for a server endpoint on the re= ceiving=C2=A0side. Ideally, all wallets should be able to conduct Payjoin t= ransactions with each other. This would require a different mechanism to ex= change the PSBTs, but otherwise the specification should need no amendment.= Samourai has implemented their Soroban protocol to do this over Tor, but a= s far as I know it's not yet documented.=C2=A0

Given Payjoin is fee efficient (much more so than coinjoin) and relatively= simple to implement, it appears to hold great promise in disrupting blockc= hain analysis. I'd love to see a standard that wallets can adopt to rec= eive=C2=A0Payjoin transactions without a server endpoint.

Craig

On Sat, Jan 16, 2021 at 5:13 AM dev_f via bitcoin-dev &l= t;bitcoin-dev@list= s.linuxfoundation.org> wrote:
Hey Chris,

I assume that a major reason for the lack of adoption is the lack of visibi= lity.
I personally first found out about PayJoin when using BTCPayServer for a do= nation
and being told by the site that PayJoin was available (https:= //hrf.org/donate-bitcoin/payjoin/).
The wiki page you created is a good starting point. Bringing up the issue o= f implementing
PayJoin directly with the companies / in the respective software repos seem= s like it would
be a strong first step for greater adoption. Gets more eyes on it in genera= l.
(Directly contributing to the software by writing an implementation is obvi= ously the
most helpful, though clearly harder.)

As a second option, pushing merchants towards accepting Bitcoin specificall= y via
software like BTCPayServer, which already supports PayJoin, might be immens= ely
helpful when Bitcoin adoption itself rises.

Fitti

Sent with ProtonMail Secure Email.

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90

On Saturday, January 16th, 2021 at 1:07 AM, Chris Belcher via bitcoin-dev &= lt;bitcoin-dev@lists.linuxfoundation.org> wrote:

> PayJoin is an exciting bitcoin privacy technology which has the
>

> potential to damage the ability of blockchain surveillance to spy on >

> bitcoin users and destroy bitcoin's fungibility. A protocol standa= rd has
>

> already been defined and implemented by a couple of projects such as >

> BTCPayServer, Wasabi Wallet, JoinMarket and BlueWallet.
>

> I've made a wiki page tracking adoption:
>

> https://en.bitcoin.it/wiki/PayJoin_adoption
>

> It is similar to the Bech32 adoption page.
>

> Recently a UK bitcoin exchange shut down due to new regulations, with<= br> >

> the owner writing a very interesting and relevant blog post that I'= ;ll
>

> quote here:
>

> > you=E2=80=99re considered suspicious if you used a marketplace an= d not an
>

> exchange. Coinjoin counts as high risk. Gambling is high risk. As you<= br> >

> use entities that are paranoid about keeping their coins clean and
>

> adhering to all the regulations, your risk scores will continue to
>

> increase and without you even knowing why, your deposits will become >

> rejected, you may be asked to supply documents or lose the coins, your=
>

> account may become suspended without you having any clue what you did<= br> >

> wrong. And quite possibly you didn=E2=80=99t do anything wrong. But th= at won=E2=80=99t
>

> matter.
>

> > The goal post, the risk score threshold will keep moving along th= is
>

> trend until the point where you will be afraid of using your personal<= br> >

> wallet, donating to someone online, receiving bitcoins from anywhere >

> except for regulated exchanges. At that point, crypto will be akin to = a
>

> regular bank account. You won=E2=80=99t have a bitcoin wallet, you wil= l have
>

> accounts to websites.
>

> https://blog.bitbargain.com/post/638= 504004285054976/goodbye
>

> If we want bitcoin to fulfill its dream of a permissionless money for<= br> >

> the internet then we'll have to work on this. What can we do to in= crease
>

> adoption of PayJoin?
>

> bitcoin-dev mailing list
>

> bitcoin-dev@lists.linuxfoundation.org
>

> https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev__________________________________________= _____
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000eda97005b8fe6a6e--