From: LORD HIS EXCELLENCY JAMES HRMH <willtech@live•com.au>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Taproot NACK
Date: Wed, 24 Feb 2021 03:23:35 +0000 [thread overview]
Message-ID: <SL2P216MB00896C65DECD973205D17ABE9D9F9@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
Good Afternoon,
It has been reported that Taproot will enable some Monero like features including the ability to hide transactions.
If that is the case I offer a full NACK and let me explain.
A part of the benefit of using Bitcoin is its honesty. The full transaction is published on the blockchain. If that were to change so that transactions may be obfuscated from scrutiny then any government would have unlimited impetus to ban Bitcoin, and speculation has that is the reason India has been reported to have banned cryptocurrencies already.
I am in support of the expanded use case of Bitcoin without harming the established robust fairness and equal equity offered. The core functionality of Bitcoin, its values, must remain unaltered.
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.
[-- Attachment #2: Type: text/html, Size: 3619 bytes --]
next reply other threads:[~2021-02-24 3:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 3:23 LORD HIS EXCELLENCY JAMES HRMH [this message]
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
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=SL2P216MB00896C65DECD973205D17ABE9D9F9@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM \
--to=willtech@live$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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