From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 3079540A for ; Fri, 31 Jul 2015 17:41:21 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8D6481F1 for ; Fri, 31 Jul 2015 17:41:18 +0000 (UTC) Received: by lbqc9 with SMTP id c9so25113356lbq.1 for ; Fri, 31 Jul 2015 10:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=87MRsaweixIWOsDxBSKFt0DN8+34WeNNu5YSk3mYXBg=; b=Bkdt1TC+zzka9eazlrvQBAiKaATslHfjopxXp9rEUH4kMiCvU4TfvMCSexIT8FrxlB EZDm8lNMQIZivkNnjfHi3BNoKNVuzSMTz0qCYExXJWCH/2UER0QwRG0kHGYqzxvHNo+y ANcuzGbXaB8+Zb7ZZElmFBbwcUEoKKHq1k3AxMgMP3hRDWTiLPx5b6EXEknUUqNMJ96R 3qXtW3GIuunOjOIVzOr67skE4lJ402brp6t2jtsBDLGGTk5696F/X8JTISqBGif8oEJk AGW7k9f22ykDlKqbCYk7g5wKLv4u5uRIWjFvQEjQpQNnmX4cOPJwAgVBQMtSd8Wj9eAQ CJuA== X-Received: by 10.112.13.9 with SMTP id d9mr4276632lbc.57.1438364476512; Fri, 31 Jul 2015 10:41:16 -0700 (PDT) Received: from [192.168.1.33] (lumumba.torservers.net. [77.247.181.163]) by smtp.gmail.com with ESMTPSA id z12sm1051588lbp.46.2015.07.31.10.41.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Jul 2015 10:41:15 -0700 (PDT) Message-ID: <55BBB32B.3080802@gmail.com> Date: Fri, 31 Jul 2015 18:40:59 +0100 From: Thomas Kerin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: bitcoin-dev@lists.linuxfoundation.org References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, 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 Subject: Re: [bitcoin-dev] [Bitcoin-development] [BIP draft] Motivation and deployment of consensus rules changes ([soft/hard]forks) 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: Fri, 31 Jul 2015 17:41:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I really think there should be a document before a BIP number is assigned. On 23/07/15 12:10, Jorge Timón via bitcoin-dev wrote: > Discussions about whether to get miner's confirmation on > uncontroversial hardforks or not, and about whether to use nHeight, > nMedianTime or just use nTime are spreading all around. Hopefully > getting a BIP number (even though this is still a draft) will help > concentrating discussions about deployment of uncontroversial > hardforks to a single place. > Greg, can I get a BIP number for this? > > On Sun, Jun 21, 2015 at 12:54 PM, Tier Nolan wrote: >> On Sun, Jun 21, 2015 at 11:31 AM, Jorge Timón wrote: >>> >>> You mean the timewarp fix can be coded as a softfork instead of a >>> hardfork? How so? >> >> >> The easiest would be a rule requiring that all blocks are within 1 day of >> the median of the previous 11 blocks. At the moment, you need to be greater >> than that value. This would add a condition at the other end. >> >> It wouldn't be a total fix, but it would protect against the exploit. >> >> A stricter soft fork would be that the two blocks in question have to have >> the same timestamp. This would force the off by 1 and the correct value to >> give the same result. >> >>> If that's the case, do you have a better candidate? >> >> >> I think it is fine, since fixing it "right" does require a hard fork, >> especially if it is only to show a non controversial hard fork. >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev - -- My PGP key can be found here: -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVu7MlAAoJEAiDZR291eTlGnkP/jG/oW2PfPwDt6t+1UJ7P1LO /NDtpUI5wiPQ6aXBmqKSx7FxZ9QJQM1tB1SpGhFosOXXSiYLjNos0l0S6oRw7yGC LzXmbNTL863F0vOfRU35yxQJbcUi6gOHk8E/oo2X/V+BgAoc4cweK4080C8k1vki 7kPPiSek4erMo7TVNb5vsHkOI6QXhKNV/lFuSOuRAwklRY5vL2BZi56HekOnoFdr iHebmRrjL7R+IFzasnWtHh6KGs51tg02SOPTMXwJ/H+xDqN9LXk/DJUbp9QhEa+t TwojQBj7D+HMWavaLRVjVQOcvxxm3PTwZHmHxzfrx3kG5nsZNWrebWElHikW8BuW dg6Yq/6mIW59HPyNSc5HCBnNonKpZebsQU0rdzOcwWFdk0SZ1TuKrYjNu9uDVGpo od21hIpGYa1FTxk1HQ63PMf5SKmLunvHOehWw8pmXy44k3WVkABAhi7YNIbA8Qvj DJ+k9wtypDBraoQh1yur4r1cBbBVcbaxRwv42MBGhtTXPVzRu6CikJNwa65z1AqT AM3av8+IIgiq9dYn1uzDh1BQGSsB5YYQZ3QDHpM1DxCvjXvmgf4RdFwC0Q0B0X3S jnWebazQvxN9qsylHAJeTZ0+rJCsx+R3Fl2Myasz/c3a6uaYJVi9/N0j3yRm1EYt 3Py8BGrArkIe3CeXaTCV =Yh0o -----END PGP SIGNATURE-----