Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Ruzvf-0005Am-Fc for bitcoin-development@lists.sourceforge.net; Wed, 08 Feb 2012 05:18:51 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; envelope-from=grarpamp@gmail.com; helo=mail-ww0-f41.google.com; Received: from mail-ww0-f41.google.com ([74.125.82.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Ruzve-0000xD-Qw for bitcoin-development@lists.sourceforge.net; Wed, 08 Feb 2012 05:18:51 +0000 Received: by wgbdt11 with SMTP id dt11so4724531wgb.4 for ; Tue, 07 Feb 2012 21:18:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.103.97 with SMTP id fv1mr38671488wib.17.1328678324745; Tue, 07 Feb 2012 21:18:44 -0800 (PST) Received: by 10.180.103.227 with HTTP; Tue, 7 Feb 2012 21:18:44 -0800 (PST) Date: Wed, 8 Feb 2012 00:18:44 -0500 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -0.7 (/) 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 (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 0.9 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Ruzve-0000xD-Qw Subject: [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 05:18:51 -0000 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. Of some known future issues... raw transaction rate, the eventual pay (or extort?, depending on how megapools pan out) to process mining environment, and scaling the client count itself... this one appears to be already present.