MIME-Version: 1.0
In-Reply-To: <55BBB32B.3080802@gmail.com>
References: <CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com>
	<CAE-z3OVM8vwjo_-FOggSoOWR78w=Rmm+GS7Xv9uSK0jdx1_zdw@mail.gmail.com>
	<CABm2gDrs6XwG5imH3pFFDB71kx2dSfhR7kjc6Pw8hvDKqGvTPQ@mail.gmail.com>
	<CAE-z3OVgQFaFAWUJhDLzyMAE2AXoGHTy0NbUADDAZW9-veX8XA@mail.gmail.com>
	<CABm2gDrrqubbZ7MjDppu-eFxJGcydVoSAK2SC=-s-0txYX6GRQ@mail.gmail.com>
	<55BBB32B.3080802@gmail.com>
Date: Fri, 31 Jul 2015 22:37:43 +0200
Message-ID: <CABm2gDo=LKLhEh0AXBzifR8QDc2epQ8=uObBdskRyf0shShPzw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Thomas Kerin <thomas.kerin@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] [BIP draft] Motivation and
 deployment of consensus rules changes ([soft/hard]forks)
Precedence: list

On Fri, Jul 31, 2015 at 7:40 PM, Thomas Kerin via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> I really think there should be a document before a BIP number is assigned.

There was a document from the start, but after I got the BIP number, I
was renaming the file, moving from org-mode to mediawiki and getting
the code ready.
I'm sorry, I broke the old link to the document, here's the new one:
https://github.com/jtimon/bips/blob/bip-forks/bip-0099.mediawiki

Maybe I should create a PR already to have a permanent link, I don't know.
As said in the document, the code is now here:
https://github.com/bitcoin/bitcoin/compare/0.11...jtimon:hardfork-timewarp-0.11

Also, I should mention that one particular discussion related to this
BIP (whether we should use Block.nTime, median time or block.nHeight
for the activation thresholds) is being discussed in:
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009731.html

The BIP is currently assuming that the preferred choice for all
non-emergency uncontroversial hardforks is defining a starting
block.nHeight after which miners start confirming their upgrade. Once
the 95% threshold is reached the hardfork takes effect.
Long after that, after that first block enforcing the new rules is
deeply buried, that check can simply replaced by re-defining the
threshold height not with the height when miners started voting, but
simply with the height in which the rules started being enforced for
the first time (see https://github.com/bitcoin/bitcoin/pull/5966/files
).