public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
To: Jeremy <jlrubin@mit.edu>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
Date: Sun, 28 Feb 2021 11:36:37 +0000	[thread overview]
Message-ID: <SL2P216MB0089322359FD1FC4C89AB1619D9B9@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAD5xwhhxw7RhwMWSxa76HZqefpVcJidVpzE7Vbzk+hsD6zfUHQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4430 bytes --]

Good Evening,

Thank-you for your advice @JeremyRubin<https://twitter.com/JeremyRubin> on the basis you advise, "Taproot does not enable monero-like privacy features", I am prepred to withdraw my NACK notably that the existing feeatures of Bitcoin MUST be maintained, and whereby the UTXO of a transaction is identifiable, the PayTo Address, and the amount all without any obfuscation.

Lightning does not really provide obfuscation, it provides a result of a subset of transactions although the operation of the channel is observable to the parties.

The reports I were reading concerning the supposed operation of Taproot published in a public media channel may have been speculation or misinformation nonetheless it is prudent to conditionally reply as you see that I have. It is important not to allow things to slip through the cracks. As you may believe may astute reviewers could make a full disclosure to this list it is not to be expected.

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<mail://local/Sent/www.willtech.com.au>
www.go-overt.com<mail://local/Sent/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: Jeremy <jlrubin@mit.edu>
Sent: Sunday, 28 February 2021 3:14 AM
To: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>; Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK

I have good news for you: Taproot does not enable monero-like privacy features any moreso than already exist in Bitcoin today. At its core, taproot is a way to make transactions with embedded smart contracts less expensive, done so in a manner that may marginally improve privacy dependent on user behavior (but not in the monero-like way you mention). For example, it makes it possible for lightning channels to look structurally similar to single key wallets, but it does nothing inherently to obfuscate the transaction graph as in monero.

Such "monero-like" transaction graph obfuscation may already exist in Bitcoin via other techniques (coinjoin, payjoin, coinswap, lightning, etc) with or without Taproot, so the point is further moot.

Do you have a source on your reporting?

You may wish to rescind your nack.


--
@JeremyRubin<https://twitter.com/JeremyRubin><https://twitter.com/JeremyRubin>


On Sat, Feb 27, 2021 at 5:46 AM LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org<mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
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<http://www.willtech.com.au>
www.go-overt.com<http://www.go-overt.com>
and other projects

earn.com/willtech<http://earn.com/willtech>
linkedin.com/in/damianwilliamson<http://linkedin.com/in/damianwilliamson>


m. 0487135719
f. +61261470192


This email does not constitute a general advice. Please disregard this email if misdelivered.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org<mailto:bitcoin-dev@lists.linuxfoundation.org>
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

[-- Attachment #2: Type: text/html, Size: 14626 bytes --]

  reply	other threads:[~2021-02-28 11:36 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 [this message]
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=SL2P216MB0089322359FD1FC4C89AB1619D9B9@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM \
    --to=willtech@live.com.au \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jlrubin@mit.edu \
    /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