public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay•com>
To: Btc Drak <btcdrak@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind as a library
Date: Sun, 30 Nov 2014 11:38:42 -0500	[thread overview]
Message-ID: <CAJHLa0P6F0cqcNM33FK38xt0fLxRcYJbkUgdDE1nDSVHaa+MMw@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzuWussNgsMo8u=Q8cSEVzTpias0nxfGGhUmM4hk3OJa8g@mail.gmail.com>

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

Though I am highly biased :)  Compared to cbitcoin, picocoin's library
(libccoin) is valgrind-clean, can parse and index the blockchain, and
supports all core and P2P data structures.


On Fri, Nov 28, 2014 at 12:49 PM, Btc Drak <btcdrak@gmail•com> wrote:

> On Fri, Nov 28, 2014 at 5:22 PM, Oliver Egginger <bitcoin@olivere•de>
> wrote:
>
>> Sorry for the off-topic but while reading this I like to ask you for
>> picocoin, see:
>>
>> https://github.com/jgarzik/picocoin
>>
>> For a research project I'm looking for a C library to operate some block
>> chain analysis (parsing raw blocks and transactions).
>
>
> This might be useful for you https://github.com/MatthewLM/cbitcoin
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> 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: 2704 bytes --]

      reply	other threads:[~2014-11-30 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 17:27 Mem Wallet
2014-11-27 17:54 ` Wladimir
2014-11-27 20:07   ` odinn
2014-11-28 17:22   ` Oliver Egginger
2014-11-28 17:49     ` Btc Drak
2014-11-30 16:38       ` 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=CAJHLa0P6F0cqcNM33FK38xt0fLxRcYJbkUgdDE1nDSVHaa+MMw@mail.gmail.com \
    --to=jgarzik@bitpay$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=btcdrak@gmail$(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