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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
|
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 <voisine@gmail.com>) id 1Z4uHs-0001Zw-P6
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 17:04:36 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.174 as permitted sender)
client-ip=209.85.220.174; envelope-from=voisine@gmail.com;
helo=mail-qk0-f174.google.com;
Received: from mail-qk0-f174.google.com ([209.85.220.174])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4uHr-0005xn-NG
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 17:04:36 +0000
Received: by qkdm188 with SMTP id m188so12252597qkd.1
for <bitcoin-development@lists.sourceforge.net>;
Tue, 16 Jun 2015 10:04:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.25.40 with SMTP id k40mr3503790qkh.30.1434474270322; Tue,
16 Jun 2015 10:04:30 -0700 (PDT)
Received: by 10.140.91.37 with HTTP; Tue, 16 Jun 2015 10:04:30 -0700 (PDT)
In-Reply-To: <e471f72fdba349d0a6d66f1c8772f6e8@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>
<e471f72fdba349d0a6d66f1c8772f6e8@riseup.net>
Date: Tue, 16 Jun 2015 10:04:30 -0700
Message-ID: <CACq0ZD5y-yeiqqTu4sq0MZ2Ta=Xd_t0eOHg9PTfyg=XgVoF-Ag@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: "justusranvier@riseup.net" <justusranvier@riseup.net>
Content-Type: multipart/alternative; boundary=001a1147eb8c52752c0518a59134
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(voisine[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z4uHr-0005xn-NG
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 17:04:36 -0000
--001a1147eb8c52752c0518a59134
Content-Type: text/plain; charset=UTF-8
With their money, if they were to take advantage of optional additional
financial services, like, as one example, comsumer protection insurance.
Aaron
On Tuesday, June 16, 2015, <justusranvier@riseup.net> wrote:
> On 2015-06-16 07:55, 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.
>>
>
> How will the SPV wallet users pay for this service? With their money, or
> with their privacy?
>
--
Aaron Voisine
co-founder and CEO
breadwallet.com
--001a1147eb8c52752c0518a59134
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
With their money, if they were to take advantage of optional additional fin=
ancial services, like, as one example, comsumer protection insurance.<div><=
br></div><div>Aaron<span></span><br><br>On Tuesday, June 16, 2015, <<a =
href=3D"mailto:justusranvier@riseup.net">justusranvier@riseup.net</a>> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">On 2015-06-16 07:55, Aaron Voisine =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who<br>
would provide the nodes they would need connect to?<br>
</blockquote>
<br>
The SPV wallet author would if they wanted their wallet to function.<br>
</blockquote>
<br>
How will the SPV wallet users pay for this service? With their money, or wi=
th their privacy?<br>
</blockquote></div><br><br>-- <br><div dir=3D"ltr"><div><div dir=3D"ltr"><d=
iv><br>Aaron Voisine</div><div>co-founder and CEO<br><a href=3D"http://brea=
dwallet.com" target=3D"_blank">breadwallet.com</a></div></div></div></div><=
br>
--001a1147eb8c52752c0518a59134--
|
