From: Alex Morcos <morcos@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] New Soft Fork Deployment: CSV (BIP's 68, 112, 113)
Date: Fri, 18 Mar 2016 15:43:41 -0400 [thread overview]
Message-ID: <CAPWm=eWhwphyex=m51KGjQmzoP3Yedt6_+As1o9wEr-A-+X+Sg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
Following on my earlier message
<https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-March/012485.html>,
I am happy to announce a new soft fork to be deployed using BIP 9
<https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki> - Version
bits.
Please review BIP 9
<https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki> as it has
been updated for information on how Version bits soft forks activate.
This deployment is being referred to as CSV (CheckSequenceVerify) and will
activate the following 3 BIPS as consensus rules:
BIP 68 <https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki> -
Relative lock-time using consensus-enforced sequence numbers
BIP 112 <https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki> -
CHECKSEQUENCEVERIFY
BIP 113 <https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki> -
Median time-past as endpoint for lock-time calculations
These BIP's have been updated with the deployment information:
bit: 0
startTime: 1462060800 "May 1st, 2016" (mainnet)
1456790400 "March 1st, 2016" (testnet)
endTime: 1493596800 "May 1st, 2017" (mainnet and testnet)
Bitcoin Core will release 0.11.3 and 0.12.1 software which implements these
soft forks in the near future.
Thanks,
Alex
[-- Attachment #2: Type: text/html, Size: 2825 bytes --]
reply other threads:[~2016-03-18 19:43 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=eWhwphyex=m51KGjQmzoP3Yedt6_+As1o9wEr-A-+X+Sg@mail.gmail.com' \
--to=morcos@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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