From: Luke Dashjr <luke@dashjr•org>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Final status
Date: Mon, 8 Feb 2016 22:57:34 +0000 [thread overview]
Message-ID: <201602082257.36009.luke@dashjr.org> (raw)
In-Reply-To: <20160208224100.GA25684@savin.petertodd.org>
On Monday, February 08, 2016 10:41:00 PM Peter Todd wrote:
> On Mon, Feb 08, 2016 at 10:17:55PM +0000, Luke Dashjr via bitcoin-dev wrote:
> > Additionally, https://github.com/bitcoin/bips/pull/315 proposes to
> > upgrade five additional from Draft to Final status, and preferably needs
> > ACKs from the champions of the BIPs:
> >
> > BIP 50: March 2013 Chain Fork Post-Mortem, by Gavin Andresen
>
> It may be good to update BIP 50 with the new information that calling it
> a "hard fork" misses subtleties about what happened during that fork. In
> particular, 0.7 rejection of the chain was non-deterministic, based on
> having seen a re-org in a specific way.
I agree BIP 50 could use some rephrasing, but the May 2013 change was
definitely a hardfork, despite the problems with the pre-March protocol.
Luke
prev parent reply other threads:[~2016-02-08 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:17 Luke Dashjr
2016-02-08 22:41 ` Peter Todd
2016-02-08 22:57 ` Luke Dashjr [this message]
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=201602082257.36009.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
/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