From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rv2zK-0002Hq-9Z for bitcoin-development@lists.sourceforge.net; Wed, 08 Feb 2012 08:34:50 +0000 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; Received: from mail-pw0-f47.google.com ([209.85.160.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rv2zE-0006s6-SN for bitcoin-development@lists.sourceforge.net; Wed, 08 Feb 2012 08:34:50 +0000 Received: by pbcum15 with SMTP id um15so246443pbc.34 for ; Wed, 08 Feb 2012 00:34:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.74.69 with SMTP id r5mr67075515pbv.118.1328690079027; Wed, 08 Feb 2012 00:34:39 -0800 (PST) Received: by 10.142.43.2 with HTTP; Wed, 8 Feb 2012 00:34:38 -0800 (PST) In-Reply-To: References: Date: Wed, 8 Feb 2012 09:34:38 +0100 Message-ID: From: Wladimir To: grarpamp Content-Type: multipart/alternative; boundary=bcaec54693e52d51f104b86fc4c0 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Rv2zE-0006s6-SN Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Scaling at the end user level X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 08:34:50 -0000 --bcaec54693e52d51f104b86fc4c0 Content-Type: text/plain; charset=UTF-8 On Wed, Feb 8, 2012 at 6:18 AM, grarpamp 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

On Wed, Feb 8, 2012 at 6:18 = AM, grarpamp <gr= arpamp@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 pa= rt of the block chain (doesn'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.

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 w= in nothing, your computer has to crunch for days anyway

BTW: On such an old computer you should probably use on= e of the thin clients.

Wladimir

=
--bcaec54693e52d51f104b86fc4c0--