From: Keagan McClelland <keagan.mcclelland@gmail•com>
To: LORD HIS EXCELLENCY JAMES HRMH <willtech@live•com.au>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
Date: Wed, 10 Mar 2021 17:47:37 -0700 [thread overview]
Message-ID: <CALeFGL2oNzuUx=aYbqtEknhJ1wviof2neB7eFwBBJ_4iA0wOMw@mail.gmail.com> (raw)
In-Reply-To: <SL2P216MB0089B36FF0EFAB9958E4DA5B9D919@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]
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 <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 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 <bitcoin-dev-bounces@lists•linuxfoundation.org> 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 <bitcoin-dev@lists•linuxfoundation.org>
> *Subject:* Re: [bitcoin-dev] Taproot NACK
>
> 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/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 5216 bytes --]
next prev parent reply other threads:[~2021-03-11 0:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 3:23 LORD HIS EXCELLENCY JAMES HRMH
2021-02-27 16:14 ` Jeremy
2021-02-28 11:36 ` LORD HIS EXCELLENCY JAMES HRMH
2021-02-28 13:07 ` Ariel Lorenzo-Luaces
2021-03-01 1:34 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-01 22:37 ` Eric Voskuil
2021-03-02 1:16 ` Daniel Edgecumbe
2021-03-03 3:06 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:58 ` eric
2021-03-03 16:30 ` micaroni
2021-03-03 14:49 ` Erik Aronesty
2021-03-04 5:06 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-05 14:04 ` Ryan Grant
2021-03-10 6:34 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-11 0:47 ` Keagan McClelland [this message]
2021-03-12 13:04 ` R E Broadley
2021-03-12 22:30 ` Eric Voskuil
2021-03-14 10:13 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-14 18:41 ` Aymeric Vitte
2021-03-17 4:19 ` ZmnSCPxj
2021-03-17 5:46 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17 7:14 ` Eric Voskuil
2021-03-02 11:56 ` Chris Belcher
2021-03-03 11:22 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-16 2:11 ` ZmnSCPxj
2021-03-16 11:39 ` DA Williamson
2021-03-17 4:11 ` ZmnSCPxj
2021-03-17 8:13 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17 9:32 ` ZmnSCPxj
2021-03-18 1:10 ` DA Williamson
2021-03-03 2:54 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:55 ` eric
2021-03-04 4:53 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 14:32 ` Thomas Hartman
2021-03-04 5:05 ` LORD HIS EXCELLENCY JAMES HRMH
[not found] <SL2P216MB008922741210CC853A51A5A19D979@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
2021-03-04 7:46 ` Eric Voskuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALeFGL2oNzuUx=aYbqtEknhJ1wviof2neB7eFwBBJ_4iA0wOMw@mail.gmail.com' \
--to=keagan.mcclelland@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=willtech@live$(echo .)com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox