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 D9F6F259 for ; Mon, 2 Nov 2015 20:33:49 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 26CA0192 for ; Mon, 2 Nov 2015 20:33:49 +0000 (UTC) Received: by lffz202 with SMTP id z202so67272334lff.3 for ; Mon, 02 Nov 2015 12:33:47 -0800 (PST) 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=OpcJr/GaZ9gQqbwP/ILVqhhlBEK46Tb9dJJudPmQt/c=; b=IYAyMLFGlVQC+HtvlGhMQi2Bhg6GWHB4KTHUE/L+pQv50spar6BO8v4si5MHGUEygz mXpLtTYrfcbhvLt3/zLIKf7wfsWRa7bi/0J2eTCA9IOuDhOKJCM2AuXBDR4J+dW8T3rB z6UxBEA+B75LAgkPX4ZKoRplpTJ5zP98nMVtAV5mC5ZHvUktJdbM4t+Qx+I0EO4DRlVz 7IMZctBO8tnEmi4lwd8Kgke+CMbTqlFUDO1A3ziBuyYSC/AHqbM5bAkfxZ9IqfxM4aUI JdEZ6HRaLP+nQgY7xwIIJbHubxgk4ep5ZX0gd9k5MNpKRH3p40hZanlloeZzM51JODd+ Befw== MIME-Version: 1.0 X-Received: by 10.25.29.129 with SMTP id d123mr7317968lfd.4.1446496427608; Mon, 02 Nov 2015 12:33:47 -0800 (PST) Received: by 10.25.22.146 with HTTP; Mon, 2 Nov 2015 12:33:47 -0800 (PST) In-Reply-To: References: Date: Mon, 2 Nov 2015 15:33:47 -0500 Message-ID: From: Gavin Andresen To: Tier Nolan Content-Type: multipart/alternative; boundary=001a11402e1ebc924c052394b1a8 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] Compatibility requirements for hard or soft 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: Mon, 02 Nov 2015 20:33:50 -0000 --001a11402e1ebc924c052394b1a8 Content-Type: text/plain; charset=UTF-8 On Sun, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > For guidelines > > * Transaction version numbers will be increased, if possible > * Transactions with unknown/large version numbers are unsafe to use with > locktime > * Reasonable notice is given that the change is being contemplated > * Non-opt-in changes will only be to protect the integrity of the network > > Locked transaction that can be validated without excessive load on the > network should be safe to use, even if non-standard. > > An OP_CAT script that requires TBs of RAM to validate crosses the > threshold of reasonableness. > I like those guidelines, although I'm sure there may be lots of arguing over what fits under "protects the integrity of the network" or what constitutes "reasonable notice" (publish a BIP at least 30 days before rolling out a change? 60 days? a year?) -- -- Gavin Andresen --001a11402e1ebc924c052394b1a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= un, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev &l= t;bitcoin-dev@lists.linuxfoundation.org> wrote:
For guidelines

* Transaction ve= rsion numbers will be increased, if possible
* Transactions w= ith unknown/large version numbers are unsafe to use with locktime
=
* Reasonable notice is given that the change is being contemplated
=
* Non-opt-in changes will only be to protect the integrity of th= e network

Locked transaction that can be validated without excessive= load on the network should be safe to use, even if non-standard.
=

An OP_CAT script that requires TBs of RAM to validate c= rosses the threshold of reasonableness.=C2=A0

I like those guidelines, although I'm sure there may be = lots of arguing over what fits under "protects the integrity of the ne= twork" or what constitutes "reasonable notice" (publish a BI= P at least 30 days before rolling out a change? 60 days? a year?)

--
--
Gavin Andresen

--001a11402e1ebc924c052394b1a8--