From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin script opcode counts
Date: Thu, 26 Jul 2012 08:50:14 -0400 [thread overview]
Message-ID: <CAAS2fgS1meaVi+Azk7G-uXqdZzV9a2K0s5rxWvbHzAnruKRRXw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP331ipTK8pO6o1YmkiYR-c5-wH5vvZ=RrxBpHyu0BQ-vw@mail.gmail.com>
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 )
prev parent reply other threads:[~2012-07-26 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 5:50 Jeff Garzik
2012-07-26 5:55 ` Jeff Garzik
2012-07-26 11:27 ` Mike Hearn
2012-07-26 12:50 ` Gregory Maxwell [this message]
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=CAAS2fgS1meaVi+Azk7G-uXqdZzV9a2K0s5rxWvbHzAnruKRRXw@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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