1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin@olivere.de>) id 1XuPF9-0000NT-7j
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Nov 2014 17:22:07 +0000
X-ACL-Warn:
Received: from olivere.de ([85.214.144.153] helo=mail.olivere.de)
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1XuPF7-00037y-5f
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Nov 2014 17:22:07 +0000
Received: from nat6-182.its.fh-giessen.de ([212.201.18.182]:1315
helo=[192.168.192.85])
by mail.olivere.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
(Exim 4.72) (envelope-from <bitcoin@olivere.de>) id 1XuPF0-0002eM-Eq
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Nov 2014 18:21:58 +0100
Message-ID: <5478AF53.1010506@olivere.de>
Date: Fri, 28 Nov 2014 18:22:27 +0100
From: Oliver Egginger <bitcoin@olivere.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAKzHBKnFHnc5+b0kU9=a0iG3HCU=mwx71DbQPk53Y91aPhA7eA@mail.gmail.com>
<CA+s+GJDKB7JoxiULAZ_22i6T0=LMw+78tmXRBs2HRoJJDAQSyQ@mail.gmail.com>
In-Reply-To: <CA+s+GJDKB7JoxiULAZ_22i6T0=LMw+78tmXRBs2HRoJJDAQSyQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1XuPF7-00037y-5f
Subject: Re: [Bitcoin-development] bitcoind as a library
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 28 Nov 2014 17:22:07 -0000
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
|
