Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9E42C170C for ; Sun, 27 Sep 2015 20:41:23 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 154F326C for ; Sun, 27 Sep 2015 20:41:23 +0000 (UTC) Received: by wicfx3 with SMTP id fx3so76707377wic.0 for ; Sun, 27 Sep 2015 13:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=w1TGsQjFU7jN72Z88ChqAvDSgsuV6w9jBTy1n+cMaXQ=; b=vLhueaz6Pe/BVhiuJHc4X8Igs0EcZwNW2bhon7fiJhL+AtDulAq4nmEQMa9Dj8gpsz w/v6gbbF7Xpy/ELXl7RvVieaLnZKKy3IADe3LNSu3sbHCdnBD4WBtZVf7n4ADcW/CZQz CfFMWalhNJ8Q00I+XaPaEzwS/0UydUvrgD65DHhEpp5BitwUgt7GqHetJpLumioCTBUe iZ4fjd2Fr0FnuYZc8CkVRAGnjOKhjcC2BbZsXBelqOpnwecbXijaSwWzMOX3sNXZha14 L9N12ia+EGKW6KhLci+/6D0OsNsamEFpt3PjSJJUNHG6bR3BguAFhq+1nbw1V0//VSd+ j8lA== X-Received: by 10.180.206.45 with SMTP id ll13mr14459453wic.6.1443386481720; Sun, 27 Sep 2015 13:41:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.21.200 with HTTP; Sun, 27 Sep 2015 13:41:02 -0700 (PDT) In-Reply-To: <20150927185031.GA20599@savin.petertodd.org> References: <20150927185031.GA20599@savin.petertodd.org> From: Btc Drak Date: Sun, 27 Sep 2015 21:41:02 +0100 Message-ID: To: Peter Todd Content-Type: multipart/alternative; boundary=001a11c2382c8444ed0520c09af2 X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM, HK_RANDOM_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY! X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Sep 2015 20:41:23 -0000 --001a11c2382c8444ed0520c09af2 Content-Type: text/plain; charset=UTF-8 On Sun, Sep 27, 2015 at 7:50 PM, Peter Todd via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 10) Waiting for nVersion bits and CHECKSEQUENCEVERIFY will significantly > delay deployment of CLTV > > It's been proposed multiple times that we wait until we can do a single > soft-fork with CSV using the nVersion bits mechanism. > > nVersion bits doesn't even have an implementation yet, nor has solid > consensus been reached on the exact semantics of how nVersion bits > should work. Small correction, the suggestion is to aim to roll out CLTV+CSV together by 0.12 release, using IsSuperMajority() (or versionbits if it is ready by then). If CSV is not ready by then, we'd just roll out CLTV. However, the CSV related pull requests are ready for final review and if that can happen soon I don't see why we wouldn't roll CLTV+CSV out together before 0.12. A considerable amount of time, discussion and iterations have occurred for the related PRs and I believe they are at the point of consensus modulo final review before merging. References: Mempool-only sequence number constraint verification https://github.com/bitcoin/bitcoin/pull/6312 Mempool-only CHECKSEQUENCEVERIFY https://github.com/bitcoin/bitcoin/pull/6564 Mempool-only Median time-past as endpoint for lock-time calculations https://github.com/bitcoin/bitcoin/pull/6566 --001a11c2382c8444ed0520c09af2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= un, Sep 27, 2015 at 7:50 PM, Peter Todd via bitcoin-dev &= lt;bitcoin-dev@lists.linuxfoundation.org> wrote:
10) Waiting for nVersion bits and CHECKSEQUENCEVERIFY will signific= antly
=C2=A0 =C2=A0 delay deployment of CLTV

It's been proposed multiple times that we wait until we can do a single=
soft-fork with CSV using the nVersion bits mechanism.

nVersion bits doesn't even have an implementation yet, nor has solid consensus been reached on the exact semantics of how nVersion bits
should work.

Small correction, the suggesti= on is to aim to roll out CLTV+CSV together by 0.12 release, using IsSuperMa= jority() (or versionbits if it is ready by then). If CSV is not ready by th= en, we'd just roll out CLTV.

However, the CSV = related pull requests are ready for final review and if that can happen soo= n I don't see why we wouldn't roll CLTV+CSV out together before 0.1= 2. A considerable amount of time, discussion and iterations have occurred f= or the related PRs and I believe they are at the point of consensus modulo = final review before merging.

References:=C2=A0

Mempool-only sequence= number constraint verification

Mempool-only CHECKSEQUENCEVE= RIFY

Mempool-only Median time-past as endpoint for lock-ti= me calculations

--001a11c2382c8444ed0520c09af2--