From: Oliver Egginger <bitcoin@olivere•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] bitcoind as a library
Date: Fri, 28 Nov 2014 18:22:27 +0100 [thread overview]
Message-ID: <5478AF53.1010506@olivere.de> (raw)
In-Reply-To: <CA+s+GJDKB7JoxiULAZ_22i6T0=LMw+78tmXRBs2HRoJJDAQSyQ@mail.gmail.com>
On Thu, Nov 27, 2014 at 6:54 PM, Wladimir <laanwj@gmail•com> wrote:
> On Thu, Nov 27, 2014 at 5:27 PM, Mem Wallet <memwallet.info@gmail•com> 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 other project would have to fill such a role ?
>
> The plan is to provide the consensus functionality as a library, the
> essential parts that make bitcoin bitcoin.
> 0.10 will have a basic transaction/script verifier available.
> In the version after that, I expect this will be extended to further
> utxo set management, but no API has been worked out for that yet.
> There are also plans to add a library for transaction signing.
>
> However there is no goal to expose *everything* as a library.
> Certainly not wallet- or user interface related functionality.
> Specialized utility libraries would fill this purpose better.
> See for example https://github.com/bitcoin/libbase58 for base58 processing.
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). Has anyone of you
experience with picocoin for that? Are there any relevant limitations?
- oliver
next prev parent reply other threads:[~2014-11-28 17:22 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 [this message]
2014-11-28 17:49 ` Btc Drak
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=5478AF53.1010506@olivere.de \
--to=bitcoin@olivere$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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