From: Segue <012mistery@frankentrikes•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Why not archive the backend of Bitcoin blockchain?
Date: Wed, 9 May 2018 17:56:00 -0700 [thread overview]
Message-ID: <fd403450-cf7f-ce56-79ca-93c77c042289@frankentrikes.com> (raw)
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 :).
Segue
next reply other threads:[~2018-05-10 0:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 0:56 Segue [this message]
2018-05-10 6:48 ` アルム カールヨハン
2018-05-10 7:54 ` ZmnSCPxj
2018-05-10 6:50 ` Jim Posen
2018-05-10 10:52 ` Patrick Shirkey
2018-06-12 8:40 ` Kulpreet Singh
2018-06-13 13:33 ` Christian Decker
2018-06-13 15:32 ` Brian Lockhart
2018-06-13 16:17 ` Christian Decker
2018-06-14 23:24 ` Brian Lockhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd403450-cf7f-ce56-79ca-93c77c042289@frankentrikes.com \
--to=012mistery@frankentrikes$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox