From: Chris <ctpacia@gmail•com>
To: Luke Dashjr <luke@dashjr•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Mutli-push op_return
Date: Sun, 8 Jan 2017 23:32:53 -0500 [thread overview]
Message-ID: <7cc28f27-9917-6992-6de5-38fd91d42e29@gmail.com> (raw)
In-Reply-To: <201701090308.58360.luke@dashjr.org>
Maybe I was too premature. The script wiki (which I realize might not be
up to date) says only one pushdata is allowed but I don't see that in
the code.
https://github.com/bitcoin/bitcoin/blob/e8cfe1ee2d01c493b758a67ad14707dca15792ea/src/policy/policy.cpp#L49
Am I missing something or am I correct to assume that multiple pushdatas
in op_return would normally be considered standard?
On 01/08/2017 10:08 PM, Luke Dashjr wrote:
> 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
>
prev parent reply other threads:[~2017-01-09 4:32 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
2017-01-09 4:32 ` Chris [this message]
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=7cc28f27-9917-6992-6de5-38fd91d42e29@gmail.com \
--to=ctpacia@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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