public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Luke Dashjr <luke@dashjr•org>
Cc: Stephen Pair <stephen@bitpay•com>,
	Mike Hearn <hearn@vinumeris•com>,
	Pieter Wuille <pieter.wuille@gmail•com>,
	Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
	Amir Taaki <genjix@riseup•net>
Subject: Re: [bitcoin-dev] BIP Final status
Date: Mon, 8 Feb 2016 17:41:00 -0500	[thread overview]
Message-ID: <20160208224100.GA25684@savin.petertodd.org> (raw)
In-Reply-To: <201602082217.57146.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

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.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org
000000000000000001ae7ca66e52359d67c407a739fde42b83ecc746d3ab735d

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

  reply	other threads:[~2016-02-08 22:44 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 [this message]
2016-02-08 22:57   ` Luke Dashjr

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=20160208224100.GA25684@savin.petertodd.org \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=genjix@riseup$(echo .)net \
    --cc=hearn@vinumeris$(echo .)com \
    --cc=luke@dashjr$(echo .)org \
    --cc=pieter.wuille@gmail$(echo .)com \
    --cc=stephen@bitpay$(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