public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 34: Block v2, Height in Coinbase
Date: Fri, 6 Jul 2012 16:10:42 -0400	[thread overview]
Message-ID: <CAAS2fgTCjmTD8qZoUnyNLhqoga8-E5osEx3qwqSfoWQewBP3Gg@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T39Hj5XSwVxkAw+UxuEyKMnjpAtYtfoLD7KpMuUCiM=Jg@mail.gmail.com>

On Fri, Jul 6, 2012 at 4:02 PM, Gavin Andresen <gavinandresen@gmail•com> wrote:
>> But those issues are solvable through other, non-backwards incompatible
>> means. For example, mandate that a <transaction hash, output index> refers
>> to the first such pair that is not already spent. No?
>
> Yes, that is essentially what BIP 30 did.

It's important to note that bip 30 doesn't prevent duplication, it
just prevents the identified really evil outcome of the duplication.

There was discussion on doing the height _before_ that, but the
realization that the rewrites were a real vulnerability made it urgent
and rolling out the height will require time while the bip30 change
could be deployed more quickly.



  reply	other threads:[~2012-07-06 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 15:10 Jeff Garzik
2012-07-06 16:45 ` Peter Vessenes
2012-07-06 16:49   ` Jeff Garzik
2012-07-06 16:56     ` Mark Friedenbach
2012-07-06 20:02       ` Gavin Andresen
2012-07-06 20:10         ` Gregory Maxwell [this message]
2012-07-06 20:02       ` Amir Taaki
2012-07-06 17:02     ` Peter Vessenes

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=CAAS2fgTCjmTD8qZoUnyNLhqoga8-E5osEx3qwqSfoWQewBP3Gg@mail.gmail.com \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=gavinandresen@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