From: Jeff Garzik <jgarzik@bitpay.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol
Date: Sat, 15 Mar 2014 12:47:00 -0400 [thread overview]
Message-ID: <CAJHLa0OyS=mwD=9buthJ_AWKwybtNaRw1t-xPU6rG2FB9awA=w@mail.gmail.com> (raw)
In-Reply-To: <20140315143414.GA5308@savin>
Thanks -- though credit is really due to ArtForz, who kicked off this
project with his half-a-node: http://pastebin.com/ZSM7iHZw
On Sat, Mar 15, 2014 at 10:34 AM, Peter Todd <pete@petertodd.org> wrote:
> On Sat, Mar 15, 2014 at 09:43:40AM -0400, Peter Todd wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> I noticed that the ngccbase Colored Coin client(1) added a
>> python-bitcoinlib dependency, specifically my fork. In addition there is
>> also now a rudementary python-bitcoinlib package in archlinux.
>
> Also, for those who don't know the history of python-bitcoinlib, credit
> where credit is due: my fork is based on Jeff Garzik's implementation(1)
> and the bulk of the code structure is his work, modulo "pythonizing"
> that I have done.
>
> 1) https://github.com/jgarzik/python-bitcoinlib
>
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000090aa23d86521312897686912946b38e93a71a98a8c287d4a
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-03-15 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 13:43 [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol Peter Todd
2014-03-15 14:34 ` Peter Todd
2014-03-15 16:47 ` Jeff Garzik [this message]
2014-03-15 16:47 ` Jeff Garzik
2014-03-15 17:12 ` Drak
2014-03-15 17:21 ` Jeff Garzik
2014-03-15 17:22 ` Peter Todd
2014-03-15 18:04 ` Drak
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='CAJHLa0OyS=mwD=9buthJ_AWKwybtNaRw1t-xPU6rG2FB9awA=w@mail.gmail.com' \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pete@petertodd.org \
/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