From: Btc Drak <btcdrak@gmail•com>
To: Oliver Egginger <bitcoin@olivere•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind as a library
Date: Fri, 28 Nov 2014 17:49:25 +0000 [thread overview]
Message-ID: <CADJgMzuWussNgsMo8u=Q8cSEVzTpias0nxfGGhUmM4hk3OJa8g@mail.gmail.com> (raw)
In-Reply-To: <5478AF53.1010506@olivere.de>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 920 bytes --]
next prev parent reply other threads:[~2014-11-28 17:49 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 [this message]
2014-11-30 16:38 ` Jeff Garzik
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='CADJgMzuWussNgsMo8u=Q8cSEVzTpias0nxfGGhUmM4hk3OJa8g@mail.gmail.com' \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin@olivere$(echo .)de \
/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