summaryrefslogtreecommitdiff
path: root/ee/afdafcfcedd929523bbd7c4f9d6e286062ae67
blob: 1b7ab634c21e9d44eaf58d9491d158b204e6e4a6 (plain)
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
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
Return-Path: <willtech@live.com.au>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 83AADC0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 17 Mar 2021 08:13:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 7216442C2A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 17 Mar 2021 08:13:50 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uY3sviCMWNmS
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 17 Mar 2021 08:13:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from APC01-SG2-obe.outbound.protection.outlook.com
 (mail-sg2apc01olkn081f.outbound.protection.outlook.com
 [IPv6:2a01:111:f400:febd::81f])
 by smtp2.osuosl.org (Postfix) with ESMTPS id A9AE940172
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 17 Mar 2021 08:13:47 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=nctTbxw0Td3tkADY0WMMPorZjPDqh5Y5R3r1D6ZhRSG7SO2aNMTBxD+dq5kcvy2coSfMui1C0GmoAbkONiuIRh3Q2Z4/cLXYRSWPl2JTPnMBJwfDLly2v2zKO4N8OqI5AUNPM8JtH/2YRhn+peyzeNnJNbXEVxjdFcV9YXcnTxmuPTgjughG1ylXXobzbG/uhuJzyMiOAUzF2VhxcPaXsP/yXegZ5aNh82ew/gVVWK1dt/xZmihYe0Ri3MkRMPVqEjTjlQSLsKxyJFt2RpWQyscP0NzqRScrJ5ON2IItb9Kd91NL2M7w3bJfdKdMmzlvfLjMiR7PxQm3QL1bgSXIOA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; 
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=/zijv4hdeguPhB1+uQ5vB27YdWyg+xgJjfnyIppMlX8=;
 b=JScplyoDrWqXxqkstGwKNl/PYMl6bv1Uu/Lm6Thtdytp/pbT/po1rou3EfUwU0ZfQJAJ41AA0vhkPKFktqRaPSoVdQ429YYP3hTuB778YLa4vzYmJoS7o4T49izm28X/NmRYLgoX1YHZsA2VAphXxHyM7fJqqx1/3Uw0Qmp6+JgaT6nZP0cbJ4+pG9mYywggWwnkf7qKEbM0DEOo3+AdMFA2v1wo7XB/bXLL0Uxup1ZI7GR+B8QzmPHV+P5Bg1HfJVipygmPk9RXPlcTIcwXrC0dObtzISBUP0mPX8MiYjKWFDtius0uNGEXylokMCDk+pIVabApeuV/C73eU8LdOg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none;
 dkim=none; arc=none
Received: from PU1APC01FT007.eop-APC01.prod.protection.outlook.com
 (2a01:111:e400:7ebe::53) by
 PU1APC01HT086.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebe::387)
 with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.31; Wed, 17 Mar
 2021 08:13:36 +0000
Received: from PS2P216MB0914.KORP216.PROD.OUTLOOK.COM (2a01:111:e400:7ebe::52)
 by PU1APC01FT007.mail.protection.outlook.com
 (2a01:111:e400:7ebe::99) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.18 via Frontend
 Transport; Wed, 17 Mar 2021 08:13:36 +0000
Received: from PS2P216MB0914.KORP216.PROD.OUTLOOK.COM
 ([fe80::dd49:6c2d:8e1e:f4a8]) by PS2P216MB0914.KORP216.PROD.OUTLOOK.COM
 ([fe80::dd49:6c2d:8e1e:f4a8%2]) with mapi id 15.20.3933.033; Wed, 17 Mar 2021
 08:13:36 +0000
