Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	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 1WTtLb-0004pA-Ue
	for bitcoin-development@lists.sourceforge.net;
	Sat, 29 Mar 2014 13:30:55 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.48 as permitted sender)
	client-ip=209.85.219.48; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f48.google.com; 
Received: from mail-oa0-f48.google.com ([209.85.219.48])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WTtLY-0006Ll-K0
	for bitcoin-development@lists.sourceforge.net;
	Sat, 29 Mar 2014 13:30:55 +0000
Received: by mail-oa0-f48.google.com with SMTP id m1so7242963oag.7
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 29 Mar 2014 06:30:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.159.137 with SMTP id xc9mr11948483oeb.31.1396099847284;
	Sat, 29 Mar 2014 06:30:47 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Sat, 29 Mar 2014 06:30:47 -0700 (PDT)
In-Reply-To: <5335EC3B.6070605@silicon>
References: <5335EC3B.6070605@silicon>
Date: Sat, 29 Mar 2014 14:30:47 +0100
X-Google-Sender-Auth: 3QasMd2MEy5rKNB91j1YHK9FdMc
Message-ID: <CANEZrP3wXZVzZ+9r6o2dDm6d+zPqs4NSeomH8eapXadxS-aMKg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Justus Ranvier <justusranvier@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6a9ae77ee3504f5bed327
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: 1WTtLY-0006Ll-K0
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 70 and OP_RETURN
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: Sat, 29 Mar 2014 13:30:56 -0000

--047d7bd6a9ae77ee3504f5bed327
Content-Type: text/plain; charset=UTF-8

They would just encode the OP_RETURN script into an Output structure. I'm
not sure about the question - you seem to give the answer yourself in the
first paragraph?

--047d7bd6a9ae77ee3504f5bed327
Content-Type: text/html; charset=UTF-8

<div dir="ltr">They would just encode the OP_RETURN script into an Output structure. I&#39;m not sure about the question - you seem to give the answer yourself in the first paragraph?<div class="gmail_extra"><br></div></div>

--047d7bd6a9ae77ee3504f5bed327--