public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay•com>
To: Richard Moore <me@ricmoo•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Looking for a good bitcoin script decompiler in Python
Date: Wed, 29 Apr 2015 19:27:19 -0400	[thread overview]
Message-ID: <CAJHLa0Pmv_XwNdcwy2JUeCpPHhj5nN-RQHzgYnVXKqUtPWxkZw@mail.gmail.com> (raw)
In-Reply-To: <09C6C0EA-FE0B-43B4-9114-6482F9CF45BA@ricmoo.com>

[-- Attachment #1: Type: text/plain, Size: 2391 bytes --]

python-bitcoinlib supports script parsing and execution.


On Wed, Apr 29, 2015 at 6:16 PM, Richard Moore <me@ricmoo•com> wrote:

> I have a library, pycoind (https://github.com/ricmoo/pycoind) you might
> find useful.
>
>
> >>> import pycoind
>
> >>>
> str(pycoind.script.Tokenizer('76a9143f320f852a51643d3ffbaa1f49bfe521dd97764a88ac'.decode('hex')))
> 'OP_DUP OP_HASH160 3f320f852a51643d3ffbaa1f49bfe521dd97764a OP_EQUALVERIFY
> OP_CHECKSIG'
>
>
>
>
> On Apr 29, 2015, at 1:12 PM, Braun Brelin <bbrelin@gmail•com> wrote:
>
> Hi all,
>
> I'm trying to find a good python script that will take the hash of the
> locking and
> unlocking tx scripts and output the actual op codes.
>
> Any ideas where to look?
>
> Thanks,
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
>
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> .·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>
>
> Richard Moore ~ Founder
> Genetic Mistakes Software inc.
> phone: (778) 882-6125
> email: ricmoo@geneticmistakes•com
> www: http://GeneticMistakes.com
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>


-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

[-- Attachment #2: Type: text/html, Size: 4343 bytes --]

      reply	other threads:[~2015-04-29 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 17:12 Braun Brelin
2015-04-29 22:16 ` Richard Moore
2015-04-29 23:27   ` Jeff Garzik [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=CAJHLa0Pmv_XwNdcwy2JUeCpPHhj5nN-RQHzgYnVXKqUtPWxkZw@mail.gmail.com \
    --to=jgarzik@bitpay$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=me@ricmoo$(echo .)com \
    /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