From: Mark Friedenbach <mark@monetize•io>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
Date: Sat, 03 May 2014 11:55:12 -0700 [thread overview]
Message-ID: <53653B90.4070401@monetize.io> (raw)
In-Reply-To: <218332ea-948d-4af0-b4c5-ced83f25d734@email.android.com>
I don't think such a pull request would be accepted. The point was to
minimize impact to the block chain. Each extras txout adds 9 bytes
minimum, with zero benefit over serializing the data together in a
single OP_RETURN.
On 05/03/2014 11:39 AM, Peter Todd wrote:
> The standard format ended up being exactly:
>
> OP_RETURN <0 to 40-byte PUSHDATA>
>
> You've split the data across two PUSHDATA's. The standard should have let the data be split up like that; pull requests accepted.
>
next prev parent reply other threads:[~2014-05-03 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 18:04 Flavien Charlon
2014-05-03 18:39 ` Peter Todd
2014-05-03 18:55 ` Mark Friedenbach [this message]
2014-05-03 19:08 ` Gregory Maxwell
2014-05-03 19:15 ` Mark Friedenbach
2014-05-04 13:25 ` Jeff Garzik
2014-05-04 12:07 ` Sergio Lerner
2014-05-05 17:30 ` Jeff Garzik
2014-05-04 5:15 ` Jeff Garzik
2014-05-04 10:05 ` Flavien Charlon
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=53653B90.4070401@monetize.io \
--to=mark@monetize$(echo .)io \
--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