summaryrefslogtreecommitdiff
path: root/a2/205134759423c0626fb9b3f1342c698b24c12e
blob: 9b74bc299e8783dab02923c77fdca1d72767a1d7 (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
Return-Path: <damian@willtech.com.au>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id E2E74C000A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 16 Mar 2021 11:41:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id D135B42FF6
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 16 Mar 2021 11:41:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001,
 RCVD_IN_MSPIKE_H2=-0.001, SPF_SOFTFAIL=0.665, T_DKIM_INVALID=0.01]
 autolearn=no autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=neutral
 reason="invalid (public key: not available)" header.d=willtech.com.au
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 pAJDuCHu0j3b
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 16 Mar 2021 11:41:09 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from out2-41.antispamcloud.com (out2-41.antispamcloud.com
 [185.201.17.41])
 by smtp2.osuosl.org (Postfix) with ESMTPS id CAB3C42D1E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 16 Mar 2021 11:41:08 +0000 (UTC)
Received: from s110.servername.online ([204.44.192.22])
 by mx134.antispamcloud.com with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128)
 (Exim 4.92) (envelope-from <damian@willtech.com.au>)
 id 1lM845-0016eB-Cx; Tue, 16 Mar 2021 12:40:54 +0100
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
 d=willtech.com.au; s=default; h=Content-Transfer-Encoding:MIME-Version:
 Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID:Sender:
 Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
 Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
 List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
 bh=f4VgJUX+2Q+h2L3miWo8AnZmHa2QYgDc3Ii6G7tg7qY=; b=1bCzPeCGJMDcnof7Db3njQy3XX
 xuzUh669tEj1mtXAqX6yXhy23N2u8e0LWEjlRxkToKw+/b9MtUDJj0uaFe6l+QePlKcDq/C1HWlCw
 Wh4cYXjtsYtu2brhyoPX+rvBZsY0Xe+zvMuVA4ylgs+jxuUG032pxwJVdimt4+ZW4Q5Yv5szMnwJs
 d5a3BE5tQl+qgNhh5w0WaUMh/vWPvQJALG25Y/29yik3rc9XBPgSlCRssP2d/uL8L591oStL6wqRp
 IIrEpBc5dXmoHydZ4k4sTjxR0PHUYtxHHm+pqnocj9/7uovvasXm7NNZQvIz1Upu5jlg3DyGBK15H
 PQlSwyWg==;
Received: from [155.143.183.67] (port=35842 helo=ux533f)
 by s110.servername.online with esmtpsa (TLS1.2) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93)
 (envelope-from <damian@willtech.com.au>)
 id 1lM83B-001YLh-O9; Tue, 16 Mar 2021 04:39:51 -0700
Message-ID: <932f2f2866cac087a207f8757c9df4b776ccdb04.camel@willtech.com.au>
From: DA Williamson <damian@willtech.com.au>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>, Bitcoin Protocol Discussion
 <bitcoin-dev@lists.linuxfoundation.org>, LORD HIS EXCELLENCY JAMES HRMH
 <willtech@live.com.au>
Date: Tue, 16 Mar 2021 22:39:47 +1100
In-Reply-To: <Wz83obOLCjtbO-rIDw9mHM0ObBrE10y1rLg8vbEyp5BIxtfzlUJyLlnPZ-RWnvsKzJaKRe4bo7hnjlJnwL4-g7HyRNa6TvL_Y-gBQ12ifCg=@protonmail.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>
Organization: Willtech
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-OutGoing-Spam-Status: No, score=-1.0
X-Get-Message-Sender-Via: s110.servername.online: authenticated_id:
 damian@willtech.com.au
