[Bitcoin-development] Bug with handing of OP_RETURN?

Jeff Garzik jgarzik at bitpay.com
Mon May 5 17:30:02 UTC 2014


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 at 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 at 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/




More information about the bitcoin-dev mailing list