Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.174 as permitted sender)
	client-ip=209.85.223.174; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f174.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAJna-Hj1U5cQ22bSXoNB-4ck_urCuS9xCk+iEHsbh+yv17MP7A@mail.gmail.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
	<CAADm4BCEFCiOpNzUThPPHUamP2256izU8pwD3nerLCxks0wENA@mail.gmail.com>
	<CAAS2fgTx40XSLhiygnJMrSbOC=iJ2YMVLNK7-AMt3ifvAHDZUA@mail.gmail.com>
	<E9BAD633-3B6A-4A2C-AA06-DB591973DF66@bitsofproof.com>
	<53456B99.9010207@monetize.io>
	<B2FEC170-7214-4E46-8830-153995870B62@bitsofproof.com>
	<00b77560-d7ed-4ed4-a4e5-eb1f00467a06@email.android.com>
	<0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com>
	<CANEZrP2Q=TG+jejEVFFh5FhjzDDkySHNSTfwtKueLcHu=pB6Kw@mail.gmail.com>
	<CA+s+GJBRvDFgktTgW2sCvAVahrjxcGqfgHw0BVNPvwUupotVrg@mail.gmail.com>
	<534592E2.7040800@gmail.com>
	<CAAS2fgS3q6N9go-NSKdjLwgU_5bFwa8YE88DcjNYHQTwzPCn3Q@mail.gmail.com>
	<5345986C.3040901@gmail.com>
	<CAAS2fgQyXHNnBDKoUMd_=-=1irGJ6cFKwi59enLJvFJiWBv50A@mail.gmail.com>
	<CAJna-Hj1U5cQ22bSXoNB-4ck_urCuS9xCk+iEHsbh+yv17MP7A@mail.gmail.com>
Date: Wed, 9 Apr 2014 22:35:13 +0200
Message-ID: <CA+s+GJA0EqvZB3Bi75W+-Pfkjg=3=-wafjSBPMCnd_vbi2F-0w@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=089e01183c36a8819504f6a209a1
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV
	wallets
Precedence: list

--089e01183c36a8819504f6a209a1
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 9, 2014 at 10:12 PM, slush <slush@centrum.cz> wrote:

> Maybe there're other ideas how to improve current situation without needs
> of reworking the architecture.
>

Nothing I've proposed here would require larger changes to the architecture
then were already planned. After SPV lands we are going to split off the
wallet, and that will need an interface to an bitcoind to allow 'running
with full node'. If that can be generalized to be useful for other (SPV)
clients as well, that would be useful, hence I asked for input.

It of course doesn't preclude also looking for other solutions.

Wladimir

--089e01183c36a8819504f6a209a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Apr 9, 2014 at 10:12 PM, slush <span dir=3D"ltr">&lt;<a href=3D=
"mailto:slush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Maybe there&#39;re other id=
eas how to improve current situation without needs of reworking the archite=
cture.</div>
</blockquote><div><br></div><div>Nothing I&#39;ve proposed here would requi=
re larger changes to the architecture then were already planned. After SPV =
lands we are going to split off the wallet, and that will need an interface=
 to an bitcoind to allow &#39;running with full node&#39;. If that can be g=
eneralized to be useful for other (SPV) clients as well, that would be usef=
ul, hence I asked for input. <br>
<br></div><div>It of course doesn&#39;t preclude also looking for other sol=
utions.<br></div><div><br></div><div>Wladimir<br><br></div></div></div></di=
v>

--089e01183c36a8819504f6a209a1--