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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <brianchoffman@gmail.com>) id 1WYIGo-0006yn-Hd
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 16:56:10 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.173 as permitted sender)
client-ip=209.85.192.173; envelope-from=brianchoffman@gmail.com;
helo=mail-pd0-f173.google.com;
Received: from mail-pd0-f173.google.com ([209.85.192.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WYIGn-0003NT-FA
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 16:56:10 +0000
Received: by mail-pd0-f173.google.com with SMTP id z10so4110362pdj.4
for <bitcoin-development@lists.sourceforge.net>;
Thu, 10 Apr 2014 09:56:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.161.69 with SMTP id xq5mr20936475pab.62.1397148963562;
Thu, 10 Apr 2014 09:56:03 -0700 (PDT)
Received: by 10.70.89.237 with HTTP; Thu, 10 Apr 2014 09:56:03 -0700 (PDT)
In-Reply-To: <CALC81COfHg-xcwOPB2qGuF494KCwWNL3H7UrRB-uhL4wEdkOJQ@mail.gmail.com>
References: <CANEZrP04O7EqB=TqyTiC7O1K2A9R0nKJ_ssANHKg=Byum8-LtA@mail.gmail.com>
<CA+s+GJDbYjwhpsV15a+7kCO_vTstEewVrwvqbnB=a5zOSwFC6Q@mail.gmail.com>
<CAAS2fgStmEpiUV4Yh-qqu6sZ+VZ5SiQPwp+QA=3X5zR52ia3OA@mail.gmail.com>
<CA+s+GJBxEC2MifJQY5-vn2zSOHo-UOm8B1vYHHOfuxq26=VscQ@mail.gmail.com>
<CAADm4BDDJkS_xdjUn=2Yzs4B0RXTvpzpd5Z_kDRorzrn1HWSng@mail.gmail.com>
<CANEZrP1rPZYkTLmx5GOdj67oQAgFjeaF-LCKAXpg5XsEhXYFuQ@mail.gmail.com>
<CAADm4BB8y=k_f7CG3tyX6ruWF0w3+hU2Szv7ajLp1x7KhS56GA@mail.gmail.com>
<CALC81COfHg-xcwOPB2qGuF494KCwWNL3H7UrRB-uhL4wEdkOJQ@mail.gmail.com>
Date: Thu, 10 Apr 2014 12:56:03 -0400
Message-ID: <CAADm4BAZiRvjbwjPFQdP+FaHQ8ATi8UVbj=ZxYnNm7LuqTTn5Q@mail.gmail.com>
From: Brian Hoffman <brianchoffman@gmail.com>
To: Ricardo Filipe <ricardojdfilipe@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b6dd002abeca904f6b31706
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.173 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: 1WYIGn-0003NT-FA
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Chain pruning
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: Thu, 10 Apr 2014 16:56:10 -0000
--047d7b6dd002abeca904f6b31706
Content-Type: text/plain; charset=UTF-8
Okay...will let myself out now ;P
On Thu, Apr 10, 2014 at 12:54 PM, Ricardo Filipe
<ricardojdfilipe@gmail.com>wrote:
> that's what blockchain pruning is all about :)
>
> 2014-04-10 17:47 GMT+01:00 Brian Hoffman <brianchoffman@gmail.com>:
> > Looks like only about ~30% disk space savings so I see your point. Is
> there
> > a critical reason why blocks couldn't be formed into "superblocks" that
> are
> > chained together and nodes could serve a specific superblock, which
> could be
> > pieced together from different nodes to get the full blockchain? This
> would
> > allow participants with limited resources to serve full portions of the
> > blockchain rather than limited pieces of the entire blockchain.
> >
> >
> > On Thu, Apr 10, 2014 at 12:28 PM, Mike Hearn <mike@plan99.net> wrote:
> >>
> >> Suggestions always welcome!
> >>
> >> The main problem with this is that the block chain is mostly random
> bytes
> >> (hashes, keys) so it doesn't compress that well. It compresses a bit,
> but
> >> not enough to change the fundamental physics.
> >>
> >> However, that does not mean the entire chain has to be stored on
> expensive
> >> rotating platters. I've suggested that in some star trek future where
> the
> >> chain really is gigantic, it could be stored on tape and spooled off at
> high
> >> speed. Literally a direct DMA from tape drive to NIC. But we're not
> there
> >> yet :)
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> >
>
--047d7b6dd002abeca904f6b31706
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Okay...will let myself out now ;P</div><div class=3D"gmail=
_extra"><br><br><div class=3D"gmail_quote">On Thu, Apr 10, 2014 at 12:54 PM=
, Ricardo Filipe <span dir=3D"ltr"><<a href=3D"mailto:ricardojdfilipe@gm=
ail.com" target=3D"_blank">ricardojdfilipe@gmail.com</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">that's what blockchain pruning is all ab=
out :)<br>
<br>
2014-04-10 17:47 GMT+01:00 Brian Hoffman <<a href=3D"mailto:brianchoffma=
n@gmail.com">brianchoffman@gmail.com</a>>:<br>
> Looks like only about ~30% disk space savings so I see your point. Is =
there<br>
> a critical reason why blocks couldn't be formed into "superbl=
ocks" that are<br>
> chained together and nodes could serve a specific superblock, which co=
uld be<br>
> pieced together from different nodes to get the full blockchain? This =
would<br>
> allow participants with limited resources to serve full portions of th=
e<br>
> blockchain rather than limited pieces of the entire blockchain.<br>
><br>
><br>
> On Thu, Apr 10, 2014 at 12:28 PM, Mike Hearn <<a href=3D"mailto:mik=
e@plan99.net">mike@plan99.net</a>> wrote:<br>
>><br>
>> Suggestions always welcome!<br>
>><br>
>> The main problem with this is that the block chain is mostly rando=
m bytes<br>
>> (hashes, keys) so it doesn't compress that well. It compresses=
a bit, but<br>
>> not enough to change the fundamental physics.<br>
>><br>
>> However, that does not mean the entire chain has to be stored on e=
xpensive<br>
>> rotating platters. I've suggested that in some star trek futur=
e where the<br>
>> chain really is gigantic, it could be stored on tape and spooled o=
ff at high<br>
>> speed. Literally a direct DMA from tape drive to NIC. But we'r=
e not there<br>
>> yet :)<br>
><br>
><br>
><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-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
><br>
</blockquote></div><br></div>
--047d7b6dd002abeca904f6b31706--
|
