public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP65 / CHECKLOCKTIMEVERIFY deployment
Date: Tue, 4 Aug 2015 18:54:39 +0200	[thread overview]
Message-ID: <CAPg+sBgn-y=rBDDMeD+P0xEJiJ=XUv0Da39Cxr23NNOWzewmNw@mail.gmail.com> (raw)
In-Reply-To: <20150628195053.GA9909@muck>

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

On Sun, Jun 28, 2015 at 9:50 PM, Peter Todd <pete@petertodd.org> wrote:

> 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.
>

ACK on merging using IsSuperMajority.

-- 
Pieter

[-- Attachment #2: Type: text/html, Size: 1227 bytes --]

      reply	other threads:[~2015-08-04 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 22:33 [bitcoin-dev] BIP65 / CHECKLOCKTIMEVERIFY deployment Peter Todd
2015-06-25 23:52 ` Eric Lombrozo
2015-06-26  0:07   ` Tier Nolan
2015-06-28 19:50 ` Peter Todd
2015-08-04 16:54   ` Pieter Wuille [this message]

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='CAPg+sBgn-y=rBDDMeD+P0xEJiJ=XUv0Da39Cxr23NNOWzewmNw@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.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