summaryrefslogtreecommitdiff
path: root/a0/a31f452fb8941ded3e8b77d5f10566f0200e9a
blob: e34c67d2fc4564e852f96b1436763e2064583f89 (plain)
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
Return-Path: <pshirkey@boosthardware.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 15807949
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 10 May 2018 10:58:10 +0000 (UTC)
X-Greylist: delayed 00:05:27 by SQLgrey-1.7.6
Received: from mail.boosthardware.com (boosthardware.com [138.201.186.201])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id 7AC93683
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 10 May 2018 10:58:09 +0000 (UTC)
Received: from boosthardware.com (localhost.localdomain [127.0.0.1])
	by mail.boosthardware.com (Postfix) with ESMTP id 41FC380EE8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 10 May 2018 12:52:40 +0200 (CEST)
Received: from 109.103.113.193
	(SquirrelMail authenticated user pshirkey@boosthardware.com)
	by boosthardware.com with HTTP; Thu, 10 May 2018 12:52:41 +0200
Message-ID: <0cc0a7249708ad26a7cbef702370b234.squirrel@boosthardware.com>
In-Reply-To: <fd403450-cf7f-ce56-79ca-93c77c042289@frankentrikes.com>
References: <fd403450-cf7f-ce56-79ca-93c77c042289@frankentrikes.com>
Date: Thu, 10 May 2018 12:52:41 +0200
From: "Patrick Shirkey" <pshirkey@boosthardware.com>
To: "Bitcoin Protocol Discussion" <bitcoin-dev@lists.linuxfoundation.org>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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: Thu, 10 May 2018 12:45:10 +0000
Subject: Re: [bitcoin-dev] Why not archive the backend of Bitcoin blockchain?
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: Thu, 10 May 2018 10:58:10 -0000


> On 3/17/18, someone posted on the Lightning-dev list, "Can I try
> Lightning without running a fully-fledged bitcoin block chain? (Yubin
> Ruan)."  The inquirer was asking because he didn't have much space to
> store the entire blockchain on his laptop.
>
> I replied:
>
> "Developers,
>
> On THIS note and slightly off-topic but relevant, why can't chunks of
> blockchain peel off the backend periodically and be archived, say on
> minimum of 150 computers across 7 continents?
>
> It seems crazy to continue adding on to an increasingly long chain to
> infinity if the old chapters (i.e. more than, say, 2 years old) could be
> stored in an evenly distributed manner across the planet. The same 150
> computers would not need to store every chapter either, just the index
> would need to be widely distributed in order to reconnect with a chapter
> if needed. Then maybe it is no longer a limitation in the future for
> people like Yubin. "
>
> It was suggested by a couple of lightning developers that I post this
> idea on the bitcoin-dev list.  So, here I post :).
>

You can already use the "prune" flag to get a snapshot of the blockchain
but it is incompatible with "txindex" and "rescan" so maybe that is and
issue for lightning nodes?




-- 
Patrick Shirkey
Boost Hardware