From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VISK7-0002C9-EI for bitcoin-development@lists.sourceforge.net; Sat, 07 Sep 2013 23:53:51 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([89.207.132.31]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1VISK6-0003Jv-Dh for bitcoin-development@lists.sourceforge.net; Sat, 07 Sep 2013 23:53:51 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:222:4dff:fe50:4c49]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 57413AE8FD0 for ; Sat, 7 Sep 2013 23:33:55 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Sat, 7 Sep 2013 23:33:52 +0000 User-Agent: KMail/1.13.7 (Linux/3.7.8-gentoo; KDE/4.10.5; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201309072333.53026.luke@dashjr.org> X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1VISK6-0003Jv-Dh Subject: Re: [Bitcoin-development] Blockchain archival X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Sep 2013 23:53:51 -0000 On Saturday, September 07, 2013 11:21:31 PM rob.golding@astutium.com wrote: > > 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. There's no reason to require the full blockchain download before being up and running. Bitcoin-Qt 0.9 will (probably) have Pieter's work in this area to be usable very quickly, and download/verify the history in the background (there's no way to be completely trust-free without this). > If going that route, then solutions to the 'consolidate addresses/wallets' > question and formal 'discard' of addresses could get addressed. Not sure what you mean here. Addresses and wallets are two completely different things. Addresses are single-use destinations that point to a wallet (which is itself private and unknown to the network). Luke