From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ) 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 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: In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2014 17:22:07 -0000 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 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