From: Tim Ruffing <crypto@timruffing•de>
To: vjudeu <vjudeu@gazeta•pl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Sum of the keys attack on taproot
Date: Sat, 15 May 2021 22:25:23 +0200 [thread overview]
Message-ID: <13a8be987fc22ecc6284de4b84ef5310f2cd420c.camel@timruffing.de> (raw)
In-Reply-To: <131606955-6366ea10aec2eec765339d72e7c936ab@pmq5v.m5r2.onet>
On Sat, 2021-05-15 at 12:21 +0200, vjudeu via bitcoin-dev wrote:
> All that is needed is producing a signature matching the sum of the
> public keys used in taproot, which is "(a+b-a)*G",
This is simply not true.
Taproot does not enable this, or any other form of "cross-input
aggregation", i.e., spending multiple UTXOs with a single signature.
Tim
next prev parent reply other threads:[~2021-05-15 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 10:21 vjudeu
2021-05-15 20:25 ` Tim Ruffing [this message]
2021-05-15 20:35 ` Ruben Somsen
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=13a8be987fc22ecc6284de4b84ef5310f2cd420c.camel@timruffing.de \
--to=crypto@timruffing$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/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