+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]

+ helo=mx.sourceforge.net)

+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)

+ (envelope-from <pete@petertodd.org>) id 1WXvJv-0001ma-K7

+ for bitcoin-development@lists.sourceforge.net;

+ Wed, 09 Apr 2014 16:25:51 +0000

+Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org

+ designates 62.13.148.96 as permitted sender)

+ client-ip=62.13.148.96; envelope-from=pete@petertodd.org;

+ helo=outmail148096.authsmtp.net;

+Received: from outmail148096.authsmtp.net ([62.13.148.96])

+ by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)

+ id 1WXvJt-0006a8-FP for bitcoin-development@lists.sourceforge.net;

+ Wed, 09 Apr 2014 16:25:51 +0000

+Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])

+ by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s39GPgvs026810;

+ Wed, 9 Apr 2014 17:25:42 +0100 (BST)

+Received: from [25.125.109.65] ([24.114.70.19]) (authenticated bits=0)

+ by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s39GPdqE043599

+ (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);

+ Wed, 9 Apr 2014 17:25:40 +0100 (BST)

+User-Agent: K-9 Mail for Android

+In-Reply-To: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>

+References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>

+MIME-Version: 1.0

+Content-Transfer-Encoding: 8bit

+Content-Type: text/plain;

+ charset=UTF-8

+From: Peter Todd <pete@petertodd.org>

+Date: Wed, 09 Apr 2014 12:03:08 -0400

+To: Wladimir <laanwj@gmail.com>,

+ Bitcoin Dev <bitcoin-development@lists.sourceforge.net>

+Message-ID: <a591551b-1a5b-4fdc-8e4a-1a1dae4242f4@email.android.com>

+X-Server-Quench: 97b34e4f-c003-11e3-b802-002590a15da7

+X-AuthReport-Spam: If SPAM / abuse - report it at:

+ http://www.authsmtp.com/abuse

+X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR

+ aAdMdgsUGUUGAgsB AmIbWlNeUlh7XWI7 aQ5PbARZfE1OQQRj

+ T0xPR01TWkZrCGth Ul9rUh1xcgxPNn9y ZUZhEHlcDkd+IEIr

+ Xx1UFW4bZGY1a31N WEBaagNUcgZDfk5E bwQuUz1vNG8XDQg5

+ AwQ0PjZ0MThBJSBS WgQAK04nCWwKAjU7 RhYOWDQpWEcMTCY8

+ NRs7LFJUGUEdPw08 NkFpYmomewAbDglT A1ol

+X-Authentic-SMTP: 61633532353630.1023:706

+X-AuthFastPath: 0 (Was 255)

+X-AuthSMTP-Origin: 24.114.70.19/465

+X-AuthVirus-Status: No virus detected - but ensure you scan with your own

+ anti-virus system.

+X-Spam-Score: -1.5 (-)

+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.

+ See http://spamassassin.org/tag/ for more details.

+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for

+ sender-domain

+ -0.0 SPF_PASS SPF: sender matches SPF record

+X-Headers-End: 1WXvJt-0006a8-FP

+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: <bitcoin-development.lists.sourceforge.net>

+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,

+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>

+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>

+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>

+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>

+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,

+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>

+X-List-Received-Date: Wed, 09 Apr 2014 16:25:51 -0000

+

+-----BEGIN PGP SIGNED MESSAGE-----

+Hash: SHA512

+

+Two talking points for said developers yo their user re: "Why use a full node?":

+

+1) It's more private. Bloom filters gives away quite accurate statistical information about what coins you own to whom ever you happen to be connected too. An attacker can easily use this to deanonymize you even if you don't reuse addresses; Tor does not help much against this attack.

+

+2) It's more secure. SPV means you are trusting miners to do validation for you. With the extremely high degree of mining centralisation we currently have it would only take one or two pools getting hacked for an attacker to be able to get enough hashing power to easily fool your SPV wallet into accepting a fake transaction.

+

+

+As for what we can offer those developers, partial UTXO set mode would be a great long term goal.

+

+On 9 April 2014 11:29:32 GMT-04:00, 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.sourceforge.net/lists/listinfo/bitcoin-development

+-----BEGIN PGP SIGNATURE-----

+Version: APG v1.1.1

+

+iQFQBAEBCgA6BQJTRW88MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8

+cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhUIBB/4tVMqj7NEHFekUgv7O

+hKgUNreD5RQbVLjiG9BIKWTdOrD79qNk66QVxuH7oOCypMLCdT2ctdvsvfH8ncdG

+GVpTcbXL39vEk9qkGN4wY2++pKn5unqKg1C99YbJAcC62XMFJjjES2XiwyKGsYmb

+IplOEN7BXh9KE01f7gPh4nZqtqsb6XnlLQGjjRWGlX/oIMphUOdfMtBdWql59bx3

+wnHUDc1pAv2bCcyiUI/nOoyNyZixZC16wXoM2pnAJ9PhPbd79lmiKVmjNmrqhu17

+HIHlKXk6YD8JVlHD8NoaC1GUwG39jmt5nk1vsfvvesXF+c0VqctVNIitVkvqLNj+

+mwXd

+=4b5H

+-----END PGP SIGNATURE-----

+

+

+