Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.47 as permitted sender)
	client-ip=209.85.160.47; envelope-from=laanwj@gmail.com;
	helo=mail-pw0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAD2Ti2_vGc+SJX_+uTz4ZVk1r5DhCOm6n3yKW16o9QaPKTQkHQ@mail.gmail.com>
References: <CAD2Ti2_vGc+SJX_+uTz4ZVk1r5DhCOm6n3yKW16o9QaPKTQkHQ@mail.gmail.com>
Date: Wed, 8 Feb 2012 09:34:38 +0100
Message-ID: <CA+s+GJCh4n2BAj=sFfUnUBgcJuJ9EPe=5qYftZ8SogDX_EQATg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: grarpamp <grarpamp@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec54693e52d51f104b86fc4c0
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Scaling at the end user level
Precedence: list

--bcaec54693e52d51f104b86fc4c0
Content-Type: text/plain; charset=UTF-8

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

--bcaec54693e52d51f104b86fc4c0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><div class=3D"gmail_quote">On Wed, Feb 8, 2012 at 6:18 =
AM, grarpamp <span dir=3D"ltr">&lt;<a href=3D"mailto:grarpamp@gmail.com">gr=
arpamp@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A freshly deployed client on an old p4 has been idly crunching away<br>
at building and verifying the initial chain for about a week now. It<br>
should be done in a day or two. This seems rather untenable for<br>
new users. Have any groups published proposals for distributing<br>
a weekly precomputed bootstrap chain?<br>
rsync? db_dump &gt; git &gt; db_load?<br>
There is also 50% or more compression available in the index<br>
and chain.<br></blockquote><div><br></div><div>I have proposed packaging pa=
rt of the block chain (doesn&#39;t even have to be weekly, just until the l=
ast checkpoint), but people fear it runs contrary to the distributed approa=
ch of Bitcoin.</div>
<div><br></div><div>Which is kind of true:</div><div><br></div><div>- If it=
 is imported un-validated, you have to rely on the packager to lie to you (=
insert false transactions etc)</div><div>- If it has to be validated, you w=
in nothing, your computer has to crunch for days anyway</div>
<div><br></div><div>BTW: On such an old computer you should probably use on=
e of the thin clients.<br><div><br></div><div>Wladimir</div></div><div><br>=
</div></div></div>

--bcaec54693e52d51f104b86fc4c0--