Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.170 as permitted sender)
	client-ip=209.85.223.170; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f170.google.com; 
MIME-Version: 1.0
In-Reply-To: <534570A2.9090502@gmx.de>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
	<CAAt2M18z_Qkqat1OETiXAz0QQey4+y5J6=pC7nkoJfyfrpj3=A@mail.gmail.com>
	<CAAS2fgScWkentFy7Ak0bpYVLsOFL+xkwPm5QRu9ENeX9oCtPug@mail.gmail.com>
	<534570A2.9090502@gmx.de>
Date: Wed, 9 Apr 2014 21:25:13 +0200
Message-ID: <CA+s+GJAXu3SEXFDDwi85dNFjO2rfPXJrg-aKHYwbogAHfu3vfQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Thomas Voegtlin <thomasv1@gmx.de>
Content-Type: multipart/alternative; boundary=047d7b1117c14b99f704f6a10f14
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV
	wallets
Precedence: list

--047d7b1117c14b99f704f6a10f14
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 9, 2014 at 6:09 PM, Thomas Voegtlin <thomasv1@gmx.de> wrote:

> Le 09/04/2014 17:54, Gregory Maxwell a =C3=A9crit :
>
> > Sadly today Electrum requires more than a full node, it requires a
> > number of large additional indexes over what a full node has and
> > pruning is precluded. I don't think that increasing the resource
> > utilization of the node is a good way to go there for the purposes
> > expressed here. (not that electrum couldn't be used here, but not
> > unmodified without the resource usage increasing route)
> >
>
> Electrum uses two large indexes:
>
>      address -> utxo
>
> (patricia tree, aka "ultimate blockchain compression", see thread
> started by Alan Reiner in the bitcointalk forum)
>

Thanks for the explanation.

Adding a RPC call for a "address -> utxo" query wouldn't be a big deal. It
has been requested before for other purposes as well, all the better if it
helps for interaction with Electrum.

Spent history would be involve a much larger index, and it's not likely
that will end up in bitcoin

Wladimir

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Wed, Apr 9, 2014 at 6:09 PM, Thomas Voegtlin <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:thomasv1@gmx.de" target=3D"_blank">thomasv1@gmx.de</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Le 09/04/2014 17:54, Gregory Maxwell a =C3=
=A9crit :<br>
<div class=3D""><br>
&gt; Sadly today Electrum requires more than a full node, it requires a<br>
&gt; number of large additional indexes over what a full node has and<br>
&gt; pruning is precluded. I don&#39;t think that increasing the resource<b=
r>
&gt; utilization of the node is a good way to go there for the purposes<br>
&gt; expressed here. (not that electrum couldn&#39;t be used here, but not<=
br>
&gt; unmodified without the resource usage increasing route)<br>
&gt;<br>
<br>
</div>Electrum uses two large indexes:<br>
<br>
=C2=A0 =C2=A0 =C2=A0address -&gt; utxo<br>
<br>
(patricia tree, aka &quot;ultimate blockchain compression&quot;, see thread=
<br>
started by Alan Reiner in the bitcointalk forum)<br></blockquote><div><br><=
/div><div class=3D"h5">Thanks for the explanation.<br><br>Adding a RPC call=
 for a &quot;address -&gt; utxo&quot; query wouldn&#39;t be a big deal. It =
has been requested before for other purposes as well, all the better if it =
helps for interaction with Electrum.<br>
</div><div class=3D"h5"><br></div><div class=3D"h5">Spent history would be =
involve a much larger index, and it&#39;s not likely that will end up in bi=
tcoin<br></div><div class=3D"h5"><br>Wladimir<br><br></div></div></div></di=
v>

--047d7b1117c14b99f704f6a10f14--