From: Alex Morcos <morcos@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Soft fork for BIPs 68, 112, and 113
Date: Tue, 1 Mar 2016 09:34:13 -0500 [thread overview]
Message-ID: <CAPWm=eWYGsD78wuCeg9RBiPQg2B8XzS-om85bEcJyL2A1Kfb-w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
reply other threads:[~2016-03-01 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPWm=eWYGsD78wuCeg9RBiPQg2B8XzS-om85bEcJyL2A1Kfb-w@mail.gmail.com' \
--to=morcos@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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