1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
|
Return-Path: <dev@fitti.io>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id B0FA7C013A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Jan 2021 03:02:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by fraxinus.osuosl.org (Postfix) with ESMTP id 97D3F86A8F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Jan 2021 03:02:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id vd9L7TmJobsq
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Jan 2021 03:02:37 +0000 (UTC)
X-Greylist: delayed 00:09:40 by SQLgrey-1.7.6
Received: from mail-41104.protonmail.ch (mail-41104.protonmail.ch
[185.70.41.104])
by fraxinus.osuosl.org (Postfix) with ESMTPS id 835AA86A37
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Jan 2021 03:02:37 +0000 (UTC)
Received: from mail-03.mail-europe.com (mail-03.mail-europe.com
[91.134.188.129])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits))
(No client certificate requested)
by mail-41104.protonmail.ch (Postfix) with ESMTPS id 3058923F17CF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 16 Jan 2021 02:52:54 +0000 (UTC)
Authentication-Results: mail-41104.protonmail.ch;
dkim=pass (2048-bit key) header.d=fitti.io header.i=@fitti.io
header.b="OxrbEwDZ"
Date: Sat, 16 Jan 2021 02:52:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fitti.io;
s=protonmail3; t=1610765563;
bh=EePJB2+b1y9hbwux3IzmhgatRosn+fgc7FuE3vsd/WM=;
h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
b=OxrbEwDZi8wmPsrWIfGFEeRllROJhUB/PNVWKI9FkuMv1SccoSRlhmVF0T83eO1FH
0ShtY0D7ACAuBg/mcCqHtB7oK4rNoXn99H/xRqDCKUEpjJDuGigXU50jnrONSX0GAu
+TGblQoWDhiOQCzML13Yb/MrQLWluHFRlpVlQ27sE2J8Z8yr7KodSENAhAQRe8IXdU
SeFb2ulXjXhGBpkkArZY18Iwd0d4oc3WT3fMv+seG8smOQMmd3Zi/L9UkqM2GXJoYR
RrY3b81isvGgsNU0cAXKtQDeaJKJHIe/X/AQC6l+qO7tg7HqDQ86bDmsPkC2hxpGCf
wVznOCidn5shg==
To: Chris Belcher <belcher@riseup.net>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: dev_f <dev@fitti.io>
Reply-To: dev_f <dev@fitti.io>
Message-ID: <MRPJ51OJKiOHFfMaz1Y0XC-BWAyJqQFRQttP5sApf8_gtlVk3k-jziFACTwFZ3QPK3jFZ9yaVmFXf9BuN-dbo3J1JrWjLTkk3wKw1LfocKk=@fitti.io>
In-Reply-To: <2b8ba39f-8fe9-8800-b8e6-47ca263774d5@riseup.net>
References: <2b8ba39f-8fe9-8800-b8e6-47ca263774d5@riseup.net>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
micalg=pgp-sha512;
boundary="---------------------2e6662e3881502818242b8f9e2b6fb2b";
charset=utf-8
X-Mailman-Approved-At: Sat, 16 Jan 2021 03:13:12 +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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jan 2021 03:02:41 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
-----------------------2e6662e3881502818242b8f9e2b6fb2b
Content-Type: multipart/mixed;boundary=---------------------bec6bee05b79bfb9601bcf256fe73266
-----------------------bec6bee05b79bfb9601bcf256fe73266
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8
Hey Chris,
I assume that a major reason for the lack of adoption is the lack of visib=
ility.
I personally first found out about PayJoin when using BTCPayServer for a d=
onation
and being told by the site that PayJoin was available (https://hrf.org/don=
ate-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 see=
ms like it would
be a strong first step for greater adoption. Gets more eyes on it in gener=
al.
(Directly contributing to the software by writing an implementation is obv=
iously the
most helpful, though clearly harder.)
As a second option, pushing merchants towards accepting Bitcoin specifical=
ly via
software like BTCPayServer, which already supports PayJoin, might be immen=
sely
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 M=
essage =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 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=E2=80=99re 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=E2=80=99t do anything wrong. But that=
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 increase
> =
> adoption of PayJoin?
> =
> bitcoin-dev mailing list
> =
> bitcoin-dev@lists.linuxfoundation.org
> =
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-----------------------bec6bee05b79bfb9601bcf256fe73266
Content-Type: application/pgp-keys; filename="publickey - dev@fitti.io - 0xC413574E.asc"; name="publickey - dev@fitti.io - 0xC413574E.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - dev@fitti.io - 0xC413574E.asc"; name="publickey - dev@fitti.io - 0xC413574E.asc"
LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tDQpWZXJzaW9uOiBPcGVuUEdQLmpz
IHY0LjEwLjkNCkNvbW1lbnQ6IGh0dHBzOi8vb3BlbnBncGpzLm9yZw0KDQp4ak1FWGV3QkpoWUpL
d1lCQkFIYVJ3OEJBUWRBdEJ0aTU4NXBHSEdLc3BjN2sybG5KSUpLcW9oeTlTanUNCnQ0NW83Q0J3
aFdQTkcyUmxka0JtYVhSMGFTNXBieUE4WkdWMlFHWnBkSFJwTG1sdlBzSjNCQkFXQ2dBZg0KQlFK
ZDdBRW1CZ3NKQndnREFnUVZDQW9DQXhZQ0FRSVpBUUliQXdJZUFRQUtDUkMzNXA0UWxpTEM0Q3cx
DQpBUG9EWGgvVEI0MjdrcjJJUUxyb2NDNDR4bStLdVo2cUNFOHR1Tzh1OGpIMWJnRCtQMGgrLzUw
ZXJjbkUNCmVSWVlTS3J2KzUzR0orTDZBMzkrWmZ4YVprbW5UZ3JPT0FSZDdBRW1FZ29yQmdFRUFa
ZFZBUVVCQVFkQQ0KVkxLZ3BVamZoN0lkMDRub1VJRk4weTNGdjFJVWpTLzJpZ1NTeUV0aHIzVURB
UWdId21FRUdCWUlBQWtGDQpBbDNzQVNZQ0d3d0FDZ2tRdCthZUVKWWl3dUF4cEFFQWxwWlRES3Nh
cHE2ckJWR1NGN3ZCWXBBeHBRQTANClZubDlQMDVSMk5kVlp1QUEvMHNQRGVrTFlubjlBL09OeHN1
bENlMGdrTjZBd3pRVkR0aENUOTVtOGxJSQ0KPW5OWjMNCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZ
IEJMT0NLLS0tLS0NCg==
-----------------------bec6bee05b79bfb9601bcf256fe73266--
-----------------------2e6662e3881502818242b8f9e2b6fb2b
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wnUEARYKAAYFAmACVPIAIQkQt+aeEJYiwuAWIQTEE1dOBidk60R4yc635p4Q
liLC4FPDAP4uF996O2ks15DxESETPrbLNnODv6ovASm9oDYS+ABRqAEA+CbB
irFYzNdtVUS3JQLsp7x3fpsTWrCpAZR79j/88AA=
=yXAr
-----END PGP SIGNATURE-----
-----------------------2e6662e3881502818242b8f9e2b6fb2b--
|
