Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXuZT-00053H-EC for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 15:37:51 +0000 X-ACL-Warn: Received: from wp059.webpack.hosteurope.de ([80.237.132.66]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WXuZR-0000FJ-Nr for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 15:37:51 +0000 Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated by wp059.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1WXuZL-0000Ic-8z; Wed, 09 Apr 2014 17:37:43 +0200 Content-Type: multipart/signed; boundary="Apple-Mail=_D7522D74-1362-4119-997B-C0815E34F735"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Tamas Blummer In-Reply-To: Date: Wed, 9 Apr 2014 17:37:43 +0200 Message-Id: <05F8CE60-8058-4616-B3CD-511D6972D36C@bitsofproof.com> References: To: Wladimir X-Mailer: Apple Mail (2.1874) X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1397057869; 215585a3; X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WXuZR-0000FJ-Nr Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets 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: Wed, 09 Apr 2014 15:37:51 -0000 --Apple-Mail=_D7522D74-1362-4119-997B-C0815E34F735 Content-Type: multipart/alternative; boundary="Apple-Mail=_9886D866-9CE0-4786-8513-3ABC2869A1AD" --Apple-Mail=_9886D866-9CE0-4786-8513-3ABC2869A1AD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii YES Such a bitcoind is what I called border router in a previous mail.=20 Yes, SPV wallets are getting ahead of features, so people will use them = also because on size just does not fit all, but all want to ensure being = on the same trunk of the chain. Therefore serious user of Bitcoin run a bitcoind as a border router and = connect SPV wallets with higher functionality to that trusted node(s). This is what I think the core should focus on: Being a lightweight = superfast consensus building border router and nothing more. No wallet, = no GUI, no RPC calls, no Payment protocol and the rest. Regards, Tamas Blummer http://bitsofproof.com On 09.04.2014, at 17:29, Wladimir wrote: > Hello, >=20 > This is primarily aimed at developers of SPV wallets. >=20 > 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. >=20 > It's great to see innovation in wallets, but it's worrying that the = number of full nodes decreases.=20 >=20 > 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). >=20 > 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. >=20 > In exchange the user would get increased (full node level) security, = as the SPV wallet would have a local trusted node. >=20 > Does this sound like a good idea? >=20 > 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? >=20 > Wladimir >=20 > = --------------------------------------------------------------------------= ---- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment=20 > Start a new project now. Try Jenkins in the cloud. > = http://p.sf.net/sfu/13600_Cloudbees_______________________________________= ________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --Apple-Mail=_9886D866-9CE0-4786-8513-3ABC2869A1AD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
YES

Such a bitcoind is what = I called border router in a previous mail. 

Yes, SPV wallets are getting ahead of features, so people will use them = also because on size just does not fit all, but all want to ensure being = on the same trunk of the chain.
Therefore serious user of Bitcoin run a = bitcoind as a border router and connect SPV wallets with higher = functionality to that trusted node(s).

This is what I think the core should focus = on: Being a lightweight superfast consensus building border router and = nothing more. No wallet, no GUI, no RPC calls,
no Payment protocol and the = rest.

Regards,

Tamas = Blummer
http://bitsofproof.com

On 09.04.2014, at 17:29, Wladimir <laanwj@gmail.com> = wrote:

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

= --------------------------------------------------------------------------= ----
Put Bad Developers to Shame
Dominate Development with Jenkins = Continuous Integration
Continuously Automate Build, Test & = Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_____________________= __________________________
Bitcoin-development mailing = list
Bitcoin-development@lists.sourceforge.net
https://lists.sourcef= orge.net/lists/listinfo/bitcoin-development

= --Apple-Mail=_9886D866-9CE0-4786-8513-3ABC2869A1AD-- --Apple-Mail=_D7522D74-1362-4119-997B-C0815E34F735 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJTRWlHAAoJEPZykcUXcTkc8ycIALRAFKe4XRJfwm0QCHQS8O9f ZkXT3fT55CB6yIIr2Eu+ykvmFH83dOgDwI2izK1HR4JGmBzCq6FPJnceD+E+gVcI IU46rKpTpbXPWVfFJ6jJmSmE2RoHCkX9NKRJFMt6iKUEPh+G1CT3ABpIGuT+mh2a LWJg1bj5YZevBJu5zsmcLGWqrdUKJKGshoxwUU/uzTU1MfMispBfd9jEOwlPlDSE qK7N28AH2caySCB5wC0D5dxhGSj6+kqS9IXSeAH9SxIR+thQUlfIA1fy2d/yuA4v yzi1JRXKJ6ea93sDhYSiP7RT9K8Q6IRjCBqSFMepGob4fF1TKKbcig8vDcoX3eM= =VGvQ -----END PGP SIGNATURE----- --Apple-Mail=_D7522D74-1362-4119-997B-C0815E34F735--