From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Xu5Ls-0000wT-Iu for bitcoin-development@lists.sourceforge.net; Thu, 27 Nov 2014 20:07:44 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of riseup.net designates 198.252.153.129 as permitted sender) client-ip=198.252.153.129; envelope-from=odinn.cyberguerrilla@riseup.net; helo=mx1.riseup.net; Received: from mx1.riseup.net ([198.252.153.129]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Xu5Lr-0003cs-14 for bitcoin-development@lists.sourceforge.net; Thu, 27 Nov 2014 20:07:44 +0000 Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 0543040DCC; Thu, 27 Nov 2014 20:07:37 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: odinn.cyberguerrilla) with ESMTPSA id 4127241FFD Message-ID: <54778481.9020002@riseup.net> Date: Thu, 27 Nov 2014 20:07:29 +0000 From: odinn MIME-Version: 1.0 To: Wladimir , Mem Wallet References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 X-Virus-Scanned: clamav-milter 0.98.4 at mx1 X-Virus-Status: Clean Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [198.252.153.129 listed in list.dnswl.org] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Headers-End: 1Xu5Lr-0003cs-14 Cc: Bitcoin Dev 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: Thu, 27 Nov 2014 20:07:44 -0000 -----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 project were broken out as distinct repositories - see: https://github.com/darkwallet/stealth.js and https://github.com/darkwallet/coinjoin.js installable using npm I'm probably missing something here, but it seems to me like breaking things out as distinct repositories might be a good approach. The question is what would be in a distinct repository or repositories? Currently if someone is looking at core, everything is seen here: https://github.com/bitcoin/bitcoin/ Wladimir: > On Thu, Nov 27, 2014 at 5:27 PM, Mem Wallet > wrote: >=20 >> 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 ? >=20 > 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. >=20 > However there is no goal to expose *everything* as a library.=20 > Certainly not wallet- or user interface related functionality.=20 > Specialized utility libraries would fill this purpose better. See > for example https://github.com/bitcoin/libbase58 for base58 > processing. >=20 > Wladimir >=20 > -----------------------------------------------------------------------= ------- > >=20 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and > Dashboards with Interactivity, Sharing, Native Excel Exports, App > Integration & more Get technology previously reserved for > billion-dollar corporations, FREE=20 > http://pubads.g.doubleclick.net/gampad/clk?id=3D157005751&iu=3D/4140/os= tg.clktrk > >=20 _______________________________________________ > Bitcoin-development mailing list=20 > Bitcoin-development@lists.sourceforge.net=20 > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >=20 - --=20 http://abis.io ~ "a protocol concept to enable decentralization and expansion of a giving economy, and a new social good" https://keybase.io/odinn -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJUd4SAAAoJEGxwq/inSG8Che8H/3PMt0NQSrVSqnC6WC9scXdD aqGnsdZkhnLRs0szJSTjiQm+xCk6aUcEsKCGu298Xhkv38S4DSfWa+OhFZGPKmOZ wlfnXAz3SprQ8xzy/NVqavtFRk+pGDRxgBIzzgBfbz3BdPKxMywi9BNnaK0YA6UA 08giKmtqblHTKmKuguK23YIYjAAk3Csg0Vg4BgN2MgeEXl9PJI6vh4+jNckXWtAT /gKjPXG/Q+f9wl5pxSY/+ZfmRUtjHye3f8hHjpSEmxjpB9QzeeDg63DzAhOH0ip5 vXaIePZED//SmN3eH+S22vAx/a83URkr5B2+8Cffx/oO5laYRthoMHLi/2+XkO4=3D =3DUWhs -----END PGP SIGNATURE-----