Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.180 as permitted sender)
	client-ip=209.85.213.180; envelope-from=laanwj@gmail.com;
	helo=mail-ig0-f180.google.com; 
MIME-Version: 1.0
Date: Wed, 9 Apr 2014 17:29:32 +0200
Message-ID: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e015384fe718f5304f69dc419
Subject: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets
Precedence: list

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

Hello,

This is primarily aimed at developers of SPV wallets.

The recently reported decrease in number of full nodes could have several
reasons, one of them that less people are running Bitcoin Core for the
wallet because the other wallets are getting ahead in both features and
useability.

It's great to see innovation in wallets, but it's worrying that the number
of full nodes decreases.

It may be that lots of people would support the network by running a full
node, but don't want to go through the trouble of installing bitcoin core
separately (and get confused because it's a wallet, too).

Hence I'd like to explore the idea of adding an option to popular SPV
wallets, to spin a bitcoind process in the background. This could be pretty
much transparent to the user - it would sync in the background, the wallet
could show statistics about the node, but is not dependent on it.

In exchange the user would get increased (full node level) security, as the
SPV wallet would have a local trusted node.

Does this sound like a good idea?

Is there any way that Bitcoin Core can help to accomedate this 'embedded'
usage? Specific Interfaces, special builds - maybe add a walletless
bitcoind build to gitian - bindings, dlls, etc?

Wladimir

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

<div dir=3D"ltr"><div><div><div>Hello,<br><br>This is primarily aimed at de=
velopers of SPV wallets.<br><br></div>The recently reported decrease in num=
ber of full nodes could have several reasons, one of them that less people =
are running Bitcoin Core for the wallet because the other wallets are getti=
ng ahead in both features and useability.<br>
<br>It&#39;s great to see innovation in wallets, but it&#39;s worrying that=
 the number of full nodes decreases. <br><br>It may be that lots of people =
would support the network by running a full node, but don&#39;t want to go =
through the trouble of installing bitcoin core separately (and get confused=
 because it&#39;s a wallet, too).<br>
</div><div><br></div>Hence I&#39;d like to explore the idea of adding an op=
tion to popular SPV wallets, to spin a bitcoind process in the background. =
This could be pretty much transparent to the user - it would sync in the ba=
ckground, the wallet could show statistics about the node, but is not depen=
dent on it.<br>
<br>In exchange the user would get increased (full node level) security, as=
 the SPV wallet would have a local trusted node.<br><br></div><div>Does thi=
s sound like a good idea?<br></div><div><br></div>Is there any way that Bit=
coin Core can help to accomedate this &#39;embedded&#39; usage? Specific In=
terfaces, special builds - maybe add a walletless bitcoind build to gitian =
- bindings, dlls, etc?<br>
<div><div><div><br>Wladimir<br><br></div></div></div></div>

--089e015384fe718f5304f69dc419--