From: dev_f <dev@fitti.io>
To: Chris Belcher <belcher@riseup.net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] PayJoin adoption
Date: Sat, 16 Jan 2021 02:52:34 +0000 [thread overview]
Message-ID: <MRPJ51OJKiOHFfMaz1Y0XC-BWAyJqQFRQttP5sApf8_gtlVk3k-jziFACTwFZ3QPK3jFZ9yaVmFXf9BuN-dbo3J1JrWjLTkk3wKw1LfocKk=@fitti.io> (raw)
In-Reply-To: <2b8ba39f-8fe9-8800-b8e6-47ca263774d5@riseup.net>
[-- Attachment #1.1: Type: text/plain, Size: 3301 bytes --]
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.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
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 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
>
> the owner writing a very interesting and relevant blog post that I'll
>
> quote here:
>
> > you’re considered suspicious if you used a marketplace and not 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’t do anything wrong. But that won’t
>
> 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’t 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 increase
>
> adoption of PayJoin?
>
> bitcoin-dev mailing list
>
> bitcoin-dev@lists.linuxfoundation.org
>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #1.2: publickey - dev@fitti.io - 0xC413574E.asc --]
[-- Type: application/pgp-keys, Size: 640 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2021-01-16 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 0:07 [bitcoin-dev] PayJoin adoption Chris Belcher
2021-01-16 2:52 ` dev_f [this message]
2021-01-16 6:15 ` Craig Raw
2021-01-18 20:38 ` Lucas Ontivero
2021-01-19 15:44 ` Chris Belcher
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='MRPJ51OJKiOHFfMaz1Y0XC-BWAyJqQFRQttP5sApf8_gtlVk3k-jziFACTwFZ3QPK3jFZ9yaVmFXf9BuN-dbo3J1JrWjLTkk3wKw1LfocKk=@fitti.io' \
--to=dev@fitti.io \
--cc=belcher@riseup.net \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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