From: Jeff Garzik <jgarzik@bitpay.com>
To: Sergio Lerner <sergiolerner@certimix.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
Date: Mon, 5 May 2014 13:30:02 -0400 [thread overview]
Message-ID: <CAJHLa0MSmbVsYccqzsNjyMMGT1Ffy3ULTJ_O9jv3ZbDHMpVbkQ@mail.gmail.com> (raw)
In-Reply-To: <53662D89.5070106@certimix.com>
Correct, though that was somewhat unintentional. The pushed-data size
is limited to <= 40 bytes, and as non-pushdata opcodes carry zero
pushed data, they are accepted.
On Sun, May 4, 2014 at 8:07 AM, Sergio Lerner <sergiolerner@certimix.com> wrote:
> El 03/05/2014 03:55 p.m., Mark Friedenbach escribió:
>>
>> On 05/03/2014 11:39 AM, Peter Todd wrote:
>>> The standard format ended up being exactly:
>>>
>>> OP_RETURN <0 to 40-byte PUSHDATA>
>>>
> Please remember that the code actually does not implement the "standard
> format" (at least the last time I checked it). Any opcode after
> OP_RETURN is accepted:
>
> For example: OP_RETURN OP_CHECKSIG
>
> is accepted.
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-05-05 17:30 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 [this message]
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=CAJHLa0MSmbVsYccqzsNjyMMGT1Ffy3ULTJ_O9jv3ZbDHMpVbkQ@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=sergiolerner@certimix.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