Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D6F8F89C for ; Wed, 29 Mar 2017 04:21:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DF675161 for ; Wed, 29 Mar 2017 04:21:40 +0000 (UTC) Received: from [192.168.1.111] (137.189.135.19 [137.189.135.19]) by mx.zohomail.com with SMTPS id 1490761297585964.0486404973495; Tue, 28 Mar 2017 21:21:37 -0700 (PDT) From: Johnson Lau Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Date: Wed, 29 Mar 2017 12:21:33 +0800 In-Reply-To: <1526531.K1h7bgEXcQ@cherry> To: Tom Zander References: <1526531.K1h7bgEXcQ@cherry> X-Mailer: Apple Mail (2.3259) X-ZohoMailClient: External X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE 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] Hard fork proposal from last week's meeting 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: Wed, 29 Mar 2017 04:21:42 -0000 --Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 29 Mar 2017, at 04:50, Tom Zander > wrote: >=20 > On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via bitcoin-dev = wrote: >> So if we really want to get prepared for a potential HF with unknown >> parameters, >=20 > That was not suggested. >=20 > Maybe you can comment on the very specific suggestion instead? >=20 > --=20 > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel = Just take something like FlexTran as example. How you could get prepared = for that without first finalising the spec? Or changing the block interval from 10 minutes to some other value? Also, fixing the sighash bug for legacy scripts? There are many other ideas that require a HF: https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas = = --Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On 29 Mar 2017, at 04:50, Tom Zander <tomz@freedommail.ch>= wrote:

On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via = bitcoin-dev wrote:
So = if we really want to get prepared for a potential HF with unknown
parameters,

That = was not suggested.

Maybe you can comment on = the very specific suggestion instead?

-- =
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

Just take something like FlexTran as example. How you could = get prepared for that without first finalising the spec?

Or changing the block = interval from 10 minutes to some other value?

Also, fixing the sighash bug for legacy = scripts?

There = are many other ideas that require a HF:
https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas
= --Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3--