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
|
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 <brianchoffman@gmail.com>) id 1WXue6-0005Pw-DA
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 15:42:38 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.181 as permitted sender)
client-ip=209.85.192.181; envelope-from=brianchoffman@gmail.com;
helo=mail-pd0-f181.google.com;
Received: from mail-pd0-f181.google.com ([209.85.192.181])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXue5-0002c4-F4
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 15:42:38 +0000
Received: by mail-pd0-f181.google.com with SMTP id p10so2566477pdj.26
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Apr 2014 08:42:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.65.204 with SMTP id z12mr13094751pas.60.1397058151583;
Wed, 09 Apr 2014 08:42:31 -0700 (PDT)
Received: by 10.70.89.237 with HTTP; Wed, 9 Apr 2014 08:42:31 -0700 (PDT)
In-Reply-To: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
Date: Wed, 9 Apr 2014 11:42:31 -0400
Message-ID: <CAADm4BCEFCiOpNzUThPPHUamP2256izU8pwD3nerLCxks0wENA@mail.gmail.com>
From: Brian Hoffman <brianchoffman@gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=001a113625bcdb147c04f69df25c
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.181 listed in list.dnswl.org]
-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
(brianchoffman[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: 1WXue5-0002c4-F4
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:42:38 -0000
--001a113625bcdb147c04f69df25c
Content-Type: text/plain; charset=UTF-8
How would this affect the user in terms of disk storage? They're going to
get hammered on space constraints aren't they? If it's not required how
likely are users to enable this?
On Wed, Apr 9, 2014 at 11:29 AM, Wladimir <laanwj@gmail.com> wrote:
> 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
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> 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
>
>
--001a113625bcdb147c04f69df25c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">How would this affect the user in terms of disk storage? T=
hey're going to get hammered on space constraints aren't they? If i=
t's not required how likely are users to enable this?</div><div class=
=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Wed, Apr 9, 2014 at 11:29 AM, Wladimi=
r <span dir=3D"ltr"><<a href=3D"mailto:laanwj@gmail.com" target=3D"_blan=
k">laanwj@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<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?<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<div><div><div><br>Wladimir<br><br></div></div></div></font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
Put Bad Developers to Shame<br>
Dominate Development with Jenkins Continuous Integration<br>
Continuously Automate Build, Test & Deployment<br>
Start a new project now. Try Jenkins in the cloud.<br>
<a href=3D"http://p.sf.net/sfu/13600_Cloudbees" target=3D"_blank">http://p.=
sf.net/sfu/13600_Cloudbees</a><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=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--001a113625bcdb147c04f69df25c--
|
