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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WXuRW-0004ZO-To
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 15:29:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.180 as permitted sender)
client-ip=209.85.213.180; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f180.google.com;
Received: from mail-ig0-f180.google.com ([209.85.213.180])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXuRW-0004LU-8P
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 15:29:38 +0000
Received: by mail-ig0-f180.google.com with SMTP id c1so2558409igq.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Apr 2014 08:29:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.122.8 with SMTP id lo8mr5225277igb.31.1397057372896; Wed,
09 Apr 2014 08:29:32 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 9 Apr 2014 08:29:32 -0700 (PDT)
Date: Wed, 9 Apr 2014 17:29:32 +0200
Message-ID: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e015384fe718f5304f69dc419
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
(laanwj[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: 1WXuRW-0004LU-8P
Subject: [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:29:39 -0000
--089e015384fe718f5304f69dc419
Content-Type: text/plain; charset=UTF-8
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
--089e015384fe718f5304f69dc419
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>Hello,<br><br>This is primarily aimed at de=
velopers of SPV wallets.<br><br></div>The recently reported decrease in num=
ber 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 getti=
ng 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 op=
tion 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 ba=
ckground, the wallet could show statistics about the node, but is not depen=
dent 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 thi=
s sound like a good idea?<br></div><div><br></div>Is there any way that Bit=
coin Core can help to accomedate this 'embedded' usage? Specific In=
terfaces, special builds - maybe add a walletless bitcoind build to gitian =
- bindings, dlls, etc?<br>
<div><div><div><br>Wladimir<br><br></div></div></div></div>
--089e015384fe718f5304f69dc419--
|
