From: Lloyd Fournier <lloyd.fourn@gmail.com>
To: Jay Berg <jay@protoblock.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot (and graftroot) complexity
Date: Sun, 20 Sep 2020 13:23:28 +1000 [thread overview]
Message-ID: <CAH5Bsr1vZ_T_4REUriwJ-1gTMN35g3yjEAzq1RYx6xALhtT2RA@mail.gmail.com> (raw)
In-Reply-To: <36F82F07-9650-466F-99EB-09D306BABAEB@protoblock.com>
Hi Jay,
I don't think there's much of a difference in security or privacy.
The advice to avoid key-reuse remains the same and for the same reasons.
LL
On Sat, Sep 19, 2020 at 11:08 PM Jay Berg via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Newb here.. don’t know if "in-reply-to" header is misbehaving.
>
> But this is the OP thread:
>
> [bitcoin-dev] Taproot (and graftroot) complexity
> Anthony Towns aj at erisian.com.au
> Mon Feb 10 00:20:11 UTC 2020
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-February/017622.html
>
> <a href="mailto:bitcoin-dev%40lists.linuxfoundation.org?Subject=Re:%20Re%3A%20%5Bbitcoin-dev%5D%20Taproot%20%28and%20graftroot%29%20complexity&In-Reply-To=%3C20200210002011.lelhcdmjejmoh6xv%40erisian.com.au%3E" title="[bitcoin-dev] Taproot (and graftroot) complexity">aj at erisian.com.au
> </a>
>
> On 9/19/20, 5:35 AM, "bitcoin-dev on behalf of Jay Berg via bitcoin-dev" <bitcoin-dev-bounces@lists.linuxfoundation.org on behalf of bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>
> > 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
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2020-09-20 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 12:52 [bitcoin-dev] Taproot (and graftroot) complexity Jay Berg
2020-09-20 3:23 ` Lloyd Fournier [this message]
[not found] <<20200210002011.lelhcdmjejmoh6xv@erisian.com.au>
2020-09-19 7:13 ` Jay Berg
2020-09-19 8:46 ` Jay Berg
-- 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=CAH5Bsr1vZ_T_4REUriwJ-1gTMN35g3yjEAzq1RYx6xALhtT2RA@mail.gmail.com \
--to=lloyd.fourn@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jay@protoblock.com \
/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