From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WOsHc-00089H-DM for bitcoin-development@lists.sourceforge.net; Sat, 15 Mar 2014 17:22:04 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.172 as permitted sender) client-ip=209.85.212.172; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f172.google.com; Received: from mail-wi0-f172.google.com ([209.85.212.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WOsHb-0001In-5P for bitcoin-development@lists.sourceforge.net; Sat, 15 Mar 2014 17:22:04 +0000 Received: by mail-wi0-f172.google.com with SMTP id hi5so687766wib.17 for ; Sat, 15 Mar 2014 10:21:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5Z6sbvwAVOB0VdjVEl4S4ZR8vs1Uu5bMVmaxb3Kxtv0=; b=V3QNFBQzGTwnm3eMeo8etifkD7Y4ELRZ2PAfUdXFsPARShBAoeU1t3OiplQRMGq12R NHeaq4Vp7oNeDgyHJ6m3agMYiuRwxxU+5/qqp6DiD3wljMg+o3MH8Lf3FZJ+cNlGqjJp 7ggrkik9kLnpmEPNWu6TUC+ZbPDVtjkLZxeQyZbw7diiWVpOOpSZSUycfx1+6LlHHMZR cmBxKrqigco5Sl5WUvPHYR3yiScrpsRfsMAmzcH0Y18bg4mpW7qRldIIfh25Mt7jHaQN 3bbmVyc5zh2OTKzn9uEK+qxNukNvnRW1PaNUn/jgY8LD+8PIkXcvoQjdPqaL+L4Tjd4n RsmQ== X-Gm-Message-State: ALoCoQmGWpFA+6tJ4bAmrqM4HrxkebkoHhW0D6bCFJ7weoEhoGDlTK77hiyZJf7OX9hvsIU+jB2S X-Received: by 10.194.192.132 with SMTP id hg4mr11830314wjc.28.1394904116999; Sat, 15 Mar 2014 10:21:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Sat, 15 Mar 2014 10:21:36 -0700 (PDT) In-Reply-To: References: <20140315134340.GA12937@savin> From: Jeff Garzik Date: Sat, 15 Mar 2014 13:21:36 -0400 Message-ID: To: Drak Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WOsHb-0001In-5P Cc: Bitcoin Dev , Andy Weidenbaum , Alex Mizrahi Subject: Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2014 17:22:04 -0000 I am happy to do whatever makes the new maintainer and users most happy. That includes giving the new maintainer commit privs in my repo. On Sat, Mar 15, 2014 at 1:12 PM, Drak wrote: > Would it make sense to pull that stuff in and add Peter with commit access > since your repo is top of the fork tree. > > Drak > > > On 15 March 2014 16:47, Jeff Garzik wrote: >> >> Sounds great. I'm glad to see this with a more active maintainer. >> Maintaining -three- client libs was a bit much for me. >> >> On Sat, Mar 15, 2014 at 9:43 AM, 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. >> > >> > So with that in mind I'm releasing v0.1, perhaps somewhat arbitrarily: >> > >> > https://github.com/petertodd/python-bitcoinlib/tree/v0.1 >> > >> > This Python2/3 library provides an easy interface to the bitcoin data >> > structures and protocol. The approach is low-level and "ground up", with >> > a focus on providing tools to manipulate the internals of how Bitcoin >> > works in a Pythonic way, without straying far from the Bitcoin Core >> > implementation. >> > >> > The current status of the library as of v0.1 is that the support for >> > data-structures related to transactions, scripting, addresses, and keys >> > are all quite usable and the API is probably not going to change that >> > much. Bitcoin Core RPC support is included and automatically converts >> > the JSON to/from Python objects when appropriate. EvalScript(), >> > VerifyScript(), and SignatureHash() are all functional and pass all the >> > Bitcoin Core unittests, as well as a few that are still yet to be >> > merged.(2) You'll find some examples for signing pay2script-hash and >> > p2sh txouts in the examples/ directory; I personally used the >> > transaction signing functionality to make up a set of unittests related >> > to OP_CODESEPARATOR and FindAndDelete() recently. Finally my dust-b-gone >> > script(3) is another good example, specifically of the RPC >> > functionality. >> > >> > I personally haven't had any need for the p2p network related code for >> > some time, so I'm sure it's not in a good state and it lacks unittests; >> > Bloom filters for one are missing the merkle-block support to actually >> > make them useful. But the RPC support makes up for that for many uses. >> > >> > This release and others in the future are signed by my PGP key, as well >> > as every publicly pushed commit. You can verify the key via WoT, my >> > bitcointalk account, signing history in the Bitcoin Core repo, and >> > mailing list records among other sources. >> > >> > Disclaimer: This is alpha code in a language not known for type-safety. >> > I wouldn't personally use python-bitcoinlib for anything >> > other than experiments and neither should you. >> > >> > 1) https://github.com/bitcoinx/ngcccbase >> > 2) https://github.com/bitcoin/bitcoin/pull/3861 >> > 3) https://github.com/petertodd/dust-b-gone >> > >> > - -- >> > 'peter'[:-1]@petertodd.org >> > 000000000000000097649e8d66395b3cb4527263409adf628c76cc56af0434fe >> > -----BEGIN PGP SIGNATURE----- >> > Version: GnuPG v1.4.14 (GNU/Linux) >> > >> > iQGrBAEBCACVBQJTJFkFXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw >> > MDAwMDAwMDAwMDAwMDA3OGEyNGUxNTBlNTc2ZGVjZWUyYWQzMGNhMmE2YTRhMmM3 >> > NGVkYmJkNjM2NDViNjcvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 >> > ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftZiwgAk8YVN9t76tKIKcWKyrGgv8yk >> > UZGZkkrowED0lyhMXfmviezeWhjvHZgQrwha2hAuik36WEBN1jnv9wuJ6g9tnxGY >> > PyG8n1SV2rtQ/QIJyL6wOuqL3UZi6d6IdZ/udVmyGwz+XhE89AwitR0++MvxkPNv >> > i9R3Gw5Z1CnS2W0jGpAT88k3q3pqEzbYutP/FaylL2+6MuSUGwHUoY8dqcRkwkw1 >> > eIrd2W33x4NvuxYPLnHR64uE0B8KoreZOyyskMdeMsKtZNflkfgfMiD10xnw2PGx >> > z8S42wPbrI5ZYLL1OLdRfuKMdQ4qOyF4jfV+QRZWQ5t5Qh1akVWmz7ffFHGo0Q== >> > =k1pi >> > -----END PGP SIGNATURE----- >> >> >> >> -- >> Jeff Garzik >> Bitcoin core developer and open source evangelist >> BitPay, Inc. https://bitpay.com/ >> >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today! >> http://p.sf.net/sfu/13534_NeoTech >> _______________________________________________ >> 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/