From: Maciej Trebacz <maciej@bitalo•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Standardizing OP_RETURN message format
Date: Sun, 6 Apr 2014 09:35:20 +0200 [thread overview]
Message-ID: <CAD=_8RSn+ZtxJL1=3BsaEvfc4Wrg7MW-uDTcnQo75GQbrVP3Ng@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
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?
--
Best regards,
Maciej Trębacz - Bitalo.com
[-- Attachment #2: Type: text/html, Size: 1451 bytes --]
next reply other threads:[~2014-04-06 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 7:35 Maciej Trebacz [this message]
2014-04-06 9:21 ` Gregory Maxwell
2014-04-06 10:37 ` Peter Todd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD=_8RSn+ZtxJL1=3BsaEvfc4Wrg7MW-uDTcnQo75GQbrVP3Ng@mail.gmail.com' \
--to=maciej@bitalo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox