public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Flavien Charlon <flavien.charlon@coinprism.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
Date: Sun, 4 May 2014 11:05:36 +0100	[thread overview]
Message-ID: <CABbpET9W28zKKWjXTDm6k6ka48+giy7JQBAbDBtJNsS3WqRv-g@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0NPJgZqgxhGYrFXdHwAgYNnE_At7tDzLb2V=K5TnXO7FQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

Thanks, that makes sense, just wanted to make sure this what the problem
was.


On Sun, May 4, 2014 at 6:15 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:

> On Sat, May 3, 2014 at 2:04 PM, Flavien Charlon
> <flavien.charlon@coinprism.com> wrote:
> > Outputs are above dust, inputs are not spent. OP_RETURN is supposed to be
> > standard in 0.9.1 and the data is well below 40 bytes, so why is this
> being
> > rejected?
>
> The carried data must all be contained within one pushdata.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>

[-- Attachment #2: Type: text/html, Size: 1118 bytes --]

      reply	other threads:[~2014-05-04 10:06 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
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 [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=CABbpET9W28zKKWjXTDm6k6ka48+giy7JQBAbDBtJNsS3WqRv-g@mail.gmail.com \
    --to=flavien.charlon@coinprism.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /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