From: Aaron Voisine <voisine@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Small update to BIP 62
Date: Fri, 18 Jul 2014 21:38:16 -0700 [thread overview]
Message-ID: <CACq0ZD4GwDZbEK4oE_BJxN-nDTb_4+hhDFZ0T7xGAi8v3G349A@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSwzx7M9NLjoOgfAgQT2cHmUWYD8hBmwHRRhgG9UgmmhA@mail.gmail.com>
Well, you could always create a transaction with a different signature
hash, say, by changing something trivial like nLockTime, or changing
the order of inputs or outputs. Is that what you're talking about? Or
is there some sophistry I'm ignorant of having to do with the elliptic
curve math in the signature itself?
Aaron Voisine
breadwallet.com
On Fri, Jul 18, 2014 at 6:28 PM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Fri, Jul 18, 2014 at 3:03 PM, Aaron Voisine <voisine@gmail•com> wrote:
>>> 9. New signatures by the sender
>>
>> I'm not suggesting it be required, but it would be possible to
>> mitigate this one by requiring that all signatures deterministically
>> generate k per RFC6979. I'm using this in breadwallet.
>
> Nope.
>
> Your homework assignment is to explain why. :)
next prev parent reply other threads:[~2014-07-19 4:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 15:14 Pieter Wuille
2014-07-18 15:39 ` Mike Hearn
2014-07-18 15:45 ` Pieter Wuille
2014-07-18 17:25 ` Pieter Wuille
2014-07-18 18:10 ` Pieter Wuille
2014-07-18 20:56 ` Wladimir
2014-07-18 22:03 ` Aaron Voisine
2014-07-19 1:28 ` Gregory Maxwell
2014-07-19 4:38 ` Aaron Voisine [this message]
2014-07-19 6:56 ` Gregory Maxwell
2014-07-19 8:34 ` Aaron Voisine
2014-07-19 19:08 ` Aaron Voisine
2014-07-19 14:46 ` Pieter Wuille
2014-07-18 20:51 ` Wladimir
2014-09-01 20:48 ` Gregory Maxwell
2014-09-03 16:34 ` Pieter Wuille
2014-09-07 23:31 ` Pieter Wuille
2014-09-12 16:35 ` Pieter Wuille
2014-09-13 22:45 ` Pieter Wuille
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=CACq0ZD4GwDZbEK4oE_BJxN-nDTb_4+hhDFZ0T7xGAi8v3G349A@mail.gmail.com \
--to=voisine@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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