From: Peter Todd <pete@petertodd•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP65 / CHECKLOCKTIMEVERIFY deployment
Date: Sun, 28 Jun 2015 15:50:54 -0400 [thread overview]
Message-ID: <20150628195053.GA9909@muck> (raw)
In-Reply-To: <20150625223344.GA2406@muck>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Thu, Jun 25, 2015 at 06:33:44PM -0400, Peter Todd wrote:
> Thoughts? If there are no objections I'll go ahead and write that code,
> using the same thresholds as BIP66.
I've opened a pull-req to deploy CHECKLOCKTIMEVERIFY via the
IsSuperMajority() mechanism:
https://github.com/bitcoin/bitcoin/pull/6351
Final step towards CLTV deployment on mainnet.
I've copied the logic and tests from the previous BIP66 (DERSIG)
soft-fork line-by-line for ease of review; any code review applicable to
BIP66 should be applicable to BIP65.
Once merged I'll prepare a backport of the soft-fork logic for the
v0.10.x branch as well.
--
'peter'[:-1]@petertodd.org
00000000000000000dbc12bdcb4d0a340272edd649d24849f86a20d075f0dba1
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-28 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 22:33 Peter Todd
2015-06-25 23:52 ` Eric Lombrozo
2015-06-26 0:07 ` Tier Nolan
2015-06-28 19:50 ` Peter Todd [this message]
2015-08-04 16:54 ` Pieter Wuille
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=20150628195053.GA9909@muck \
--to=pete@petertodd$(echo .)org \
--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