MIME-Version: 1.0
Date: Sun, 6 Apr 2014 09:35:20 +0200
Message-ID: <CAD=_8RSn+ZtxJL1=3BsaEvfc4Wrg7MW-uDTcnQo75GQbrVP3Ng@mail.gmail.com>
From: Maciej Trebacz <maciej@bitalo.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7ba97a8803ee2d04f65acba0
Subject: [Bitcoin-development] Standardizing OP_RETURN message format
Precedence: list

--047d7ba97a8803ee2d04f65acba0
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

So, OP_RETURN is here and there is no coming back. So if we have it, it
would be nice to actually make use of it in a good way. I would like to
write a process BIP with a proposal for standardizing OP_RETURN
transactions for better interoperability between services. Right now there
are no guidelines for crafting these transactions, so everyone just does
what he believes is good for him.

What I would propose is a common, extensible protocol that can be used by
anyone. The generic format would be like this:

OP_RETURN OP_PUSHDATA[length] {2-byte message type} {data}

So basically, we would have a list of message types, that can be then
parsed by everyone because the format is open. It could go like this:

MSG Type | Parameters | Description

00 00 | unknown | Unused type, use it if you don't want to share your
message format with others
00 01 | none | Proof of burn transaction. Use it if you want to effectively
destroy coins (by sending it all as fees to miners)
...

And so on. I have few more ideas for these kind of messages, but it will
only work if we try to make it an open standard, hence the BIP idea. Can I
expect that it will be included with other BIPs if I write it?

--=20
Best regards,
Maciej Tr=EAbacz - Bitalo.com

--047d7ba97a8803ee2d04f65acba0
Content-Type: text/html; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

So, OP_RETURN is here and there is no coming back. So if we have it, it wou=
ld be nice to actually make use of it in a good way.=A0I would like to writ=
e a process=A0BIP with a proposal for standardizing OP_RETURN transactions =
for better interoperability between services. Right now there are no guidel=
ines for crafting these transactions, so everyone just does what he believe=
s is good for him.<div>
<br></div><div>What I would propose is a common, extensible protocol that c=
an be used by anyone. The generic format would be like this:</div><div><br>=
</div><div>OP_RETURN OP_PUSHDATA[length] {2-byte message type} {data}</div>
<div><br></div><div>So basically, we would have a list of message types, th=
at can be then parsed by everyone because the format is open. It could go l=
ike this:</div><div><br></div>MSG Type | Parameters | Description<div><br>
</div><div>00 00 | unknown=A0| Unused type, use it if you don&#39;t want to=
 share your message format with others</div><div>00 01 | none=A0| Proof of =
burn transaction. Use it if you want to effectively destroy coins (by sendi=
ng it all as fees to miners)</div>
<div>...</div><div><br></div><div>And so on. I have few more ideas for thes=
e kind of messages, but it will only work if we try to make it an open stan=
dard, hence the BIP idea. Can I expect that it will be included with other =
BIPs if I write it?</div>
<div><br></div><div>--=A0</div><div>Best regards,</div><div>Maciej Tr=EAbac=
z - Bitalo.com</div>

--047d7ba97a8803ee2d04f65acba0--