- From: Mountie Lee <mountie@paygate.net>
- Date: Thu, 12 May 2016 13:49:19 +0900
- To: Christopher Allen <ChristopherA@blockstream.com>
- Cc: "public-blockchain@w3.org" <public-blockchain@w3.org>
- Message-ID: <CAE-+aYJ1TrjArQzN5OccRc7suPbJenCjpMr+_7hovSA5QVrQ5Q@mail.gmail.com>
I got comment from a member. he suggested to use "OP_PUSH <data> OP_DROP" instead of using "OP_RETURN <data>" as input script. On Wed, May 11, 2016 at 6:17 AM, Christopher Allen < ChristopherA@blockstream.com> wrote: > It would be pretty difficult to send a Bitcoin script in an OP_RETURN > given preferred 40 byte limit, 80 max. P2SH median size is 358 bytes. > > -- Christopher Allen > > > On Monday, May 9, 2016, Mountie Lee <mountie@paygate.net> wrote: > >> Hi. >> >> I were try to set OP_RETURN <data> script as input script of bitcoin >> transaction >> to toss the role to consumer. >> >> I believe it is not implemented at bitcoin-core client but somebody were >> tried it. >> >> best regards >> mountie >> >> On Mon, May 9, 2016 at 11:23 PM, Christopher Allen < >> ChristopherA@blockstream.com> wrote: >> >>> >>> On Sun, May 8, 2016 at 11:08 AM, Mountie Lee <mountie@paygate.net> >>> wrote: >>> >>>> is there any example using OP_RETURN script hash for P2SH address and >>>> original OP_RETURN script will be used at transaction input? >>>> >>> >>> I am not sure I understand your question. >>> >>> You can put anything into OP_RETURN, but by policy it not interpreted by >>> Bitcoin itself. This doesn’t mean that you can’t use it for Layer 2 >>> protocols (and many do), but P2SH is a Layer 1. >>> >>> — Christopher Allen >>> >> >> >> >> -- >> Mountie Lee >> >> PayGate >> CTO, CISSP >> Tel : +82 2 2140 2700 >> E-Mail : mountie@paygate.net >> >> -- Mountie Lee PayGate CTO, CISSP Tel : +82 2 2140 2700 E-Mail : mountie@paygate.net
Received on Thursday, 12 May 2016 04:50:16 UTC