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
|
Return-Path: <alex.mutovkin@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8F30DCC9
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 16 Aug 2017 17:37:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com
[209.85.128.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4CA52D0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 16 Aug 2017 17:37:36 +0000 (UTC)
Received: by mail-wr0-f182.google.com with SMTP id y96so19055374wrc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 16 Aug 2017 10:37:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=SgmOLihXQUzpa8zQdudPDj3ytcHNQWVdBgaaAhrzosQ=;
b=L/5yra7mT2NZhi1p1BeLqRVdjEjHbQMzmcTuzVLhef3hsuh6z/eY1Ht4s+5tTsVa18
EsAap+JmxhmkBicC9rY0W/pVDUQyS7oyKPAdivmb8Ml9rKI6P+b5GLXQTjM9v63l0NJg
Uby1SjJyyG1WTQljGzqYDJA8ZWRKJnQu0bW4GtyyjAUXedQRylPVj4iycc87WhtTJqDX
vs0FQ/1qzjxkMLvoWgtqGyzYiO9vnHIiPd1pAJ/GKDE2RhcsPqSJeSc3VB67/Qjea+Z+
vC92QVDysRRE4GC/TrTc0qGkdh/D7c2Xx4DEfQIM4Yw1ag4sAW8d8RwPC+Ta3KMylw6G
FtfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=SgmOLihXQUzpa8zQdudPDj3ytcHNQWVdBgaaAhrzosQ=;
b=b1MWo5fxva5IA4YvyDZpR/c8dFik977NAeHxfHESh/ySNyMzRQhiVsMjJHaHUjAk5Z
q6eb2xuYqtABniJjhGVhUpSx9x0ytBFVfLqYmEzXodLLtxDi97KVOaPNZOltgL/s1h4c
BbZwLOk/hpgzIdgl+H26jEkbfbKtglUGtkGLYA+sqyZCTtP+VIbrmBevZG0P++KDhvsF
4fS9EdDgLV/UCOG50LnSQtlKA0/YYXIIBAYGfLv3ceU8Ic8hFaGZcm2JKl6tawWcH/RS
drt4adWc/tf8W70H9cdRCdsagbBXeORQLBrCAFBpxIToSS86O4CfU83S4mar3jmPK3Bw
vV5Q==
X-Gm-Message-State: AHYfb5iP6o/Y9ck/k24zivpie3gsEhwLO83M5D6z80PWYC84FTTHPDkS
28X+Axjx6p54soRn/JJWVqfquRkB91eD1+o=
X-Received: by 10.223.197.201 with SMTP id v9mr631839wrg.87.1502905054825;
Wed, 16 Aug 2017 10:37:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.21.7 with HTTP; Wed, 16 Aug 2017 10:37:34 -0700 (PDT)
In-Reply-To: <CANN4kmdAehrmb3KvXsS7-gZgFTLcxHFyoMimwDi1_Aohmy+PDQ@mail.gmail.com>
References: <CAEadUTKo12vscHQUpjA16kQkrKBp34iw-JTRf0TdwUc9rqzznQ@mail.gmail.com>
<CAEadUT+oty3vU0LOMMoOdy7yNF92q+rgGbtV-AgjO8PGknZ+gg@mail.gmail.com>
<CANN4kmdAehrmb3KvXsS7-gZgFTLcxHFyoMimwDi1_Aohmy+PDQ@mail.gmail.com>
From: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0JzRg9GC0L7QstC60LjQvQ==?=
<alex.mutovkin@gmail.com>
Date: Wed, 16 Aug 2017 20:37:34 +0300
Message-ID: <CAEadUTL49V6GXgXAfYFw_E2AHPNemZVhgZZsvqueSOovs2yRMA@mail.gmail.com>
To: Nick ODell <nickodell@gmail.com>
Content-Type: multipart/alternative; boundary="089e08241fd4ec918d0556e259d1"
X-Mailman-Approved-At: Wed, 16 Aug 2017 17:41:49 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting
blockchain database to reduce its size.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 17:37:36 -0000
--089e08241fd4ec918d0556e259d1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I read about prune option right now, actually i didn't hear about it before=
.
Yes this option can save some disk space but afaik first (awful N-days
lasting) synchronization still requires to download full database.
My approach also cuts database and replaces all old blocks (except say last
6 blocks for security reason)
with series of blocks with rolled initial totals and optionally purged from
tiny wallets crap (storing on six thousand current nodes and on the swarm
of full wallets
information that John have 100 satosi is too expensive for us and we may
annually clear that balance as fee for miners or just delete).
So almost all nodes can hold only the rolled database (i can't estimate
compression ration of the rolled database now, i am not advanced user as
you can see).
And only much less amount of archive nodes holds full expanded database.
2017-08-16 19:52 GMT+03:00 Nick ODell <nickodell@gmail.com>:
> What makes this approach better than the prune option of Bitcoin?
>
> On Wed, Aug 16, 2017 at 10:20 AM, =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=
=B9 =D0=9C=D1=83=D1=82=D0=BE=D0=B2=D0=BA=D0=B8=D0=BD via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>>
>> Let me describe the possible improvement of the bitcoin blockchain
>> database (BBD) size in general terms.
>>
>> We can implement new routine : annual split of the BBD. Reason is that
>> 140gb full wallet unconvinience.
>>
>> BBD splits in two parts :
>> 1) old blocks before the date of split and
>> 2) new blocks, starting from first technical block with all rolled total=
s
>> on the date of split.
>> (also possible transfer of tiny totals due to their unprofitability
>> to the miners, so we cut long tail of tiny holders)
>> 3) old blocks packs into annual megablocks and stores in the side archiv=
e
>> chain for some needs for FBI investigations or other goals.
>>
>>
>> Thanks for your attention,
>>
>> Alexey Mutovkin
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>
--089e08241fd4ec918d0556e259d1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>I read about prune option right now, actual=
ly i didn't hear about it before.<br></div>Yes this option can save som=
e disk space but afaik first (awful N-days lasting) synchronization still r=
equires to download full database. <br></div>My approach also cuts database=
and replaces all old blocks (except say last 6 blocks for security reason)=
<br>with series of blocks with rolled initial totals and optionally purged=
from tiny wallets crap (storing on six thousand current nodes and on the s=
warm of full wallets <br></div><div>=C2=A0information that John have 100 sa=
tosi is too expensive for us and we may annually clear that balance as fee =
for miners or just delete).</div><div><br></div>So almost all nodes can hol=
d only the rolled database (i can't estimate compression ration of the =
rolled database now, i am not advanced user as you can see).<br>=C2=A0And o=
nly much less amount of archive nodes holds full expanded database.<br><br>=
<br><br><br><br><br><br><div><br><br>=C2=A0 <br><div><br></div></div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-08-16 19:52 =
GMT+03:00 Nick ODell <span dir=3D"ltr"><<a href=3D"mailto:nickodell@gmai=
l.com" target=3D"_blank">nickodell@gmail.com</a>></span>:<br><blockquote=
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr">What makes this approach better than t=
he prune option of Bitcoin?</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote"><div><div class=3D"h5">On Wed, Aug 16, 2017 at 10:20 AM, =
=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9 =D0=9C=D1=83=D1=82=D0=BE=D0=B2=
=D0=BA=D0=B8=D0=BD via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:=
bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a>></span> wrote:<br></div></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div><div class=3D"h5"><div dir=3D"ltr"><div class=3D"gma=
il_quote"><br><div dir=3D"ltr"><div><div><div><div><div>Let me describe the=
possible improvement of the bitcoin blockchain database (BBD)=C2=A0 size i=
n general terms.<br><br></div>We can implement new routine : annual split o=
f the BBD. Reason is that 140gb full wallet unconvinience.<br><br></div>BBD=
splits in two parts : <br>1) old blocks before the date of split and <br>2=
) new blocks, starting from first technical block with all rolled totals on=
the date of split. <br>=C2=A0=C2=A0=C2=A0 (also possible transfer of tiny =
totals due to their unprofitability to the miners, so we cut long tail of t=
iny holders)<br></div>3) old blocks packs into annual megablocks and stores=
in the side archive chain for some needs for FBI investigations or other g=
oals.<br></div><div></div><div></div><div><br></div><div><br></div>Thanks f=
or your attention,<br><br></div>Alexey Mutovkin<br><div><div><div><br><br><=
div><br><br><br><br><div><br><br><br><br><br></div></div></div></div></div>=
</div>
</div><br></div>
<br></div></div>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
--089e08241fd4ec918d0556e259d1--
|
