MIME-Version: 1.0
Date: Tue, 1 Mar 2016 09:34:13 -0500
Message-ID: <CAPWm=eWYGsD78wuCeg9RBiPQg2B8XzS-om85bEcJyL2A1Kfb-w@mail.gmail.com>
From: Alex Morcos <morcos@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c3d4f4cc2a2b052cfda850
Subject: [bitcoin-dev] Soft fork for BIPs 68, 112, and 113
Precedence: list

--001a11c3d4f4cc2a2b052cfda850
Content-Type: text/plain; charset=UTF-8

Bitcoin Core is ready to move towards deployment of a soft fork which will
implement BIP's 68, 112, and 113.

BIP 68 - Relative lock-time using consensus-enforced sequence numbers -
https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
BIP 112 - CHECKSEQUENCEVERIFY -
https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
BIP 113 - Median time-past as endpoint for lock-time calculations -
https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki

BIP 113 logic was introduced in the 0.11.2 release as a standardness rule
and BIP 68 and BIP 112 logic has been merged into master*.
What remains to be done is finish testing, merge the logic to activate the
soft forks and backport the code to supported releases.

The exact rollout mechanism is still being finalized but will be
coordinated with the community.

This email is meant to serve as a readiness announcement and confirm that
there are no outstanding concerns.

Thanks,
Alex


* -  BIP 68 and BIP 112 logic is only enforced when the tx version is >= 2
which will only become standard with the release of the soft fork code.

--001a11c3d4f4cc2a2b052cfda850
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Bitcoin Core is ready to move towards deployment of a=
 soft fork which will implement BIP&#39;s 68, 112, and 113.</div><div><br><=
/div><div>BIP 68 - Relative lock-time using consensus-enforced sequence num=
bers - <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0068.medi=
awiki">https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki</a></=
div><div>BIP 112 - CHECKSEQUENCEVERIFY - <a href=3D"https://github.com/bitc=
oin/bips/blob/master/bip-0112.mediawiki">https://github.com/bitcoin/bips/bl=
ob/master/bip-0112.mediawiki</a></div><div>BIP 113 - Median time-past as en=
dpoint for lock-time calculations - <a href=3D"https://github.com/bitcoin/b=
ips/blob/master/bip-0113.mediawiki">https://github.com/bitcoin/bips/blob/ma=
ster/bip-0113.mediawiki</a></div><div><br></div><div>BIP 113 logic was intr=
oduced in the 0.11.2 release as a standardness rule and BIP 68 and BIP 112 =
logic has been merged into master*.=C2=A0</div><div>What remains to be done=
 is finish testing, merge the logic to activate the soft forks and backport=
 the code to supported releases.</div><div><br></div><div>The exact rollout=
 mechanism is still being finalized but will be coordinated with the commun=
ity.</div><div><br></div><div>This email is meant to serve as a readiness a=
nnouncement and confirm that there are no outstanding concerns.</div><div><=
br></div><div>Thanks,</div><div>Alex</div><div><br></div><div><br></div><di=
v>* - =C2=A0BIP 68 and BIP 112 logic is only enforced when the tx version i=
s &gt;=3D 2 which will only become standard with the release of the soft fo=
rk code.</div><div><br></div></div>

--001a11c3d4f4cc2a2b052cfda850--