1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <maciej@bitalo.com>) id 1WWj8t-0000D7-Br
for bitcoin-development@lists.sourceforge.net;
Sun, 06 Apr 2014 09:13:31 +0000
Received: from mail-lb0-f198.google.com ([209.85.217.198])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WWj8s-00010o-74
for bitcoin-development@lists.sourceforge.net;
Sun, 06 Apr 2014 09:13:31 +0000
Received: by mail-lb0-f198.google.com with SMTP id w7so3804161lbi.9
for <bitcoin-development@lists.sourceforge.net>;
Sun, 06 Apr 2014 02:13:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:date:message-id:subject:from:to
:content-type;
bh=ixYBAZgTnTNaf7nASwoaGhjln4CSRfwCIh7mZ2WmuQY=;
b=MiDXwBg1TVTf0vuxdGpkeQYX8bhvrcTw4KEFq0Zfe+a6dIhbeUkCZwDmShYs0moIIn
s4cGjkZnRkr72AztefpDRbHCVr7Yvilh2hI7qQN2sNMM43IS8miutu7MoCq7RMMCnwn3
44R8a6jf8XRRH6yY0mHf6Srfn9pDAj4DYPG73qVsZkNYYJVA5GCwp4MQ5yNjIOE4ymA2
1WpNdGCtzJ/V8cfL9GihdvKWif1EVLugj8AyPR9Bp8+hkzevb+AseWu7PDbzbcEMhipV
jetaunmvqokqZPraW7RqxnPopJe7vfFGKeX8phy1YVLbhgp82L1IQd6+bGqlDrULIVoV
MRBw==
X-Gm-Message-State: ALoCoQl5MJmWGof7SBuMuZumN9GjG13HHNstBMLqHy8Pr90pJf/HYsR9UxEIsGfqEUNm5o4yV4+T
MIME-Version: 1.0
X-Received: by 10.194.63.46 with SMTP id d14mr33325148wjs.24.1396769720352;
Sun, 06 Apr 2014 00:35:20 -0700 (PDT)
Received: by 10.216.115.10 with HTTP; Sun, 6 Apr 2014 00:35:20 -0700 (PDT)
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
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WWj8s-00010o-74
Subject: [Bitcoin-development] Standardizing OP_RETURN message format
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: Sun, 06 Apr 2014 09:13:31 -0000
--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'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--
|
