From: Jeff Garzik <jgarzik@bitpay•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: Sun, 4 May 2014 09:25:35 -0400 [thread overview]
Message-ID: <CAJHLa0NDWjHFrYE4mQ1iB_70_=9Mg04-PiberkkaQmSdFDohEQ@mail.gmail.com> (raw)
In-Reply-To: <53654057.1080105@monetize.io>
On Sat, May 3, 2014 at 3:15 PM, Mark Friedenbach <mark@monetize•io> wrote:
> Is it more complex? The current implementation using template matching
> seems more complex than `if script.vch[0] == OP_RETURN &&
> script.vch.size() < 42`
Not much more complex.
The template matches a two-chunk script with OP_RETURN + one pushdata
(or just OP_RETURN with no push). The pushdata is further limited to
MAX_OP_RETURN_RELAY bytes.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-05-04 13:26 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
2014-05-03 19:08 ` Gregory Maxwell
2014-05-03 19:15 ` Mark Friedenbach
2014-05-04 13:25 ` Jeff Garzik [this message]
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='CAJHLa0NDWjHFrYE4mQ1iB_70_=9Mg04-PiberkkaQmSdFDohEQ@mail.gmail.com' \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@monetize$(echo .)io \
/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