From: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
To: DA Williamson <damian@willtech.com.au>, ZmnSCPxj <ZmnSCPxj@protonmail.com>
Thread-Topic: [bitcoin-dev] Taproot NACK
Thread-Index: AQHXClsrfqw3JMU0H0Sw+d7oy0zq2KpsMoeAgAFEgSuAABmNgIAAwa8kgAFwAQCAAN8YgIABhuXegBPWUICAAJ7ZgIABFRAAgABCKZk=
Date: Wed, 17 Mar 2021 08:13:36 +0000
Message-ID: <PS2P216MB09140E189C0873B4232F54359D6A9@PS2P216MB0914.KORP216.PROD.OUTLOOK.COM>
References: <SL2P216MB0089B70AEDD58F2EBC46B4309D9A9@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
 <A326C6D2-7C6E-42A2-93C9-DC7647BB09B6@voskuil.org>
 <170b27c0-436f-c440-e3c3-f9577b764972@riseup.net>
 <SL2P216MB00896086AA80DE1A98293C469D989@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
 <Wz83obOLCjtbO-rIDw9mHM0ObBrE10y1rLg8vbEyp5BIxtfzlUJyLlnPZ-RWnvsKzJaKRe4bo7hnjlJnwL4-g7HyRNa6TvL_Y-gBQ12ifCg=@protonmail.com>
 <932f2f2866cac087a207f8757c9df4b776ccdb04.camel@willtech.com.au>,
 <4ltFpTt8QxX44nedimzJ7J4F1bIhwxb9rbqf1DeGlYX8W7CduYCy64miuq2IIjee_K5rBV6ofEPzdYQniEq6IR4I7ZO5ENlk9z-mQPs-YZE=@protonmail.com>
In-Reply-To: <4ltFpTt8QxX44nedimzJ7J4F1bIhwxb9rbqf1DeGlYX8W7CduYCy64miuq2IIjee_K5rBV6ofEPzdYQniEq6IR4I7ZO5ENlk9z-mQPs-YZE=@protonmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:04BFD776216879DB8A7660C49900285C5015BC4B1CAFB816823251C385762121;
 UpperCasedChecksum:EC840E27F8C26905D8DF3627772216DB9A9D24E3DCAC3D5BA6DB180D8B16A4C1;
 SizeAsReceived:7583; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [lBLMLEdZ24J0D4sentLkrfRTHB7H187i]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: f5e83d55-66fa-4919-29ea-08d8e91c90b5
x-ms-traffictypediagnostic: PU1APC01HT086:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mWt9B0s5g4hap7w1Vyxd2o7YHJgqd4tblIyUxTCOtJfLKFp4dWoS1gfHg+ka3GVLFYCPEcMjs/U1UX/8+m/HgO2FOko3zTnBmSjR/1ySCkQ9PG+5l0lDjH4OCdE35MntfjaOvUlUHrLUHU0i/PSnyTCzqeXee+vuAdc6Awb5KVWZIEFbA2/7OYF952mItgf46Xss7fvfHzIXP2nrXG+UOX+ll++E7ItdLeF3xwQGQzwKVUHtXPwFMWpnQdoHl6KfTn3fCJXDf92QAgEWLrOYglPr8DzXeidKzZeQ8L5CD0kJRt8HYAoXgw7hxeBJ8dsDiZ2Co/Kx1aY49WfRsFMkp0eXETh03dsDBuPReEejCgPlp1B0bJFMshvOT1hfXbtiMlx8SOiKvOwvJDd7W/asPLiu0VWmkXAFS0egO3yANUC2Wn01B1PLI/RMis+vrqPO
x-ms-exchange-antispam-messagedata: ufX7B03e4LLzjqqQk16HjT2S99tEXHuITMOmGq4MZH5wVoleTTIjWUSkX28ojjItKpVwIz2HJaMQTirMNTXH5Z9+YY4AjChgq1msqjCKkGBuoz0XikAmFI2Al/u9lUAyet7vOShIyGFN7rb2CdInHQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
 boundary="_000_PS2P216MB09140E189C0873B4232F54359D6A9PS2P216MB0914KORP_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: PU1APC01FT007.eop-APC01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: f5e83d55-66fa-4919-29ea-08d8e91c90b5
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2021 08:13:36.8373 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT086
X-Mailman-Approved-At: Wed, 17 Mar 2021 19:17:46 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
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: Wed, 17 Mar 2021 08:13:50 -0000

--_000_PS2P216MB09140E189C0873B4232F54359D6A9PS2P216MB0914KORP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Good afternoon,

That is not desirable since yourself and I cannot prove the property of the=
 UTXO when it is further spent unless we can ourselves scrutinize it.

We have had this conversation before where you approach your reply to resol=
ve that I have offered disagreement and I try to explain I am not disagreei=
ng and yet there should be found some common ground. Can this improve?

KING JAMES HRMH
Great British Empire

Regards,
The Australian
LORD HIS EXCELLENCY JAMES HRMH (& HMRH)
of Hougun Manor & Glencoe & British Empire
MR. Damian A. James Williamson
Wills

