Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1XleKB-00085w-QE
	for bitcoin-development@lists.sourceforge.net;
	Tue, 04 Nov 2014 13:39:07 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.175 as permitted sender)
	client-ip=209.85.217.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-lb0-f175.google.com; 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XleK9-0001i1-Na
	for bitcoin-development@lists.sourceforge.net;
	Tue, 04 Nov 2014 13:39:07 +0000
Received: by mail-lb0-f175.google.com with SMTP id n15so3239758lbi.34
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 04 Nov 2014 05:38:59 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.136.164 with SMTP id qb4mr3027686lbb.62.1415108339107;
	Tue, 04 Nov 2014 05:38:59 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.25.91.147 with HTTP; Tue, 4 Nov 2014 05:38:59 -0800 (PST)
In-Reply-To: <CAPg+sBjygohgFf2hE9cGH3ZmV0MaeniZDDNO+hFxOxo-s_d81A@mail.gmail.com>
References: <CAPg+sBjygohgFf2hE9cGH3ZmV0MaeniZDDNO+hFxOxo-s_d81A@mail.gmail.com>
Date: Tue, 4 Nov 2014 14:38:59 +0100
X-Google-Sender-Auth: yGG2Sh5trTGntwNzOjsqbviR0lU
Message-ID: <CANEZrP1wi=Wc+BgMf+9GdLLbNMfSex8XkdCLWuAeS3sj9fDo1Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=089e01183132df101a0507089580
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XleK9-0001i1-Na
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP62 and future script upgrades
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 13:39:08 -0000

--089e01183132df101a0507089580
Content-Type: text/plain; charset=UTF-8

This is another problem that only exists because of the desire to soft
fork. If "script 2.0" is a hard fork upgrade, you no longer need weird
hacks like scripts-which-are-not-scripts.

--089e01183132df101a0507089580
Content-Type: text/html; charset=UTF-8

<div dir="ltr">This is another problem that only exists because of the desire to soft fork. If &quot;script 2.0&quot; is a hard fork upgrade, you no longer need weird hacks like scripts-which-are-not-scripts.</div>

--089e01183132df101a0507089580--