Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8963493D for ; Sun, 16 Oct 2016 16:36:00 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com [209.85.220.173]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F0351A7 for ; Sun, 16 Oct 2016 16:35:59 +0000 (UTC) Received: by mail-qk0-f173.google.com with SMTP id z190so201056772qkc.2 for ; Sun, 16 Oct 2016 09:35:59 -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; bh=ck3jEsK29zbVn5ikbJxUuAO5ZdMJcGAbWL9Ord5/aoQ=; b=TU/m5X3suSHBMslk9MJkb2mBnCKDE9x3xYrd3TQRHkw+WiMQrEcfn/JGefY90t74ZY 1+HOApGLSv81Dx4mndEXwlB2tXFyIxUbD/7p8CxmL2RHrfCQjf1GsraNBIlXXR7B9J/t wri6rhy3O0pfoGDj8gOlC9D/g3954lG+RGrddex+fzPaqEsDmmyyTByBPpnb7Hwd24nO IexfveJ8UciknUFyjLl0fNBF+OBZcss69YaqA7puGY55EfHCr6fqkXhuGacP4Dv2EczG I1MIphO1LOxle6QNFKUlhi7ecWhRKnKPajgq3Sj5Bl+JcRtowMxLxhBh+4myLw/Y2eEA iSow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ck3jEsK29zbVn5ikbJxUuAO5ZdMJcGAbWL9Ord5/aoQ=; b=lq3qy5mN4hvu5mpkxOHH4iCboojyu+j+8Qp8jV5SH1VlIPvovKW1Dq90p9c0fdbUam BYhyU+3D98ZDp49BlrGsGv/sfiOdjuhV43mutkQygbRIHajLXrJ5fRs1+RnVMBbQcIt1 ysJ4zPTN10tTP96dtMZE+8oG3JBsm1KC3N9fATzcSGxntpv7tYY0lPnL7MSLA8w1adkK jNI5GeQ3rKEOp6lgRL4c16qcppWmBMqaE2htlo/8oYezg/QvwQP8yOrNG7CIoO2rE9Lf WPQ9r8C7FedCF4dcXe7K4iLTps1sE6Ia38c5KjM1UJ8KpE7fVHfSZ0wO2AiCntjW2qNp /1hw== X-Gm-Message-State: AA6/9RnHeodj2bWMTOVX0dpsJd4htOCSaW/Ks8LMRxqVVLu/U1paFVVmF/jL+9hU/LpCQDPpo1YQ6H0fEgJX/g== X-Received: by 10.233.237.145 with SMTP id c139mr19375075qkg.29.1476635759210; Sun, 16 Oct 2016 09:35:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.53.184 with HTTP; Sun, 16 Oct 2016 09:35:58 -0700 (PDT) In-Reply-To: <1782741.nelbyupFSb@strawberry> References: <1782741.nelbyupFSb@strawberry> From: Gavin Andresen Date: Sun, 16 Oct 2016 12:35:58 -0400 Message-ID: To: Tom Zander , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary=94eb2c0970d8e3f70e053efe0d63 X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sun, 16 Oct 2016 16:36:38 +0000 Subject: Re: [bitcoin-dev] Start time for BIP141 (segwit) X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 16:36:00 -0000 --94eb2c0970d8e3f70e053efe0d63 Content-Type: text/plain; charset=UTF-8 On Sun, Oct 16, 2016 at 10:58 AM, Tom Zander via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > The fallow period sounds waaaay to short. I suggest 2 months at minimum > since anyone that wants to be safe needs to upgrade. > I asked a lot of businesses and individuals how long it would take them to upgrade to a new release over the last year or two. Nobody said it would take them more than two weeks. If somebody is running their own validation code... then we should assume they're sophisticated enough to figure out how to mitigate any risks associated with segwit activation on their own. -- -- Gavin Andresen --94eb2c0970d8e3f70e053efe0d63 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= un, Oct 16, 2016 at 10:58 AM, Tom Zander via bitcoin-dev = <bitcoin-dev@lists.linuxfoundation.org> wrote:
The fallow period sounds waaaay to short. I suggest 2 months at minimum<= br> since anyone that wants to be safe needs to upgrade.

I asked a lot of businesses and individuals how long it would take th= em to upgrade to a new release over the last year or two.

Nobody said it would = take them more than two weeks.

If somebody is running their own validation code..= . then we should assume they're sophisticated enough to figure out how = to mitigate any risks associated with segwit activation on their own.

--
--
Gavin Andresen

--94eb2c0970d8e3f70e053efe0d63--