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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kevinsisco61784@gmail.com>) id 1WXxLc-0006B7-Pp
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 18:35:44 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.49 as permitted sender)
client-ip=209.85.192.49; envelope-from=kevinsisco61784@gmail.com;
helo=mail-qg0-f49.google.com;
Received: from mail-qg0-f49.google.com ([209.85.192.49])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXxLb-0000Xr-Jf
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 18:35:44 +0000
Received: by mail-qg0-f49.google.com with SMTP id j107so596667qga.8
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Apr 2014 11:35:38 -0700 (PDT)
X-Received: by 10.140.34.46 with SMTP id k43mr14040069qgk.63.1397068538126;
Wed, 09 Apr 2014 11:35:38 -0700 (PDT)
Received: from [192.168.1.115] (ool-457b2cb7.dyn.optonline.net.
[69.123.44.183])
by mx.google.com with ESMTPSA id u59sm2017371qga.8.2014.04.09.11.35.36
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 09 Apr 2014 11:35:36 -0700 (PDT)
Message-ID: <534592F5.2000407@gmail.com>
Date: Wed, 09 Apr 2014 14:35:33 -0400
From: Kevin <kevinsisco61784@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
In-Reply-To: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------030901030209010306070109"
X-Spam-Score: -0.3 (/)
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.49 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
(kevinsisco61784[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (kevinsisco61784[at]gmail.com)
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: 1WXxLb-0000Xr-Jf
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 18:35:45 -0000
This is a multi-part message in MIME format.
--------------030901030209010306070109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 4/9/2014 11:29 AM, Wladimir 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
I personally like the ida. Are you talking about a flag that could
toggle this "in the background" mode or recoding for in the background use?
--
Kevin
--------------030901030209010306070109
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 4/9/2014 11:29 AM, Wladimir wrote:<br>
</div>
<blockquote
cite="mid:CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com"
type="cite">
<div dir="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>
<div>
<div><br>
Wladimir<br>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
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.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/13600_Cloudbees">http://p.sf.net/sfu/13600_Cloudbees</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bitcoin-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
</blockquote>
I personally like the ida. Are you talking about a flag that could
toggle this "in the background" mode or recoding for in the
background use?<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Kevin
</pre>
</body>
</html>
--------------030901030209010306070109--
|
