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; 
MIME-Version: 1.0
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
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin script opcode counts
Precedence: list

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 )