public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mark Friedenbach <mark@monetize.io>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
Date: Sat, 3 May 2014 12:08:33 -0700	[thread overview]
Message-ID: <CAAS2fgS61rxB3x4ii68XTHC-V_jpfng-Px6Tv9GV20-putiLUQ@mail.gmail.com> (raw)
In-Reply-To: <53653B90.4070401@monetize.io>

On Sat, May 3, 2014 at 11:55 AM, Mark Friedenbach <mark@monetize.io> wrote:
> 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.

In this case it's not a question extra txouts, its a question of
additional pushes. Assuming you didn't get the push overhead for free,
the only issue I see with that off the cuff is extra complexity in the
IsStandard rule... but really, why?  Your application already needs to
define the meaning of the data— what point is there in making your
hash commitment less uniform with the rest of the network?



  reply	other threads:[~2014-05-03 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 18:04 [Bitcoin-development] Bug with handing of OP_RETURN? Flavien Charlon
2014-05-03 18:39 ` Peter Todd
2014-05-03 18:55   ` Mark Friedenbach
2014-05-03 19:08     ` Gregory Maxwell [this message]
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=CAAS2fgS61rxB3x4ii68XTHC-V_jpfng-Px6Tv9GV20-putiLUQ@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mark@monetize.io \
    /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