summaryrefslogtreecommitdiff
path: root/6d/ad9871482cffc66ab71987e2b011bc1ff2c804
blob: 60883dc2eb0c11333da3c01392b9cccffcd51836 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <c1.sf-bitcoin@niftybox.net>) id 1Z4tTa-0002vI-MT
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 16:12:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of niftybox.net
	designates 95.142.167.147 as permitted sender)
	client-ip=95.142.167.147;
	envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to; 
Received: from i3.hyper.to ([95.142.167.147])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1Z4tTZ-0004Gc-BF
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 16:12:38 +0000
Received: from localhost (localhost [127.0.0.1])
	by i3.hyper.to (Postfix) with ESMTP id 826B5E01C4;
	Tue, 16 Jun 2015 17:52:50 +0200 (CEST)
Received: from i3.hyper.to ([127.0.0.1])
	by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10032)
	with ESMTP id yz13OqI0S1F3; Tue, 16 Jun 2015 17:52:49 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by i3.hyper.to (Postfix) with ESMTP id 8CC2BE01D2;
	Tue, 16 Jun 2015 17:52:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at i3.hyper.to
Received: from i3.hyper.to ([127.0.0.1])
	by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id LPiV3aIm_XCc; Tue, 16 Jun 2015 17:52:49 +0200 (CEST)
Received: from [192.168.4.81] (50-1-105-186.dsl.dynamic.fusionbroadband.com
	[50.1.105.186]) by i3.hyper.to (Postfix) with ESMTPSA id A1415E01C4;
	Tue, 16 Jun 2015 17:52:48 +0200 (CEST)
Message-ID: <5580464D.6020904@niftybox.net>
Date: Tue, 16 Jun 2015 08:52:45 -0700
From: devrandom <c1.sf-bitcoin@niftybox.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Aaron Voisine <voisine@gmail.com>, 
	Justus Ranvier <justusranvier@riseup.net>
References: <CALqxMTHrnSS9MGgKO-5+=fVhiOOvk12Recs11S0PcSUxQT1wdQ@mail.gmail.com>	<CA+c4Zoy6U9RXH3Qw15sXXnaeYL-9PFbnTp=VLAJsvpC_zoAK_A@mail.gmail.com>	<CAEY8wq41ftFA1ObyUWiRGOgebwqDCAw_j+hU6_wfcXv5GSZaJw@mail.gmail.com>	<201506160341.10994.luke@dashjr.org>	<CAEY8wq4SOddGUJNqkrdhhfQEn4tXehCWiifk-P=PYUdfFcXFTQ@mail.gmail.com>	<a9e2e033c786fb7f99bcf7505ad45f21@riseup.net>
	<CACq0ZD5uYikAfVuep8XCgEs-53NbF-SYhvm4qneZsEQdgd=6rw@mail.gmail.com>
In-Reply-To: <CACq0ZD5uYikAfVuep8XCgEs-53NbF-SYhvm4qneZsEQdgd=6rw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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: 1Z4tTZ-0004Gc-BF
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] The Bitcoin Node Market
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: Tue, 16 Jun 2015 16:12:38 -0000

On 2015-06-16 12:55 AM, Aaron Voisine wrote:
>> Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who
>> would provide the nodes they would need connect to? 
> 
> The SPV wallet author would if they wanted their wallet to function.

I would also guess that the cost to provide service to SPV wallets is
less than $0.01/mo per wallet and in any case less than long-term
transaction fees.  This can either be taken up by the wallet author or
transparently through a payment channel by the user.

> 
> 
> Aaron Voisine
> co-founder and CEO
> breadwallet.com <http://breadwallet.com>

-- 
devrandom / Miron