Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <rob.golding@astutium.com>) id 1VIRox-00014p-S0
	for bitcoin-development@lists.sourceforge.net;
	Sat, 07 Sep 2013 23:21:39 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of astutium.com
	designates 80.76.216.60 as permitted sender)
	client-ip=80.76.216.60; envelope-from=rob.golding@astutium.com;
	helo=cpanel4.hosting.astutium.com; 
Received: from cpanel4.hosting.astutium.com ([80.76.216.60])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1VIRov-00063t-PK
	for bitcoin-development@lists.sourceforge.net;
	Sat, 07 Sep 2013 23:21:39 +0000
Received: from localhost ([127.0.0.1]:36429 helo=astutium.com)
	by cpanel4.hosting.astutium.com with esmtpa (Exim 4.80.1)
	(envelope-from <rob.golding@astutium.com>) id 1VIRop-0000wo-8x
	for bitcoin-development@lists.sourceforge.net;
	Sun, 08 Sep 2013 00:21:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Sun, 08 Sep 2013 00:21:31 +0100
From: rob.golding@astutium.com
To: <bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CAE0e52XQSMJj9pDb3OEMyAYkChi7=Y9=phKMm34zh1NQFSdcLw@mail.gmail.com>
References: <CAE0e52XQSMJj9pDb3OEMyAYkChi7=Y9=phKMm34zh1NQFSdcLw@mail.gmail.com>
Message-ID: <eb196950d9bf667a3b149a74c0d99ab0@astutium.com>
X-Sender: rob.golding@astutium.com
User-Agent: Roundcube Webmail/0.8.5
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - cpanel4.hosting.astutium.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - astutium.com
X-Get-Message-Sender-Via: cpanel4.hosting.astutium.com: authenticated_id:
	rob.golding@astutium.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: -3.9 (---)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1VIRov-00063t-PK
Subject: Re: [Bitcoin-development] Blockchain archival
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 07 Sep 2013 23:21:40 -0000

> bitcoin protocol needs an archival system so the blockchain doesn't
> become too big to download

Some people may want it all ...

Balance at Point-In-Time summaries (say up to the penultimate 
difficulty adjustment) would be one simple way.
And make new-adopters get up and running in minutes not days, which can 
only be a good thing.

If going that route, then solutions to the 'consolidate 
addresses/wallets' question and formal 'discard' of addresses could get 
addressed.

Rob