blob: dbf6df57250676ea3c5fa5ba1431150271fe0224 (
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
|
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 <luke@dashjr.org>) 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 <bitcoin-development@lists.sourceforge.net>;
Sat, 7 Sep 2013 23:33:55 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
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: <CAE0e52XQSMJj9pDb3OEMyAYkChi7=Y9=phKMm34zh1NQFSdcLw@mail.gmail.com>
<eb196950d9bf667a3b149a74c0d99ab0@astutium.com>
In-Reply-To: <eb196950d9bf667a3b149a74c0d99ab0@astutium.com>
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: <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: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
|