public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Public key and signature malleability
Date: Sun, 21 Oct 2012 13:05:11 -0400	[thread overview]
Message-ID: <CABsx9T2qC0Sw8VMQk+BPtwNMRUtOwwORWydXz=C79aLSyzchAg@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCouT-ehBtJsAKCUPYgiCJYJ-vh1ysNwENRrSAsANyEJw@mail.gmail.com>

Any objections from other transaction-validating implementations?

I strongly support more precisely defining the transaction validity
rules by changing the reference implementation.

-- 
--
Gavin Andresen



  reply	other threads:[~2012-10-21 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 17:55 [Bitcoin-development] Public key and signature malleability Pieter Wuille
2012-10-20 18:34 ` Gregory Maxwell
2012-10-21  6:47 ` Wladimir
2012-10-21 17:05   ` Gavin Andresen [this message]
2012-10-21 18:47     ` Mike Hearn
2012-10-21 18:48     ` Stefan Thomas

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='CABsx9T2qC0Sw8VMQk+BPtwNMRUtOwwORWydXz=C79aLSyzchAg@mail.gmail.com' \
    --to=gavinandresen@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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