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
|
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 <mh.in.england@gmail.com>) id 1WXDWy-0001og-HN
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 17:40:24 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.176 as permitted sender)
client-ip=209.85.214.176; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f176.google.com;
Received: from mail-ob0-f176.google.com ([209.85.214.176])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXDWw-0001J2-Re
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 17:40:24 +0000
Received: by mail-ob0-f176.google.com with SMTP id wp18so6861000obc.21
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 10:40:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.176.9 with SMTP id ce9mr3266204oec.55.1396892417490; Mon,
07 Apr 2014 10:40:17 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Mon, 7 Apr 2014 10:40:17 -0700 (PDT)
In-Reply-To: <CACvcBVq2+37jWgxBg2Zjj6KFtT1ZnZzTa7FOw1sLwimeT0ahhA@mail.gmail.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<5342C833.5030906@gmail.com>
<CAAS2fgTqBfEPXh2dfcL_ke6c0wfXw4qUM1rAYMkAHcAM6mYH+g@mail.gmail.com>
<5342D1DB.8060203@monetize.io>
<CAAS2fgRu-0C_ozaN0qSc9SvF2TpZ56NwceLCrfQjikuQgc85tQ@mail.gmail.com>
<5342D9FA.8080102@monetize.io>
<CAAS2fgT5xfYzup01+USkFmFWi=FtDfbPY1HPpTLyQ+6_ejGOZA@mail.gmail.com>
<CACvcBVq2+37jWgxBg2Zjj6KFtT1ZnZzTa7FOw1sLwimeT0ahhA@mail.gmail.com>
Date: Mon, 7 Apr 2014 19:40:17 +0200
X-Google-Sender-Auth: w-V7tpBGmfQRFIJaxTa7bvqaKB0
Message-ID: <CANEZrP3_v2zAqMkcTtQ1Mys2rUEcsd_MpLySefpgJ-P7OSg34g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Brent Shambaugh <brent.shambaugh@gmail.com>
Content-Type: multipart/alternative; boundary=089e0118226c5585b104f6775cc7
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WXDWw-0001J2-Re
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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: Mon, 07 Apr 2014 17:40:24 -0000
--089e0118226c5585b104f6775cc7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
It uses ~no electricity, it's not like mining.
The primary resources it needs are disk space and bandwidth, after an
intensive initial day or two of building the database.
Actually, I wonder if we should start shipping (auditable) pre-baked
databases calculated up to the last checkpoint so people can download them
and boot up their node right away. Recalculating the entire thing from
scratch every time isn't sustainable in the long run anyway.
On Mon, Apr 7, 2014 at 7:35 PM, Brent Shambaugh
<brent.shambaugh@gmail.com>wrote:
> How difficult would it be to set up a node? Using lots of electricity at
> home (if required) could be an issue, but I do have a Webfaction account.
>
>
> On Mon, Apr 7, 2014 at 12:16 PM, Gregory Maxwell <gmaxwell@gmail.com>wrot=
e:
>
>> On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach <mark@monetize.io>
>> wrote:
>> > On 04/07/2014 09:57 AM, Gregory Maxwell wrote:
>> >> That is an implementation issue=E2=80=94 mostly one that arises as an=
indirect
>> >> consequence of not having headers first and the parallel fetch, not a
>> >> requirements issue.
>> >
>> > Oh, absolutely. But the question "why are people not running full
>> > nodes?" has to do with the current implementation, not abstract
>> > capabilities of a future version of the bitcoind code base.
>>
>> The distinction is very important because it's a matter of things we
>> can and should fix vs things that cannot be fixed except by changing
>> goals/incentives! Opposite approaches to handling them.
>>
>> When I read "resource requirements of a full node are moving beyond" I
>> didn't extract from that that "there are implementation issues that
>> need to be improved to make it work better for low resource users" due
>> to the word "requirements".
>>
>>
>> ------------------------------------------------------------------------=
------
>> 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
>>
>
>
>
> -------------------------------------------------------------------------=
-----
> 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
>
>
--089e0118226c5585b104f6775cc7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">It uses ~no electricity, it's not like mining.<div><br=
></div><div>The primary resources it needs are disk space and bandwidth, af=
ter an intensive initial day or two of building the database.</div><div><br=
>
</div><div>Actually, I wonder if we should start shipping (auditable) pre-b=
aked databases calculated up to the last checkpoint so people can download =
them and boot up their node right away. Recalculating the entire thing from=
scratch every time isn't sustainable in the long run anyway.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
Apr 7, 2014 at 7:35 PM, Brent Shambaugh <span dir=3D"ltr"><<a href=3D"m=
ailto:brent.shambaugh@gmail.com" target=3D"_blank">brent.shambaugh@gmail.co=
m</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">How difficult would it be t=
o set up a node? Using lots of electricity at home (if required) could be a=
n issue, but I do have a Webfaction account. <br>
</div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">
On Mon, Apr 7, 2014 at 12:16 PM, Gregory Maxwell <span dir=3D"ltr"><<a h=
ref=3D"mailto:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</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">
<div>On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach <<a href=3D"mailt=
o:mark@monetize.io" target=3D"_blank">mark@monetize.io</a>> wrote:<br>
> On 04/07/2014 09:57 AM, Gregory Maxwell wrote:<br>
>> That is an implementation issue=E2=80=94 mostly one that arises as=
an indirect<br>
>> consequence of not having headers first and the parallel fetch, no=
t a<br>
>> requirements issue.<br>
><br>
> Oh, absolutely. But the question "why are people not running full=
<br>
> nodes?" has to do with the current implementation, not abstract<b=
r>
> capabilities of a future version of the bitcoind code base.<br>
<br>
</div>The distinction is very important because it's a matter of things=
we<br>
can and should fix vs things that cannot be fixed except by changing<br>
goals/incentives! =C2=A0Opposite approaches to handling them.<br>
<br>
When I read "resource requirements of a full node are moving beyond&qu=
ot; I<br>
didn't extract from that that "there are implementation issues tha=
t<br>
need to be improved to make it work better for low resource users" due=
<br>
to the word "requirements".<br>
<div><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" target=3D"_bla=
nk">Bitcoin-development@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>
</div></div></blockquote></div><br></div>
</div></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>
--089e0118226c5585b104f6775cc7--
|
