From: Wladimir <laanwj@gmail•com>
To: grarpamp <grarpamp@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Scaling at the end user level
Date: Wed, 8 Feb 2012 09:34:38 +0100 [thread overview]
Message-ID: <CA+s+GJCh4n2BAj=sFfUnUBgcJuJ9EPe=5qYftZ8SogDX_EQATg@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti2_vGc+SJX_+uTz4ZVk1r5DhCOm6n3yKW16o9QaPKTQkHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Wed, Feb 8, 2012 at 6:18 AM, grarpamp <grarpamp@gmail•com> wrote:
> A freshly deployed client on an old p4 has been idly crunching away
> at building and verifying the initial chain for about a week now. It
> should be done in a day or two. This seems rather untenable for
> new users. Have any groups published proposals for distributing
> a weekly precomputed bootstrap chain?
> rsync? db_dump > git > db_load?
> There is also 50% or more compression available in the index
> and chain.
>
I have proposed packaging part of the block chain (doesn't even have to be
weekly, just until the last checkpoint), but people fear it runs contrary
to the distributed approach of Bitcoin.
Which is kind of true:
- If it is imported un-validated, you have to rely on the packager to lie
to you (insert false transactions etc)
- If it has to be validated, you win nothing, your computer has to crunch
for days anyway
BTW: On such an old computer you should probably use one of the thin
clients.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1432 bytes --]
next prev parent reply other threads:[~2012-02-08 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 5:18 grarpamp
2012-02-08 7:21 ` grarpamp
2012-02-08 8:34 ` Wladimir [this message]
2012-02-08 19:32 ` grarpamp
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='CA+s+GJCh4n2BAj=sFfUnUBgcJuJ9EPe=5qYftZ8SogDX_EQATg@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=grarpamp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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