public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris <ctpacia@gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Mutli-push op_return
Date: Sun, 8 Jan 2017 21:09:09 -0500	[thread overview]
Message-ID: <8c64f5db-7cac-3fde-85c0-a75d752c4192@gmail.com> (raw)

Would there be an objection to making op_return outputs with two
pushdatas standard (same max data size)?

Use case is mostly tagging transactions so they can be returned by bloom
filtering nodes:

OP_RETURN <tag> <data>

Since bip37 nodes test each data element in each output script (which I
believe applies to op_return as well?) it provides a lightweight way of
fetching transactions where the tag matches a specific pattern.

It appears a sizable number of nodes/miners already accept such
transactions as this one was mined in the first block...
https://blockchain.info/tx/400b4738f1e4eab4062e085623b9a3a71670f5c0d42e32dbe5a4e71da5baabe0

- Chris





             reply	other threads:[~2017-01-09  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  2:09 Chris [this message]
2017-01-09  3:08 ` [bitcoin-dev] Mutli-push op_return Luke Dashjr
2017-01-09  4:32   ` Chris

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=8c64f5db-7cac-3fde-85c0-a75d752c4192@gmail.com \
    --to=ctpacia@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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