Re: [Bitcoin-development] bitcoind as a library

2014-11-30 Thread Jeff Garzik
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 wrote: > On Fri, Nov 28, 2014 at 5:22 PM, Oliver Egginger > wrote:

Re: [Bitcoin-development] bitcoind as a library

2014-11-28 Thread Btc Drak
On Fri, Nov 28, 2014 at 5:22 PM, Oliver Egginger 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

Re: [Bitcoin-development] bitcoind as a library

2014-11-28 Thread Oliver Egginger
On Thu, Nov 27, 2014 at 6:54 PM, Wladimir wrote: > On Thu, Nov 27, 2014 at 5:27 PM, Mem Wallet wrote: > >> Is there an intention that the various internal libraries could/should >> be strengthened and heirachicalized such that they would be suitable for >> 3rd party development of bitcoin relate

Re: [Bitcoin-development] bitcoind as a library

2014-11-27 Thread odinn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 A recent comment on this (I think)... https://github.com/bitcoin/bitcoin/issues/4564#issuecomment-49558760 Reflecting on an approach from a different but related project, as a result of an issue discussion in DW, stealth and coinjoin from that pr

Re: [Bitcoin-development] bitcoind as a library

2014-11-27 Thread Wladimir
On Thu, Nov 27, 2014 at 5:27 PM, Mem Wallet wrote: > Is there an intention that the various internal libraries could/should > be strengthened and heirachicalized such that they would be suitable for > 3rd party development of bitcoin related services and tools, or is that not > a goal, and some o

[Bitcoin-development] bitcoind as a library

2014-11-27 Thread Mem Wallet
Two minor observations: DecodeBase58Check is listed as inline, but isnt actually inlined in the header. This makes it both non-present in libbitcoin_common.a and unavailable to other code that would use libbitcoin_common.a as a library. (bug?) In general, the hierarchy of tools is poor/weak. for