X-Authenticated-Sender: s110.servername.online: damian@willtech.com.au
X-AuthUser: damian@willtech.com.au
X-Originating-IP: 204.44.192.22
X-Spampanel-Domain: outgoing-shared.hostpapa.com
X-Spampanel-Username: outgoingshared
Authentication-Results: antispamcloud.com; auth=pass (login)
 smtp.auth=outgoingshared@outgoing-shared.hostpapa.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.10)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+fvDE60DYW0dnzzz/xx2OFPUtbdvnXkggZ
 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zgyV9chgUwPamZQHk+R+lKPsT0YdEbZPezIbihu5xq6AWI
 hZI+Y2X7Y8rN1AFRQtujZdIRofwuppKfRmNksh6+EOFL7pzp/tkSUWelD1Cp98NZEjFPzt4HCkAg
 SDeMtwBAQnsLO8OlL77d3bdz3iqGqeqkQmEVjE0C6T0tzvjlNTE4SdfzODOX9HtNgQ5b7+fEXbEo
 Is0h57UMtPUmsa5suJc2qA4XkA4ZomJ1JMp+4IseM7WnjJK/ONW5ucd40qM3Az60u/ioSXOvpAwS
 BGhXxl+/Wzf2h9yazOgFvIXghonLpfhEcZOULfv0mFx881HSA3At4lVR1t94Gdc0HVU98odjyAd2
 lZWAXeawp7csDVZDmQkAxXU5nlwm3OhGAHneVe2N8xJNa2aE84fxk5YNy90aWcRAkyfkq45sUvGY
 uiYQolVDMPf6vdvFUmW33J+xRel4CJUcFaUzp3L6+Zt4pNUOzuR6xPLGAGccQksH3T3ajxgkZDDN
 Ei7Abtm/DWaGkim0A5DjFk2/1KcYL35Sl2zUgRx3tZ7UkK/TZiw0whbAiblZVZAoQGrzL+lZC3bY
 5Qx4fJOk03R5fJtf/Dv/gSdxjDi1ltP+wptveb2IjZfVHNPDquuy8h6ySGzqbVEbMF1LhXOle2l+
 GNkBpJCXaPpeCrkWOIy4XySNK08RP3H/RZfAoo5rnafJmMcvSTDiP69DPPZBsHYK/exHGPQNa8mP
 lnxVIWuBVdZAgvylXeVHDK/d/D3POXDyR0+CAyiOGkg5OY11LG8K3FykxW7+LHgclmgWbNReXMyj
 N+0/EuANhuD8czQsToCw9j8dfLBglnuhp1TWREvTL0aKinQfkSw0as9RXKMs/g/dzKvjaaX51SAF
 ICd9qw2h02kHKqS9DzbIJwtNkBzxKPudgwPtUrEcH960Yb6MpiL+285bId9PCYn27V4VZ+lsFBhB
 eAe+tfK9NcSidnq9JLDcMRPEmFFXfKR4FMzoHIsTcvoEh1ss+n2ffnQxt6aJ7klZab+hEVRYdFbF
 iYyaUIuGboiP50LChpkacC30U4GStVpBB5qXiiviNYE8oXwpilguHaIRsqgwzRH5txwhuft8J0Jq
X-Report-Abuse-To: spam@quarantine10.antispamcloud.com
X-Mailman-Approved-At: Tue, 16 Mar 2021 13:22:59 +0000
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: Tue, 16 Mar 2021 11:41:11 -0000

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 accepted case of P2SH is also a
moot point since we are checking transactions and not where the balance
is but where it has come from. It is not further to P2SH which is not
obfuscation but is indeed publishing to then say that we only need
publicly disclose G3 which is a tangent obfuscation.

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 email if misdelivered.
On Tue, 2021-03-16 at 02:11 +0000, ZmnSCPxj via bitcoin-dev wrote:
> Good morning JAMES,
> 
> > No-one has yet demonstrated that Conjoin or using Wasabi wallet is
> > secure if it relies on third-parties. Are the transaction not
> > forwarded partially signed as with an SPV wallet? So it is possible
> > the SPV server cannot redirect funds if dishonest? SPV wallets are
> > secure producing fully signed transactions. A ConJoin transaction
> > signs for the UTXO and forwards it to be included signed for in
> > another larger transaction with many inputs and outputs
> 
> The above point was not answered, so let me answer this for
> elucidation of you and any readers.
> 
> A CoinJoin transaction is a single transaction with many inputs and
> many outputs.
> 
> Every input must be signed.
> 
> When used to obfuscate, each input has different actual entities
> owning the coin.
> 
> In order to prevent fraud, it is necessary that what total amount
> each entity puts into the transaction, that entity also gets out (in
> freshly-generated addresses, which I hope you do not object to) as an
> output.
> 
> When providing its signature, each entity verifies that its provided
> address exists in some output first before signing out its input.
> 
> The provided signature requires all the inputs and all the outputs to
> exist in the transaction.
> Because of this, it is not possible to take a "partial" signature for
> this transaction, then change the transaction to redirect outputs
> elsewhere --- the signature of previous participants become invalid
> for the modified transaction..
> 
> Thus, the security of the CoinJoin cannot be damaged by a third
> party.
> 
> Third parties involved in popular implementations of CoinJoin (such
> as the coordinator in Wasabi) are nothing more than clerical
> actuaries that take signatures of an immutable document, and any
> attempt by that clerical actuary to change the document also destroys
> any signatures of that document, making the modified document (the
> transaction) invalid.
> 
> > . Also, none of those you mention is inherently a Privacy
> > Technology. Transparency is one of the key articles of value in
> > Bitcoin because it prevents fraud.
> 
> The prevention of fraud simply requires that all addition is
> validatable.
> It does not require that the actual values involved are visible in
> cleartext.
> 
> Various cryptographic techniques already exist which allow the
> verifiable addition of encrypted values ("homomorphisms").
> You can get 1 * G and 2 * G, add the resulting points, and compare it
> to 3 * G and see that you get the same point, yet if you did not know
> exactly what G was used, you would not know that you were checking
> the addition of 1 + 2 = 3.
> That is the basis of a large number of privacy coins.
> 
> At the same time, if I wanted to *voluntarily* reveal this 1 + 2 = 3,
> I could reveal the numbers involved and the point G I used, and any
> validator (including, say, a government taxing authority) can check
> that the points recorded on the blockchain match with what I claimed.
> 
> For the prevention of fraud, we should strive to be as transparent as
> *little* as possible, while allowing users to *voluntarily* reveal
> information.
> 
> 
> Regards,
> ZmnSCPxj
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev