From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin script opcode counts
Date: Thu, 26 Jul 2012 13:27:30 +0200 [thread overview]
Message-ID: <CANEZrP331ipTK8pO6o1YmkiYR-c5-wH5vvZ=RrxBpHyu0BQ-vw@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpdH8CnCeW=syWLt-V2nF+jmE5V1T=cJGGJxxt1M6dw3OA@mail.gmail.com>
> 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?
next prev parent reply other threads:[~2012-07-26 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 5:50 [Bitcoin-development] Bitcoin script opcode counts Jeff Garzik
2012-07-26 5:55 ` Jeff Garzik
2012-07-26 11:27 ` Mike Hearn [this message]
2012-07-26 12:50 ` Gregory Maxwell
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='CANEZrP331ipTK8pO6o1YmkiYR-c5-wH5vvZ=RrxBpHyu0BQ-vw@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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