Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 390ED7F9 for ; Thu, 10 May 2018 06:48:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 80127685 for ; Thu, 10 May 2018 06:48:40 +0000 (UTC) Received: from ip-10-217-1-36.ap-northeast-1.compute.internal (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id 0AB7114C0DF for ; Thu, 10 May 2018 15:48:39 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1) by 0 with SMTP; 10 May 2018 15:48:39 +0900 X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id 018C54C079 for ; Thu, 10 May 2018 15:48:39 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw24.oz.hdemail.jp (ip-10-185-138-250.ap-northeast-1.compute.internal [10.185.138.250]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id E9D3714C0DF for ; Thu, 10 May 2018 15:48:38 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qt0-f198.google.com (lb07.oz.hdemail.jp [54.238.57.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw24.oz.hdemail.jp (Postfix) with ESMTP id 46F2E148C109 for ; Thu, 10 May 2018 15:48:38 +0900 (JST) X-Received: by mail-qt0-f198.google.com with SMTP id t3-v6so866250qto.14 for ; Wed, 09 May 2018 23:48:38 -0700 (PDT) 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; bh=+39Zp4tNhSNc/3OwXJlmAEElFqI1gz5ZyS4ZPGQiXto=; b=tTuKMsQ679MISph1aGKDKe7fHzUXIMvhaUGkXUValHPQhYsPpOB+rRXTyqqm5tqHM6 g7KotUa85HHad+sEJcItrI+r3WamIOqxq4qtXUnz21e/irbXtB6K+n5ggYwtiaVAl1Bp 3eGWPWpEVGYASy2i26KRlpxIPxu1Cq9PO08zcrx14wkmNYhm157GYDUkkOH+DPm6swuE 1b/mjlPrMe0lRi9JzGHDTU7zfhPTupMQtMtsahDVR9mX+akC832S7vybKltatL4Umh+P jtWFz/Y1gQMygMDR92bZjBfvXvF3EZZl2UfuTgLmvIvr+b+g+Mbj2khfHrWpO/E+a3Ns HaUA== X-Gm-Message-State: ALKqPwdP001DiMLPbv0PK070luizKhN7wzbSi7kaxRUn/nSgNvioPJFU Ql/pqpba3J76TIS+McNVe8ZpwbGfkmoGa3zB6uozUj647KXuaMhGUgubyUQI5DDTdpCa6MLbsZM Xvo7RcsrfVrdxCzeXSLJcHfBNN1Bhuyw0EwHnTPKyRQt4WCvTKrS/5uBuchBU1yAkN6qzOxWHG0 jR6RHh6eZ3VGNiWgClwAOEcEmcbFNLgc84Q4cT7bII+oF1ZaaQrl2k2+iNsuQ2uZapAfy2Xejdd daQJfGPUotc0STBeK5k2OWcAEBn+GLQ2j0ZkJOAfgclYkuHpExMHKaQ3AVpOs1sbIksPMI6fUd5 zC+htPj7MRYeDuaQxiw5PFr1d3s= X-Received: by 2002:a37:338f:: with SMTP id z137-v6mr125676qkz.233.1525934916744; Wed, 09 May 2018 23:48:36 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoKl9ukmpOLF30syXCKKAVd3Wizw7Ib/A908hXigBOA8pfv2wqHpl7dXJMEgBdYPuyekFroN9hyw7k5cTJgM4w= X-Received: by 2002:a37:338f:: with SMTP id z137-v6mr125661qkz.233.1525934916412; Wed, 09 May 2018 23:48:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.12.208.90 with HTTP; Wed, 9 May 2018 23:48:16 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?B?44Ki44Or44Og44CA44Kr44O844Or44Oo44OP44Oz?= Date: Thu, 10 May 2018 15:48:16 +0900 Message-ID: To: Segue <012mistery@frankentrikes.com>, Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, FROM_EXCESS_BASE64, RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 06:48:41 -0000 He can use pruning to only store the last X MB of the blockchain. It will store the UTXO set though, which is a couple of GBs. In total, a pruned node with pruning set to 1000 MB ends up using 4.5 GB currently, but it varies slightly due to the # of UTXOs in existence. On Thu, May 10, 2018 at 9:56 AM, Segue via bitcoin-dev wrote: > 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 > > > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev