From: Gavin Andresen <gavinandresen@gmail•com>
To: Mark Friedenbach <mark@monetize•io>
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:02:16 -0400 [thread overview]
Message-ID: <CABsx9T39Hj5XSwVxkAw+UxuEyKMnjpAtYtfoLD7KpMuUCiM=Jg@mail.gmail.com> (raw)
In-Reply-To: <CACh7GpFb8Xxn9KmR34UNw6N=P96TJSgqec+eLdr5KneZAOj9Tw@mail.gmail.com>
> 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.
We want to do this also, partly for "belt and suspenders" security but
mostly for two reasons:
1. To test using block/transaction version numbers to smoothly roll
out changes. The next change we need to make might be prompted by some
crisis; better to learn any lessons now, when we have the luxury of
time to fix problems that might crop up.
2. We think we'll all appreciate the change in a year or three, when
the whole network has upgraded and we can start writing code that
assumes all new blocks past a certain checkpoint contain their height;
that should make it easier to do things like figure out whether or not
an orphan chain can possibly be part of the main chain.
--
--
Gavin Andresen
next prev parent reply other threads:[~2012-07-06 20:02 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 [this message]
2012-07-06 20:10 ` Gregory Maxwell
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='CABsx9T39Hj5XSwVxkAw+UxuEyKMnjpAtYtfoLD7KpMuUCiM=Jg@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@monetize$(echo .)io \
/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