From: DA Williamson <damian@willtech.com.au>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
Date: Thu, 18 Mar 2021 12:10:38 +1100 [thread overview]
Message-ID: <209bbf55ec070e24ababec0612334efc1ea60741.camel@willtech.com.au> (raw)
In-Reply-To: <lQzKUb3esyrfDpI7iAVpOBcpriqEgyPI305Ck08zMrcf8MDlWCn6bwccqgeUghcri2a80b1P4ys_y-W0wubvVpvbihKVUPMJUlYw73ZOl7E=@protonmail.com>
Good Morning,
The Bitcoin you are spending must exist in compliance with consensus
so, if the details are obscured then it is not possible for me to
accept your Bitcoin, to say I refuse. Otherwise, it is not possible for
me to see immutably that they exist all the way to coin genesis, they
could be invented in the obfuscation even in the example the received
Bitcoin are discarded as fees and new Bitcoin are invented. In that
case the transaction is not in balance but, without public scrutiny it
is not possible to see.
It is also necesdsary to see who should be able to spend the UTXO to
prevent fraud, so that scrutability allows consensus driven fungibility
to be proven. If the transaction is not available to scrutiny at least
at the level of P2SH where the spend reveals the pay to script with all
the other conditions of consensus then fungibilty does not exist.
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 Wed, 2021-03-17 at 09:32 +0000, ZmnSCPxj wrote:
> What property *needs* to be proven in the first place?
> Given the above, it is not *necessary* to prove *any* property of
*any* UTXO other than the property *this UTXO does not create more
coins than what was designed*.
next prev parent reply other threads:[~2021-03-18 1:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 3:23 [bitcoin-dev] Taproot NACK 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
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 [this message]
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=209bbf55ec070e24ababec0612334efc1ea60741.camel@willtech.com.au \
--to=damian@willtech.com.au \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=willtech@live.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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