et al.


Willtech
www.willtech.com.au
www.go-overt.com
and other projects

earn.com/willtech
linkedin.com/in/damianwilliamson


m. 0487135719
f. +61261470192


This email does not constitute a general advice. Please disregard this emai=
l if misdelivered.
________________________________
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Sent: Wednesday, 17 March 2021 3:11 PM
To: DA Williamson <damian@willtech.com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>; LO=
RD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
Subject: Re: [bitcoin-dev] Taproot NACK

Good morning JAMES,

> Good Afternoon,
>
> Verifiable and independantly verifiable are not the same. Independantly
> scrutinable means any public can scrutinise blockchain to determine it
> is honest. It does not rely on involved parties but insistently on the
> data published in the blockchain.

The involved parties ultimately publish the data on the blockchain, and the=
 result is independently validatable.
All that each involved party has to do is validate for itself that it does =
not lose any funds, and, by the operation of math, the summary result does =
not result in any loss (or creation) of funds, thus CoinJoin cannot lead to=
 fraud.

I do not see much of a point in your objection here.
For example, in the case of Lightning, the individual payments made by the =
participants in the channel cannot be verified by anyone else (they can lie=
 about the payments that occurred on their channel).
But both participants in the channel need to agree on a single result, and =
it is that summary result that is independently verified onchain and publis=
hed.

Indeed, one major technique for privacy improvement in Bitcoin is the simpl=
e technique of creating summaries of multiple actions without revealing det=
ails.
Such a general class of techniques works by reducing the data pushed onchai=
n which provides both (a) scale because less data on chain and (b) privacy =
because less data is analyzable onchain.

Basically ---

1.  The entire point of a public blockchain is to prevent uncontrolled forg=
ery of the coin.
    Only particular rules allow construction of new coins (in Bitcoin, the =
mining subsidy).
2.  Various techniques can be used to support the above central point.
    * The simplest is to openly publish every amount value in cleartext.
      * However, this is not necessarily the ***only*** acceptable way to a=
chieve the goal!
      * Remember, the point is to prevent uncontrolled forgery.
        The point is **not** mass surveillance.
    * Another method would be to openly publish **summaries** of transactio=
ns, such as by Lightning Network summarizing the result of multiple payment=
s.
      * CoinJoin is really just a way to summarize multiple self-payments.
    * Another method would be to use homomorphisms between a cleartext and =
a ciphertext, and publish only the ciphertext (which can be independently v=
erified as correctly being added together and that inputs equal outputs plu=
s fees).

No privacy technique worth discussing and development in Bitcoin gets aroun=
d the above point, and thus fraud cannot be achieved with those (at least i=
f we define fraud simply as "those who control the keys control the coins" =
--- someone stealing a copy of your privkeys is beyond this definition of f=
raud).
Any privacy improvement Taproot buys (mostly in LN, but also some additiona=
l privacy for CoinSwap) will still not allow fraud.

Regards,
ZmnSCPxj

--_000_PS2P216MB09140E189C0873B4232F54359D6A9PS2P216MB0914KORP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Good afternoon,</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
That is not desirable since yourself and I cannot prove the property of the=
 UTXO when it is further spent unless we can ourselves scrutinize it.<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
