From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id E2E74C000A for ; 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 ; 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 ; 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 ; 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 ) 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 ) id 1lM83B-001YLh-O9; Tue, 16 Mar 2021 04:39:51 -0700 Message-ID: <932f2f2866cac087a207f8757c9df4b776ccdb04.camel@willtech.com.au> From: DA Williamson To: ZmnSCPxj , Bitcoin Protocol Discussion , LORD HIS EXCELLENCY JAMES HRMH Date: Tue, 16 Mar 2021 22:39:47 +1100 In-Reply-To: References: <170b27c0-436f-c440-e3c3-f9577b764972@riseup.net> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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