summaryrefslogtreecommitdiff
path: root/8c/55d6e7eb376a1e3ad68836de6c1dcc6127b2a5
blob: 84406482f52e862f96eb3baec6888371eca8ab7e (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
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
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
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 <tamas@bitsofproof.com>) 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 <tamas@bitsofproof.com>
In-Reply-To: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
Date: Wed, 9 Apr 2014 17:37:43 +0200
Message-Id: <05F8CE60-8058-4616-B3CD-511D6972D36C@bitsofproof.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
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 <bitcoin-development@lists.sourceforge.net>
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 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 <laanwj@gmail.com> 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

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>YES</div><div><br></div>Such a bitcoind is what =
I called border router in a previous mail.&nbsp;<br><div =
apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true">
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.</div><div =
apple-content-edited=3D"true">Therefore serious user of Bitcoin run a =
bitcoind as a border router and connect SPV wallets with higher =
functionality to that trusted node(s).</div><div =
apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true">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,</div><div =
apple-content-edited=3D"true">no Payment protocol and the =
rest.</div><div apple-content-edited=3D"true"><br style=3D"color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2;"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2; float: none; display: inline !important;">Regards,</span><br =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2;"><br style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; =
widows: 2; float: none; display: inline !important;">Tamas =
Blummer</span><br style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; =
widows: 2;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; =
widows: 2; float: none; display: inline !important;"><a =
href=3D"http://bitsofproof.com">http://bitsofproof.com</a></span>
</span></div>
<br><div><div>On 09.04.2014, at 17:29, Wladimir &lt;<a =
href=3D"mailto:laanwj@gmail.com">laanwj@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div><div><div>Hello,<br><br>This is =
primarily aimed at developers of SPV wallets.<br><br></div>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.<br>
<br>It's great to see innovation in wallets, but it's worrying that the =
number of full nodes decreases. <br><br>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).<br>
</div><div><br></div>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.<br>
<br>In exchange the user would get increased (full node level) security, =
as the SPV wallet would have a local trusted =
node.<br><br></div><div>Does this sound like a good =
idea?<br></div><div><br></div>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?<br>
<div><br>Wladimir<br><br></div></div>
=
--------------------------------------------------------------------------=
----<br>Put Bad Developers to Shame<br>Dominate Development with Jenkins =
Continuous Integration<br>Continuously Automate Build, Test &amp; =
Deployment <br>Start a new project now. Try Jenkins in the cloud.<br><a =
href=3D"http://p.sf.net/sfu/13600_Cloudbees_______________________________=
________________">http://p.sf.net/sfu/13600_Cloudbees_____________________=
__________________________</a><br>Bitcoin-development mailing =
list<br>Bitcoin-development@lists.sourceforge.net<br>https://lists.sourcef=
orge.net/lists/listinfo/bitcoin-development<br></blockquote></div><br></bo=
dy></html>=

--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--