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
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
|
Return-Path: <cryptaxe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E69E0FE1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Sep 2018 00:02:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com
[209.85.128.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B36472C3
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Sep 2018 00:02:54 +0000 (UTC)
Received: by mail-wm1-f50.google.com with SMTP id r1-v6so13826347wmh.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 25 Sep 2018 17:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=y4ixCiMNVT0SYLsVdJ86yRBe+AvBStYdY34xUTR7mU4=;
b=p4dn6Bibcz/tmF6Vhsnork+k/j5KTWb3GJanZq9vaipZCB33952+gs5/68PjOOvQzU
WVarCrsW2oPefOxfsckcyOaPXACZWrnMLvIDtWbLVotYcwr5fcEMw68//v7AmS7qRZzK
yw8vNu/F6KnnEXInAWj925UrK4itkIEiA4TZOo/eGWE9wtFOF64vkdLjI+7tqvvmi46x
YvzfKTyF/HRN7rbImeRxuSkILOOy0lH3fVL3fdshQ+simq1n1J9SMcKDbue1eeBGEOas
X3P7+a0da7OMhrGoGDXWw5DHARYeLjv2Gzg4DUKM/zgVMDN0Nt+Acyjt5Tou6toKI92A
rbbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=y4ixCiMNVT0SYLsVdJ86yRBe+AvBStYdY34xUTR7mU4=;
b=RxTT43Zs4wqCxGeF/0pqwYXc5l/TaZVzX+qoegWos15OOyI5Y854y8GJzk0OomZriW
V3uEx/u0MZUp7AzSEzb9JBLlmJc1i5CCAMieIWMnZziZpQntAlfQnSAZQJCZOpvwICdi
qbENYd8G0feTQ5swakiLxIzVYF3oqjM3bzCWL85mEcT3ut9Zk0t0/WBxOiOX+gDxop5X
rAHES0EJkB3DNykB/uOQtKACnt5BsRBC/AwSgGLKRm8eJZNsnR31gXg56KNIF2tHKHTX
2KPucBi68oeUteM65+LrpTKXB3l4Tp3hZAS57xNeKT1tCaDxRKJmS5n5IwBFlyXWGBlV
QbjQ==
X-Gm-Message-State: ABuFfojZFSROv1D7AuHmYN694Ryw/E/Tke+DlfqUwM1+RzUsd5MfVEmA
9Epi0/qAXIZlSuacoTCIEXDaUcdqdkF4MExvc5c=
X-Google-Smtp-Source: ACcGV63/Q1QAW8wqtF0oKE79XywX3ydJOAf54+bTOglBKk7TIPz7iJKWPWeWlV9VxIz9DDbHdMZpXqaTNCC4UMsbxkI=
X-Received: by 2002:a1c:a386:: with SMTP id
m128-v6mr2300673wme.139.1537920173169;
Tue, 25 Sep 2018 17:02:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAGLBAheT0DB4Aid01vqdkwGJ6U=Fn8A4TU+XKrC=PygdXyvJjg@mail.gmail.com>
<CAGLBAhcvf6o0J4us3=d0LMmcO_AyZZZtVbsaST9Scth6yX+eSQ@mail.gmail.com>
<PS2P216MB01795F6E52A18C73E20E9D5A9D160@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
In-Reply-To: <PS2P216MB01795F6E52A18C73E20E9D5A9D160@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
From: CryptAxe <cryptaxe@gmail.com>
Date: Tue, 25 Sep 2018 17:00:03 -0700
Message-ID: <CAF5CFkhY0rYP6yb66jr0MyKBOuTXuQ+Kasz0kJ_NM985YR-wPA@mail.gmail.com>
To: willtech@live.com.au,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000009d61520576baf1ec"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 26 Sep 2018 01:06:42 +0000
Subject: Re: [bitcoin-dev] [bitcoin-discuss] Proposal to replace full
blockchain with recent history plus UTXO Set
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, 26 Sep 2018 00:02:56 -0000
--0000000000009d61520576baf1ec
Content-Type: text/plain; charset="UTF-8"
Feel free to take a look at my implementation of UTXO loading (for core
~0.16.99) here:
https://github.com/DriveNetTESTDRIVE/DriveNet/commit/60189ea9a23865180e25207ecf66f95d84f642c6
Note that this has consensus implications, and that there are bugs (some of
which are fixed in later commits to that repository)
On Tue, Sep 25, 2018 at 4:56 PM Damian Williamson via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> A fairly decent rework would be needed but it seems that the idea has
> merit initially.
>
>
> As it is now, it is not only that a utxo exists but, that the transaction
> it references and the block it is within can also be fully validated.
>
>
> So, if a utxo block set type existed then by consensus every so often a
> bunch of blocks containing just the validated utxo set to a given height,
> say 100,000 blocks below the current blockheight, and necessary header data
> could be appended onto the valid chain and nodes would be free to drop all
> preceding blocks. I suspect that many wouldn't and that even many new nodes
> would still desire to download the full blockchain but, for the use case
> you mention it would make sense.
>
>
> If done [right/wrong] it may even make Satoshi's fortune spendable.
> Something to watch out for.
> ------------------------------
> *From:* bitcoin-discuss-bounces@lists.linuxfoundation.org <
> bitcoin-discuss-bounces@lists.linuxfoundation.org> on behalf of Dave
> Scotese via bitcoin-discuss <bitcoin-discuss@lists.linuxfoundation.org>
> *Sent:* Wednesday, 26 September 2018 1:46:54 AM
> *To:* Bitcoin Discuss
> *Subject:* Re: [bitcoin-discuss] Proposal to replace full blockchain with
> recent history plus UTXO Set
>
> The image at imgur and the pastebin both reference block 542324 but the
> correct block is 542322. As the pastebin shows, the decimal and hex
> representations I gave for the block height did not match, and this is
> why. If you use the Merkle root for block 542322 instead of 542324, you'll
> be able to see the correct Game of Life play out and make the apron image.
>
> Dave.
>
> On Sun, Sep 23, 2018 at 11:38 AM Dave Scotese <dscotese@litmocracy.com>
> wrote:
>
> I thought I didn't have access to the dev list and so intended to post the
> following proposal to this discussion list, but used the wrong email
> address. Anyway, my email did get into the dev list (
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-September/016420.html)
> but I'll repeat it here:
>
> I've been working on an idea that relieves full nodes of storing the
> entire blockchain. Open source software generally relies on the fact that
> "enough" people agree that it's secure. Bitcoin software works that way
> too. So if you understand enough to see that a UTXO set is valid at a
> certain block height, and there are enough other people who agree and that
> set is recognizable by humans, then we can use that UTXO set and ditch the
> blockchain that existed up to that point. It would save a lot of storage
> and make it a lot easier to run a full node.
>
> Have you reviewed the source code from which your wallets were compiled?
> At some point, we all trust third parties, but generally (at least among
> people who understand Bitcoin) they are large composite groups so that no
> small group or individual can profit from cheating.
>
> I look forward to answering any concerns and also to any offers of help.
> I used block 542324 of the Bitcoin blockchain to make a memorable
> experience using the game of life. I wrote a script for the open-source
> Game-of-Life software Golly and shared it in the paste at
> https://pastebin.com/k5Ssc0qk. It produces the image at
> https://imgur.com/a/rwIQuVz. If someone can tell me how to get a UTXO Set
> from the bitcoin client, I'll send them $50 of bitcoin. Then I could get
> the SHA256 hash of that set and try to make a recognizable checkpoint for
> the Bitcoin blockchain. If someone runs Golly and shares a video of the
> game playing out (into the apron-shaped image), I'll send them $50 of
> bitcoin too.
>
> In a few decades when the blockchain has grown to a few terabytes and the
> UTXO Set is still just a few gigabytes, I'd like to see more people start
> running full nodes without the hassle of a long wait and loads of storage
> space. That's what stops me from running one.
>
>
>
> --
> I like to provide some work at no charge to prove my value. Do you need a
> techie?
> I own Litmocracy <http://www.litmocracy.com> and Meme Racing
> <http://www.memeracing.net> (in alpha).
> I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com>
> which now accepts Bitcoin.
> I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
> "He ought to find it more profitable to play by the rules" - Satoshi
> Nakamoto
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--0000000000009d61520576baf1ec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div>Feel free to take a look at my imple=
mentation of UTXO loading (for core ~0.16.99) here:</div><div><a href=3D"ht=
tps://github.com/DriveNetTESTDRIVE/DriveNet/commit/60189ea9a23865180e25207e=
cf66f95d84f642c6">https://github.com/DriveNetTESTDRIVE/DriveNet/commit/6018=
9ea9a23865180e25207ecf66f95d84f642c6</a></div><div><br></div><div><br></div=
><div>Note that this has consensus implications, and that there are bugs (s=
ome of which are fixed in later commits to that repository)</div><div><br><=
/div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Se=
p 25, 2018 at 4:56 PM Damian Williamson via bitcoin-dev <<a href=3D"mail=
to:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation=
.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">
<div id=3D"m_-619780837676204327divtagdefaultwrapper" style=3D"font-size:12=
pt;color:#000000;font-family:Calibri,Helvetica,sans-serif" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">A fairly decent rework would be n=
eeded but it seems that the idea has merit initially.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">As it is now, it is not only that=
a utxo exists but, that the transaction it references and the block it is =
within can also be fully validated.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">So, if a utxo block set type exis=
ted then by consensus every so often a bunch of blocks containing just the =
validated utxo set to a given height, say 100,000 blocks below the current =
blockheight, and necessary header
data could be appended onto the valid chain and nodes would be free to dro=
p all preceding blocks. I suspect that many wouldn't and that even many=
new nodes would still desire to download the full blockchain but, for the =
use case you mention it would make sense.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">If done [right/wrong] it may even=
make Satoshi's fortune spendable. Something to watch out for.<br>
</p>
</div>
<hr style=3D"display:inline-block;width:98%">
<div id=3D"m_-619780837676204327divRplyFwdMsg" dir=3D"ltr"><font face=3D"Ca=
libri, sans-serif" style=3D"font-size:11pt" color=3D"#000000"><b>From:</b> =
<a href=3D"mailto:bitcoin-discuss-bounces@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-discuss-bounces@lists.linuxfoundation.org</a> <<a hr=
ef=3D"mailto:bitcoin-discuss-bounces@lists.linuxfoundation.org" target=3D"_=
blank">bitcoin-discuss-bounces@lists.linuxfoundation.org</a>> on behalf =
of Dave Scotese via bitcoin-discuss
<<a href=3D"mailto:bitcoin-discuss@lists.linuxfoundation.org" target=3D=
"_blank">bitcoin-discuss@lists.linuxfoundation.org</a>><br>
<b>Sent:</b> Wednesday, 26 September 2018 1:46:54 AM<br>
<b>To:</b> Bitcoin Discuss<br>
<b>Subject:</b> Re: [bitcoin-discuss] Proposal to replace full blockchain w=
ith recent history plus UTXO Set</font>
<div>=C2=A0</div>
</div>
<div>
<div dir=3D"ltr">
<div>The image at imgur and the pastebin both reference block 542324 but th=
e correct block is 542322.=C2=A0 As the pastebin shows, the decimal and hex=
representations I gave for the block height did not match, and this is why=
.=C2=A0 If you use the Merkle root for block
542322 instead of 542324, you'll be able to see the correct Game of Li=
fe play out and make the apron image.<br>
</div>
<div><br>
</div>
<div>Dave.<br>
</div>
</div>
<br>
<div class=3D"m_-619780837676204327x_gmail_quote">
<div dir=3D"ltr">On Sun, Sep 23, 2018 at 11:38 AM Dave Scotese <<a href=
=3D"mailto:dscotese@litmocracy.com" target=3D"_blank">dscotese@litmocracy.c=
om</a>> wrote:<br>
</div>
<blockquote class=3D"m_-619780837676204327x_gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">
<div dir=3D"ltr">
<div dir=3D"ltr">I thought I didn't have access to the dev list and so =
intended to post the following proposal to this discussion list, but used t=
he wrong email address.=C2=A0 Anyway, my email did get into the dev list (<=
a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-Sept=
ember/016420.html" target=3D"_blank">https://lists.linuxfoundation.org/pipe=
rmail/bitcoin-dev/2018-September/016420.html</a>)
but I'll repeat it here:</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">I've been working on an idea that relieves full nodes =
of storing the entire blockchain. Open source software generally relies on =
the fact that "enough" people agree that it's secure. Bitcoin=
software works that way too. So if you understand enough
to see that a UTXO set is valid at a certain block height, and there are e=
nough other people who agree and that set is recognizable by humans, then w=
e can use that UTXO set and ditch the blockchain that existed up to that po=
int. It would save a lot of storage
and make it a lot easier to run a full node.<br>
<br>
Have you reviewed the source code from which your wallets were compiled? At=
some point, we all trust third parties, but generally (at least among peop=
le who understand Bitcoin) they are large composite groups so that no small=
group or individual can profit
from cheating.<br>
<br>
I look forward to answering any concerns and also to any offers of help.=C2=
=A0=C2=A0 I used block 542324 of the Bitcoin blockchain to make a memorable=
experience using the game of life. I wrote a script for the open-source Ga=
me-of-Life software Golly and shared it in
the paste at <a href=3D"https://pastebin.com/k5Ssc0qk" target=3D"_blank">h=
ttps://pastebin.com/k5Ssc0qk</a>. It produces the image at
<a href=3D"https://imgur.com/a/rwIQuVz" target=3D"_blank">https://imgur.com=
/a/rwIQuVz</a>. If someone can tell me how to get a UTXO Set from the bitco=
in client, I'll send them $50 of bitcoin. Then I could get the SHA256 h=
ash of that set and try to make a recognizable
checkpoint for the Bitcoin blockchain. If someone runs Golly and shares a =
video of the game playing out (into the apron-shaped image), I'll send =
them $50 of bitcoin too.<br>
<br>
In a few decades when the blockchain has grown to a few terabytes and the U=
TXO Set is still just a few gigabytes, I'd like to see more people star=
t running full nodes without the hassle of a long wait and loads of storage=
space. That's what stops me from running
one.<br>
</div>
</div>
</div>
</blockquote>
</div>
<br clear=3D"all">
<br>
-- <br>
<div dir=3D"ltr" class=3D"m_-619780837676204327x_gmail_signature">
<div dir=3D"ltr">I like to provide some work at no charge to prove my value=
. Do you need a techie?=C2=A0
<br>
I own <a href=3D"http://www.litmocracy.com" target=3D"_blank">Litmocracy</a=
> and <a href=3D"http://www.memeracing.net" target=3D"_blank">
Meme Racing</a> (in alpha). <br>
I'm the webmaster for <a href=3D"http://www.voluntaryist.com" target=3D=
"_blank">The Voluntaryist</a> which now accepts Bitcoin.<br>
I also code for <a href=3D"http://dollarvigilante.com/" target=3D"_blank">T=
he Dollar Vigilante</a>.<br>
"He ought to find it more profitable to play by the rules" - Sato=
shi Nakamoto</div>
</div>
</div>
</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--0000000000009d61520576baf1ec--
|