1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WhMik-0002vn-2X
for bitcoin-development@lists.sourceforge.net;
Mon, 05 May 2014 17:30:30 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.182 as permitted sender)
client-ip=209.85.212.182; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f182.google.com;
Received: from mail-wi0-f182.google.com ([209.85.212.182])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WhMii-0006hH-UR
for bitcoin-development@lists.sourceforge.net;
Mon, 05 May 2014 17:30:30 +0000
Received: by mail-wi0-f182.google.com with SMTP id r20so2633675wiv.3
for <bitcoin-development@lists.sourceforge.net>;
Mon, 05 May 2014 10:30:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type:content-transfer-encoding;
bh=KLFsMqPlH3ztCwcIHldg/u5xak1RBl9ZKrdtyf/ndsU=;
b=dtW2KIs2dTfMjynB/XofK26cBOo9mrnOUcFri0dEjudn7IsJlnm4ArGYx5lUYWHKky
If4JEiWyPZW6Of/YB0NxPNeM149sYnf9fVhS9l75E5a/lPiH4dwuHqGDGsSYCnEbwdMl
aiAQAbp90Z6NJAgI+SyJMHRwLTno+t3Q5Ija0mvzt7u3gn/5GUsO3MMG6cqYVzWPTspp
V4hsJUFzpgoFnR1CQgnGlj6e7tSXeACGopGLsHinc2xs+pr89VwGIVbU2AYkQhPYcVhv
k0kyhzuFfPfBSvd26+o24xVRYIBozMXcntaKd4kIn/oHT/VuYU1ADF4HYhYsLiIj+vx1
1Cow==
X-Gm-Message-State: ALoCoQmXZuwwUsyBostg2StT17LXRVZ3Ap3uXNdVSTY8O7f9gChx67K23n8NUL2hs4QamSzeLqfw
X-Received: by 10.180.14.72 with SMTP id n8mr17048224wic.53.1399311022618;
Mon, 05 May 2014 10:30:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.243.138 with HTTP; Mon, 5 May 2014 10:30:02 -0700 (PDT)
In-Reply-To: <53662D89.5070106@certimix.com>
References: <CABbpET-uDQRFQ_XAFeWkgc=A1jEW62Q+8BTZZuW5UbZXX0y+HQ@mail.gmail.com>
<218332ea-948d-4af0-b4c5-ced83f25d734@email.android.com>
<53653B90.4070401@monetize.io> <53662D89.5070106@certimix.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 5 May 2014 13:30:02 -0400
Message-ID: <CAJHLa0MSmbVsYccqzsNjyMMGT1Ffy3ULTJ_O9jv3ZbDHMpVbkQ@mail.gmail.com>
To: Sergio Lerner <sergiolerner@certimix.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WhMii-0006hH-UR
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2014 17:30:30 -0000
Correct, though that was somewhat unintentional. The pushed-data size
is limited to <=3D 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> w=
rote:
> El 03/05/2014 03:55 p.m., Mark Friedenbach escribi=C3=B3:
>>
>> 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 availabl=
e.
> 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
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
