From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Blockchain archival
Date: Sat, 7 Sep 2013 23:33:52 +0000 [thread overview]
Message-ID: <201309072333.53026.luke@dashjr.org> (raw)
In-Reply-To: <eb196950d9bf667a3b149a74c0d99ab0@astutium.com>
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
next prev parent reply other threads:[~2013-09-07 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 21:06 [Bitcoin-development] Blockchain archival Chris Evans
2013-09-07 23:21 ` rob.golding
2013-09-07 23:33 ` Luke-Jr [this message]
2013-09-08 3:56 ` rob.golding
2013-09-08 4:13 ` Jeff Garzik
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=201309072333.53026.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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