BIP 70 and OP_RETURN
4 messages, 28 to 29 Mar 2014. Started by Justus Ranvier.
Justus Ranvier (2), Mike Hearn (2)
The description of the Output message states that the payment request can specify any standard TxOut script, and that OP_RETURN is a standard transaction type that would imply the ability to specify OP_RETURN outputs in BIP 70 payment requests.
If the creator of a payment request wanted the sender to include a small amount of data as an OP_RETURN output, how would they specify this?
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?
On 03/29/2014 01:30 PM, Mike Hearn wrote:
Quoted text (4 lines)
> 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.
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 <justusranvier@gmail•com>wrote:
Quoted text (14 lines)
> 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 >