Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8298B14A1 for ; Mon, 28 Sep 2015 13:01:05 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AC53D1F3 for ; Mon, 28 Sep 2015 13:01:04 +0000 (UTC) Received: by laer8 with SMTP id r8so29952700lae.2 for ; Mon, 28 Sep 2015 06:01:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2qGP0O6y8vnsfLXUBOcizevOTFmO4AkYlaBcejZOv+A=; b=pt1MPorCyMMSetR673ovdTVS7IhcXGMx9piSnmj0ZkVqBhSJbiKDL3yL8dVJJ0g4QJ hIggj/db6N4RtIPSQL/lT5dW7bwriKTyXXw2yOlluOpeSfHIulx2qMwnaoAK3jeGERv1 reWXYQ/Qi4DyTb25NLeGQOqeYGGMa6dlMrmPCvlHC+uPZv0obaKVm9xEyP1LihhKBVGg 6Hr6KhfUSxXQE6DD2IecwDmRGFlTc1mxFTTDsy8NzWvhUzjhe+u4p7vgXcKoBA+Aw+co tSRqNP33wFAWaAi+4U17zQqJv1yBDU44nPbB4WErwtTAetr9BuhFdSpxz7rphOT+KC7w V3pA== MIME-Version: 1.0 X-Received: by 10.152.45.41 with SMTP id j9mr3686383lam.4.1443445262911; Mon, 28 Sep 2015 06:01:02 -0700 (PDT) Received: by 10.25.200.214 with HTTP; Mon, 28 Sep 2015 06:01:02 -0700 (PDT) In-Reply-To: References: <20150927185031.GA20599@savin.petertodd.org> Date: Mon, 28 Sep 2015 09:01:02 -0400 Message-ID: From: Gavin Andresen To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c29bca2610da0520ce4aa1 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham 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: Mon, 28 Sep 2015 13:01:05 -0000 --001a11c29bca2610da0520ce4aa1 Content-Type: text/plain; charset=UTF-8 I think three things need to happen: 1) Stop pretending that "everyone must agree to make consensus rule changes." "Rough consensus" is what we've always gone with, and is good enough. 2) Mr. Todd (or somebody) needs to write up a risk/benefit security tradeoff analysis doo-hickey document and publish it. I'm reasonably confident that the risks to SPV nodes can be mitigated (e.g. by deploying mempool-only first, before the soft fork rolls out), but as somebody who has only been moderately paying attention, BETTER COMMUNICATION is needed. What should SPV wallet authors be doing right now, if anything? Once the soft fork starts to roll out or activates, what do miners need to be aware of? SPV wallet authors? 3) I agree CLTV is ready to roll out, that there is rough consensus a soft fork is a reasonable way to do it, and that it should happen ASAP. On Mon, Sep 28, 2015 at 6:48 AM, Mike Hearn via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > There is *no* consensus on using a soft fork to deploy this feature. It > will result in the same problems as all the other soft forks - SPV wallets > will become less reliable during the rollout period. I am against that, as > it's entirely avoidable. > > Make it a hard fork and my objection will be dropped. > > Until then, as there is no consensus, you need to do one of two things: > > 1) Drop the "everyone must agree to make changes" idea that people here > like to peddle, and do it loudly, so everyone in the community is correctly > informed > > 2) Do nothing > > -- -- Gavin Andresen --001a11c29bca2610da0520ce4aa1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think three things need to happen:

1)= Stop pretending that "everyone must agree to make consensus rule chan= ges." "Rough consensus" is what we've always gone with, = and is good enough.

2) Mr. Todd (or somebody) need= s to write up a risk/benefit security tradeoff analysis doo-hickey document= and publish it. I'm reasonably confident that the risks to SPV nodes c= an be mitigated (e.g. by deploying mempool-only first, before the soft fork= rolls out), but as somebody who has only been moderately paying attention,= BETTER COMMUNICATION is needed. What should SPV wallet authors be doing ri= ght now, if anything? Once the soft fork starts to roll out or activates, w= hat do miners need to be aware of? SPV wallet authors?

=
3) I agree CLTV is ready to roll out, that there is rough consensus a = soft fork is a reasonable way to do it, and that it should happen ASAP.

On Mon, Se= p 28, 2015 at 6:48 AM, Mike Hearn via bitcoin-dev <bit= coin-dev@lists.linuxfoundation.org> wrote:
There is no<= /b> consensus on using a soft fork to deploy this feature. It will result i= n the same problems as all the other soft forks - SPV wallets will become l= ess reliable during the rollout period. I am against that, as it's enti= rely avoidable.

Make it a hard fork and my objection will be dropped.

Until then, as th= ere is no consensus, you need to do one of two things:

1) Drop the "everyone= must agree to make changes" idea that people here like to peddle, and= do it loudly, so everyone in the community is correctly informed

2) Do nothing


=
--
--
Gavin Andresen
--001a11c29bca2610da0520ce4aa1--