From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Sun, 1 Nov 2015 19:06:43 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.9-gentoo-r1; KDE/4.14.8; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201511011906.44081.luke@dashjr.org>
Subject: [bitcoin-dev] BIP 113: Median time-past is a HARDfork,
	not a softfork!
Precedence: list

BIP 113 makes things valid which currently are not (any transaction with a 
locktime between the median time past, and the block nTime). Therefore it is a 
hardfork. Yet the current BIP describes and deploys it as a softfork.

Furthermore, Bitcoin Core one week ago merged #6566 adding BIP 113 logic to 
the mempool and block creation. This will probably produce invalid blocks 
(which CNB's safety TestBlockValidity call should catch), and should be 
reverted until an appropriate solution is determined.

Rusty suggested something like adding N hours to the median time past for 
comparison, and to be a proper hardfork, this must be max()'d with the block 
nTime. On the other hand, if we will have a hardfork in the next year or so, 
it may be best to just hold off and deploy as part of that.

Further thoughts/input?

Luke