From: Luke Dashjr <luke@dashjr•org>
To: Chris <ctpacia@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Mutli-push op_return
Date: Mon, 9 Jan 2017 03:08:56 +0000 [thread overview]
Message-ID: <201701090308.58360.luke@dashjr.org> (raw)
In-Reply-To: <8c64f5db-7cac-3fde-85c0-a75d752c4192@gmail.com>
On Monday, January 09, 2017 2:09:09 AM Chris via bitcoin-dev wrote:
> Would there be an objection to making op_return outputs with two
> pushdatas standard (same max data size)?
Standards (BIPs) need to describe a specific use case and protocol for doing
it.
As you note, the default policy on most nodes is to allow such outputs.
Luke
next prev parent reply other threads:[~2017-01-09 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 2:09 Chris
2017-01-09 3:08 ` Luke Dashjr [this message]
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=201701090308.58360.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ctpacia@gmail$(echo .)com \
/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