From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTupm-0008Np-GG for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 15:06:10 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.43 as permitted sender) client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f43.google.com; Received: from mail-oa0-f43.google.com ([209.85.219.43]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTupl-0004YQ-JZ for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 15:06:10 +0000 Received: by mail-oa0-f43.google.com with SMTP id eb12so7504515oac.30 for ; Sat, 29 Mar 2014 08:06:04 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.134.137 with SMTP id pk9mr12253033oeb.40.1396105564273; Sat, 29 Mar 2014 08:06:04 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Sat, 29 Mar 2014 08:06:04 -0700 (PDT) In-Reply-To: <5336E07E.5040309@gmail.com> References: <5335EC3B.6070605@silicon> <5336E07E.5040309@gmail.com> Date: Sat, 29 Mar 2014 16:06:04 +0100 X-Google-Sender-Auth: 7akXxDNiupy3zJZQksNTsPVr63A Message-ID: From: Mike Hearn To: Justus Ranvier Content-Type: multipart/alternative; boundary=047d7b471dfa3a410504f5c028c6 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: 1WTupl-0004YQ-JZ Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2014 15:06:10 -0000 --047d7b471dfa3a410504f5c028c6 Content-Type: text/plain; charset=UTF-8 They should do. If they don't they're not spec compliant. I'm not sure what they actually do though. Currently only Bitcoin Core and Android Bitcoin Wallet implement BIP 70 so you can just create such a request and then try it out and see what happens. On Sat, Mar 29, 2014 at 4:02 PM, Justus Ranvier wrote: > On 03/29/2014 01:30 PM, Mike Hearn wrote: > > 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? > > > > I guess what I was asking is whether or not all BIP70 compatible clients > will support the creation of all standard output types, including > OP_RETURN outputs. > > -- > Support online privacy by using email encryption whenever possible. > Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k > --047d7b471dfa3a410504f5c028c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
They should do. If they don't they're not spec com= pliant. I'm not sure what they actually do though. Currently only Bitco= in Core and Android Bitcoin Wallet implement BIP 70 so you can just create = such a request and then try it out and see what happens.


On Sat, Mar 2= 9, 2014 at 4:02 PM, Justus Ranvier <justusranvier@gmail.com><= /span> wrote:
On 0= 3/29/2014 01:30 PM, Mike Hearn wrote:
> 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?
>

I guess what I was asking is whether or not all BIP70 compatibl= e clients
will support the creation of all standard output types, including
OP_RETURN outputs.

--
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=3DbakOKJFtB-k

--047d7b471dfa3a410504f5c028c6--