Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id A8025C0001 for ; Thu, 11 Mar 2021 00:47:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 8ED6842FF5 for ; Thu, 11 Mar 2021 00:47:51 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 2z0DEQNHUw1Z for ; Thu, 11 Mar 2021 00:47:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by smtp2.osuosl.org (Postfix) with ESMTPS id 5C11E400C3 for ; Thu, 11 Mar 2021 00:47:50 +0000 (UTC) Received: by mail-wr1-x434.google.com with SMTP id u16so25354934wrt.1 for ; Wed, 10 Mar 2021 16:47:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VWLHsCX2sgLi2+xIO8p30xUG6md43qhqpY5CUEwsQno=; b=fzNVjGatzpD/qf4SsFiNG/TMVs/7sNL7MwfN0i+y44XrTxfyh3eD742FmI4PFlbX5h owWCz3cHZCSW+AGOHixzA0I2YZ/AXfQBsN+kbQEqVn/sCWMU/NfytI4pVy79An/xXTZq QjYF/9cf/LcuXLVFUlZ3k7Tyb35JJ8HWZnpGs9i6yXHzgnzuKhiPMlwOUqHMsYfXoBW9 CV4Y3mEeTPp+yRgTvk+T1EhYd7QGULimGAzy8+gY1hUXSHT+uYUxxMiFykb5Y2Z05J8q kDPmNAH2xobtv+pnltDTcAO5oOTk4h3ao4w5dz9sWkQ9lQF87ej6pw4khNr1VOp6krTG 46Fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VWLHsCX2sgLi2+xIO8p30xUG6md43qhqpY5CUEwsQno=; b=GBN2zvtQTJQVGyXMjfgXEDH16kh1M3fM5fhMqSA49y0+7JAV4nRC6zAjFb45wTX6R2 1Cb1e45SJVEoETwJRyzQVfnZGPZxWm9+/BA7Bl52rztg8DdV38do/qAJ77ClTZ7tnoPd gwNVZoWy+lIonRToUpZoO+5vjjKIZ77fBCFcWBfzk0CrF/StgpFjYr1+2nq60rhSgHih W2VewziIr4Yk7ZGcEpPLLhAO2BqVyAERlu3nlqRcEG+xGZQ9C6q2ze2OE5wkUxZB/xOM E+TAd9c4dsTKXbr1Hr36YDcZC8lRalOO5mSF7JnYrUQq7elEQ0BvWOiP3Dv47PM1Qm40 lh5A== X-Gm-Message-State: AOAM532fQXgjMjZldjZiqVxrFawi3oiLMO3OSr0Q3HANRMhAOXz02rlO nBT78uYsVNBpYPCaRNwSbHXynIgrgmDvmY/EXPQ= X-Google-Smtp-Source: ABdhPJyZGmjIieQWvdKNw9YKTBlKqVdBY54QXax54dNLcrCh/kO9WC9fwTJPC37YgK0ulSX+ZjrIzkXKUFVC0vb3utI= X-Received: by 2002:a5d:4e85:: with SMTP id e5mr6143465wru.218.1615423668597; Wed, 10 Mar 2021 16:47:48 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Keagan McClelland Date: Wed, 10 Mar 2021 17:47:37 -0700 Message-ID: To: LORD HIS EXCELLENCY JAMES HRMH , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000edb69505bd3821e2" X-Mailman-Approved-At: Thu, 11 Mar 2021 00:49:01 +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: Thu, 11 Mar 2021 00:47:51 -0000 --000000000000edb69505bd3821e2 Content-Type: text/plain; charset="UTF-8" LORD HIS EXCELLENCY, This isn't different with Taproot either. When you spend a P2SH output you reveal the script. In Taproot you reveal the portion of the script that is relevant to allowing you to spend it. There is no value to specifying the other possible conditions that could have moved the coins because, after all, you aren't invoking those clauses to move the coins. I am showing you my fingertip, and pointing to my finger tip, the palm is not relevant. Keagan On Wed, Mar 10, 2021 at 2:11 AM LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev wrote: > Good Afternoon, > > You cannot liken the ability to scrutinise the public ledger to be the > same as hiding information, it is like showing your palm while you are > pointing at the back of your hand. The advice that I have is P2SH is > scrutable once the UTXO is spent. Also, there is no public ledger > obfuscation in creating new addresses, there is a plausible reduction in > transaction linkage. > > 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. > ------------------------------ > *From:* bitcoin-dev on > behalf of Ryan Grant via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> > *Sent:* Saturday, 6 March 2021 1:04 AM > *To:* Bitcoin Protocol Discussion > *Subject:* Re: [bitcoin-dev] Taproot NACK > > On Thu, Mar 4, 2021 at 8:48 PM LORD HIS EXCELLENCY JAMES HRMH via > bitcoin-dev wrote: > > My concern was that the more complex scripts allow obfuscation of the > Pay To address > > This is no different from options available in P2SH, or from the > obfuscation achieved by generating a new address for a payment. > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000edb69505bd3821e2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
LORD HIS EXCELLENCY,

This isn'= ;t different with Taproot either. When you spend a P2SH output you reveal t= he script. In Taproot you reveal the portion of the script that is relevant= to allowing you to spend it. There is no value to specifying the other pos= sible conditions that could have moved the coins because, after all, you ar= en't invoking those clauses to move the coins. I am showing you my fing= ertip, and pointing to my finger tip, the palm is not relevant.

Keagan

On Wed, Mar 10, 2021 at 2:11 AM LORD HIS EXCELLENCY JAM= ES HRMH via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
Good Afternoon,

You cannot liken the ability to scrutinise the public ledger to be the same= as hiding information, it is like showing your palm while you are pointing= at the back of your hand. The advice that I have is P2SH is scrutable once= the UTXO is spent. Also, there is no public ledger obfuscation in creating new addresses, there is a plau= sible reduction in transaction linkage.

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.

=C2=A0
Willtech
and other projects
=C2=A0


m. 0487135719
f. +61261470192


This email does not constitute a general adv= ice. Please disregard this email if misdelivered.
Fro= m: bitcoin-dev <bitcoin-dev-bounces@lists.linuxfoundation.or= g> on behalf of Ryan Grant via bitcoin-dev <bitcoin-dev@lists.lin= uxfoundation.org>
Sent: Saturday, 6 March 2021 1:04 AM
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundatio= n.org>
Subject: Re: [bitcoin-dev] Taproot NACK
=C2=A0
On Thu, Mar 4, 2021 at 8:48 PM LORD HIS EXCELLENCY JAMES HRMH via
bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> My concern was that the more complex scripts allow obfuscation of the = Pay To address

This is no different from options available in P2SH, or from the
obfuscation achieved by generating a new address for a payment.
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoi= n-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000edb69505bd3821e2--