We have had this conversation before where you approach your reply to resol=
ve that I have offered disagreement and I try to explain I am not disagreei=
ng and yet there should be found some common ground. Can this improve?</div=
>
<div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div id=3D"Signature">
<div>
<div></div>
<div></div>
<div></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<div>KING JAMES HRMH</div>
<div>Great British Empire</div>
<div><br>
</div>
<div>Regards,
<div>The Australian</div>
<div>LORD HIS EXCELLENCY JAMES HRMH (&amp; HMRH)</div>
<div>of Hougun Manor &amp; Glencoe &amp; British Empire</div>
<div>MR. Damian A. James Williamson</div>
<div>Wills</div>
<div><br>
</div>
<div>et al.</div>
<div><br>
</div>
<div>&nbsp;</div>
<div>Willtech</div>
<div>www.willtech.com.au</div>
<div>www.go-overt.com</div>
<div>and other projects</div>
<div>&nbsp;</div>
<div>earn.com/willtech</div>
<div>linkedin.com/in/damianwilliamson</div>
<div><br>
</div>
<div><br>
</div>
<div>m. 0487135719</div>
<div>f. +61261470192</div>
<div><br>
</div>
<div><br>
</div>
<span style=3D"font-size: 10pt;">This email does not constitute a general a=
dvice. Please disregard this email if misdelivered.</span><br>
</div>
<div></div>
</div>
</div>
</div>
</div>
<div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=
=3D"Calibri, sans-serif" color=3D"#000000"><b>From:</b> ZmnSCPxj &lt;ZmnSCP=
xj@protonmail.com&gt;<br>
<b>Sent:</b> Wednesday, 17 March 2021 3:11 PM<br>
<b>To:</b> DA Williamson &lt;damian@willtech.com.au&gt;<br>
<b>Cc:</b> Bitcoin Protocol Discussion &lt;bitcoin-dev@lists.linuxfoundatio=
n.org&gt;; LORD HIS EXCELLENCY JAMES HRMH &lt;willtech@live.com.au&gt;<br>
<b>Subject:</b> Re: [bitcoin-dev] Taproot NACK</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt"=
>
<div class=3D"PlainText">Good morning JAMES,<br>
<br>
&gt; Good Afternoon,<br>
&gt;<br>
&gt; Verifiable and independantly verifiable are not the same. Independantl=
y<br>
&gt; scrutinable means any public can scrutinise blockchain to determine it=
<br>
&gt; is honest. It does not rely on involved parties but insistently on the=
<br>
&gt; data published in the blockchain.<br>
<br>
The involved parties ultimately publish the data on the blockchain, and the=
 result is independently validatable.<br>
All that each involved party has to do is validate for itself that it does =
not lose any funds, and, by the operation of math, the summary result does =
not result in any loss (or creation) of funds, thus CoinJoin cannot lead to=
 fraud.<br>
<br>
I do not see much of a point in your objection here.<br>
For example, in the case of Lightning, the individual payments made by the =
participants in the channel cannot be verified by anyone else (they can lie=
 about the payments that occurred on their channel).<br>
But both participants in the channel need to agree on a single result, and =
it is that summary result that is independently verified onchain and publis=
hed.<br>
<br>
Indeed, one major technique for privacy improvement in Bitcoin is the simpl=
e technique of creating summaries of multiple actions without revealing det=
ails.<br>
Such a general class of techniques works by reducing the data pushed onchai=
n which provides both (a) scale because less data on chain and (b) privacy =
because less data is analyzable onchain.<br>
<br>
Basically ---<br>
<br>
1.&nbsp; The entire point of a public blockchain is to prevent uncontrolled=
 forgery of the coin.<br>
&nbsp;&nbsp;&nbsp; Only particular rules allow construction of new coins (i=
n Bitcoin, the mining subsidy).<br>
2.&nbsp; Various techniques can be used to support the above central point.=
<br>
&nbsp;&nbsp;&nbsp; * The simplest is to openly publish every amount value i=
n cleartext.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * However, this is not necessarily the ***on=
ly*** acceptable way to achieve the goal!<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Remember, the point is to prevent uncontro=
lled forgery.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The point is **not** mass survei=
llance.<br>
&nbsp;&nbsp;&nbsp; * Another method would be to openly publish **summaries*=
* of transactions, such as by Lightning Network summarizing the result of m=
ultiple payments.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * CoinJoin is really just a way to summarize=
 multiple self-payments.<br>
&nbsp;&nbsp;&nbsp; * Another method would be to use homomorphisms between a=
 cleartext and a ciphertext, and publish only the ciphertext (which can be =
independently verified as correctly being added together and that inputs eq=
ual outputs plus fees).<br>
<br>
No privacy technique worth discussing and development in Bitcoin gets aroun=
d the above point, and thus fraud cannot be achieved with those (at least i=
f we define fraud simply as &quot;those who control the keys control the co=
ins&quot; --- someone stealing a copy of your
 privkeys is beyond this definition of fraud).<br>
Any privacy improvement Taproot buys (mostly in LN, but also some additiona=
l privacy for CoinSwap) will still not allow fraud.<br>
<br>
Regards,<br>
ZmnSCPxj<br>
</div>
</span></font></div>
</div>
</body>
</html>

--_000_PS2P216MB09140E189C0873B4232F54359D6A9PS2P216MB0914KORP_--