public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jay Berg <jay@protoblock.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot (and graftroot) complexity
Date: Sat, 19 Sep 2020 07:13:40 +0000	[thread overview]
Message-ID: <212F3FD1-5642-4C61-A135-D74490AECAEA@contoso.com> (raw)
In-Reply-To: <<20200210002011.lelhcdmjejmoh6xv@erisian.com.au>>


> At the time you create a utxo, provided you don't reuse keys, all taproot
> spends are indistinguishable. At the time you spend a taproot utxo,

does reusing keys act differently in taproot than with Pay-to-PubKey-Hash? Or is it the same deal.. same pubkey creates same address? 

Question is: is the security/privacy implications worse when reusing pubkeys with taproot? 

ty
jay  


       reply	other threads:[~2020-09-19  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20200210002011.lelhcdmjejmoh6xv@erisian.com.au>
2020-09-19  7:13 ` Jay Berg [this message]
2020-09-19  8:46 ` [bitcoin-dev] Taproot (and graftroot) complexity Jay Berg
2020-09-19 12:52 Jay Berg
2020-09-20  3:23 ` Lloyd Fournier
  -- strict thread matches above, loose matches on Subject: below --
2020-02-09 20:19 Bryan Bishop
2020-02-09 20:40 ` Matt Corallo
2020-02-09 22:32   ` Antoine Riard
2020-02-10  0:20 ` Anthony Towns
2020-02-10  6:27 ` ZmnSCPxj

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=212F3FD1-5642-4C61-A135-D74490AECAEA@contoso.com \
    --to=jay@protoblock.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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