public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: rob.golding@astutium.com
To: <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Blockchain archival
Date: Sun, 08 Sep 2013 00:21:31 +0100	[thread overview]
Message-ID: <eb196950d9bf667a3b149a74c0d99ab0@astutium.com> (raw)
In-Reply-To: <CAE0e52XQSMJj9pDb3OEMyAYkChi7=Y9=phKMm34zh1NQFSdcLw@mail.gmail.com>

> 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




  reply	other threads:[~2013-09-07 23:21 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 [this message]
2013-09-07 23:33   ` Luke-Jr
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=eb196950d9bf667a3b149a74c0d99ab0@astutium.com \
    --to=rob.golding@astutium.com \
    --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