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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1SuNWL-0003iS-D7
for bitcoin-development@lists.sourceforge.net;
Thu, 26 Jul 2012 12:50:25 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=gmaxwell@gmail.com;
helo=mail-pb0-f47.google.com;
Received: from mail-pb0-f47.google.com ([209.85.160.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SuNWF-0001TW-VM
for bitcoin-development@lists.sourceforge.net;
Thu, 26 Jul 2012 12:50:25 +0000
Received: by pbbrq2 with SMTP id rq2so2984763pbb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 26 Jul 2012 05:50:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.232.103 with SMTP id tn7mr4838567pbc.86.1343307014042; Thu,
26 Jul 2012 05:50:14 -0700 (PDT)
Received: by 10.68.59.6 with HTTP; Thu, 26 Jul 2012 05:50:14 -0700 (PDT)
In-Reply-To: <CANEZrP331ipTK8pO6o1YmkiYR-c5-wH5vvZ=RrxBpHyu0BQ-vw@mail.gmail.com>
References: <CA+8xBpdH8CnCeW=syWLt-V2nF+jmE5V1T=cJGGJxxt1M6dw3OA@mail.gmail.com>
<CANEZrP331ipTK8pO6o1YmkiYR-c5-wH5vvZ=RrxBpHyu0BQ-vw@mail.gmail.com>
Date: Thu, 26 Jul 2012 08:50:14 -0400
Message-ID: <CAAS2fgS1meaVi+Azk7G-uXqdZzV9a2K0s5rxWvbHzAnruKRRXw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.1 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-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
0.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SuNWF-0001TW-VM
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin script opcode counts
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: Thu, 26 Jul 2012 12:50:25 -0000
On Thu, Jul 26, 2012 at 7:27 AM, Mike Hearn <mike@plan99.net> wrote:
>> OP_CODESEPARATOR 14
>> OP_DEPTH 182
>
> I'm interested to see what scripts were using OP_DEPTH and
> OP_CODESEPARATOR, as the latter appears to be useless to my eyes.
>
> Could you give some tx ids which use unusual opcodes?
The OP_DEPTH are all screwups in P2Pool blocks.
( the software was making tiny payments to scriptpubkey 'script' due
to a bug, and it went unnoticed for a long time because it was assumed
that it was just some p2sh user intentionally being stupid )
|
