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
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <voisine@gmail.com>) id 1Z4iEX-0002CC-BS
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 04:12:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.169 as permitted sender)
client-ip=209.85.220.169; envelope-from=voisine@gmail.com;
helo=mail-qk0-f169.google.com;
Received: from mail-qk0-f169.google.com ([209.85.220.169])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4iEW-00060v-83
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 04:12:21 +0000
Received: by qkfe185 with SMTP id e185so2863889qkf.3
for <bitcoin-development@lists.sourceforge.net>;
Mon, 15 Jun 2015 21:12:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.140.238.22 with SMTP id j22mr41857497qhc.98.1434427934859;
Mon, 15 Jun 2015 21:12:14 -0700 (PDT)
Received: by 10.140.91.37 with HTTP; Mon, 15 Jun 2015 21:12:14 -0700 (PDT)
In-Reply-To: <CAEY8wq4SOddGUJNqkrdhhfQEn4tXehCWiifk-P=PYUdfFcXFTQ@mail.gmail.com>
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>
Date: Mon, 15 Jun 2015 21:12:14 -0700
Message-ID: <CACq0ZD69egjyaBBUeuvVX9LZUkX7hT7xokHn=SumppRbzA1kUQ@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: Kevin Greene <kgreenek@gmail.com>
Content-Type: multipart/alternative; boundary=001a113594ee8366fb05189ac7f6
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: 1Z4iEW-00060v-83
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 04:12:21 -0000
--001a113594ee8366fb05189ac7f6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
We're planning to run our own full nodes to take load off the volunteer
network as breadwallet use increases, and also contribute any SPV serving
performance optimizations we can make to bitcoin-core. Just want to let
people know we share these concerns and have plans to mitigate any negative
impact on the network.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Jun 15, 2015 at 8:49 PM, Kevin Greene <kgreenek@gmail.com> wrote:
>
>
> On Mon, Jun 15, 2015 at 8:41 PM, Luke Dashjr <luke@dashjr.org> wrote:
>
>> On Tuesday, June 16, 2015 3:30:44 AM Kevin Greene wrote:
>> > Would SPV wallets have to pay to connect to the network too? From the
>> > user's perspective, it would be somewhat upsetting (and confusing) to
>> see
>> > your balance slowly draining every time you open your wallet app. It
>> would
>> > also tie up outputs every time you open up your wallet. You may go to
>> pay
>> > for something in a coffee shop, only to find that you can't spend your
>> > bitcoin because the wallet had to create a transaction to pay to sync
>> with
>> > the network.
>> >
>> > Also, users of centralized wallet services like Coinbase would not hav=
e
>> to
>> > pay that fee; but users of native wallets like breadwallet would have =
no
>> > such option. This incentivizes users to use centralized wallets.
>> >
>> > So this is kind of imposing a worse user experience on users who want =
to
>> > use bitcoin the "right" way. That doesn't seem like a good thing to me
>> :/
>>
>> SPV isn't the "right" way either ;)
>>
>
> =E2=80=8BHah, fair enough, there is no such thing as the "right" way to d=
o
> anything. But I still think punishing users who use SPV wallets is =E2=80=
=8Ba
> less-than-ideal way to incentive people to run full nodes. Right now SPV =
is
> the best way that exists for mobile phones to participate in the network =
in
> a decentralized way. This proposal makes the user experience for mobile
> wallets a little more confusing and annoying.
>
>
>>
>> If you're running a full node (the real "right way"), you should be able
>> to
>> earn more bitcoins than you pay out.
>>
>> Luke
>>
>
>
>
> -------------------------------------------------------------------------=
-----
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a113594ee8366fb05189ac7f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">We're planning to run our own full nodes to take load =
off the volunteer network as breadwallet use increases, and also contribute=
any SPV serving performance optimizations we can make to bitcoin-core. Jus=
t want to let people know we share these concerns and have plans to mitigat=
e any negative impact on the network.</div><div class=3D"gmail_extra"><br c=
lear=3D"all"><div><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div=
dir=3D"ltr"><div><br>Aaron Voisine</div><div>co-founder and CEO<br><a href=
=3D"http://breadwallet.com" target=3D"_blank">breadwallet.com</a></div></di=
v></div></div></div></div>
<br><div class=3D"gmail_quote">On Mon, Jun 15, 2015 at 8:49 PM, Kevin Green=
e <span dir=3D"ltr"><<a href=3D"mailto:kgreenek@gmail.com" target=3D"_bl=
ank">kgreenek@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"color:#336666">=
<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span c=
lass=3D"">On Mon, Jun 15, 2015 at 8:41 PM, Luke Dashjr <span dir=3D"ltr">&l=
t;<a href=3D"mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tuesday, June =
16, 2015 3:30:44 AM Kevin Greene wrote:<br>
> Would SPV wallets have to pay to connect to the network too? From the<=
br>
> user's perspective, it would be somewhat upsetting (and confusing)=
to see<br>
> your balance slowly draining every time you open your wallet app. It w=
ould<br>
> also tie up outputs every time you open up your wallet. You may go to =
pay<br>
> for something in a coffee shop, only to find that you can't spend =
your<br>
> bitcoin because the wallet had to create a transaction to pay to sync =
with<br>
> the network.<br>
><br>
> Also, users of centralized wallet services like Coinbase would not hav=
e to<br>
> pay that fee; but users of native wallets like breadwallet would have =
no<br>
> such option. This incentivizes users to use centralized wallets.<br>
><br>
> So this is kind of imposing a worse user experience on users who want =
to<br>
> use bitcoin the "right" way. That doesn't seem like a go=
od thing to me :/<br>
<br>
</span>SPV isn't the "right" way either ;)<br></blockquote><d=
iv><br></div></span><div><div class=3D"gmail_default" style=3D"color:rgb(51=
,102,102)">=E2=80=8BHah, fair enough, there is no such thing as the "r=
ight" way to do anything. But I still think punishing users who use SP=
V wallets is =E2=80=8Ba less-than-ideal way to incentive people to run full=
nodes. Right now SPV is the best way that exists for mobile phones to part=
icipate in the network in a decentralized way. This proposal makes the user=
experience for mobile wallets a little more confusing and annoying.</div><=
/div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If you're running a full node (the real "right way"), you sho=
uld be able to<br>
earn more bitcoins than you pay out.<br>
<span><font color=3D"#888888"><br>
Luke<br>
</font></span></blockquote></span></div><br></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
<br></blockquote></div><br></div>
--001a113594ee8366fb05189ac7f6--
|
