Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1St4m4-00025R-3t for bitcoin-development@lists.sourceforge.net; Sun, 22 Jul 2012 22:37:16 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; envelope-from=grarpamp@gmail.com; helo=mail-ob0-f175.google.com; Received: from mail-ob0-f175.google.com ([209.85.214.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1St4m3-00069h-Go for bitcoin-development@lists.sourceforge.net; Sun, 22 Jul 2012 22:37:16 +0000 Received: by obcva7 with SMTP id va7so9133438obc.34 for ; Sun, 22 Jul 2012 15:37:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.21.198 with SMTP id x6mr17849088oee.24.1342996629881; Sun, 22 Jul 2012 15:37:09 -0700 (PDT) Received: by 10.76.81.10 with HTTP; Sun, 22 Jul 2012 15:37:09 -0700 (PDT) Date: Sun, 22 Jul 2012 18:37:09 -0400 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -0.9 (/) 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.7 AWL AWL: From: address is in the auto white-list X-Headers-End: 1St4m3-00069h-Go Subject: [Bitcoin-development] Scalability issues 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: Sun, 22 Jul 2012 22:37:16 -0000 Given a testbed: Pentium 4 1.8GHz single core, 2GB ram, FreeBSD 8, disk is geli aes-128 + zfs sha-256, bitcoin 0.6.3, Tor proxy, An estimate is made that by the end of the year bitcoin will completely overrun the capabilities of this reasonable class of machines. It already takes a month to build a new blockchain, let alone keep up with new incoming blocks. Yes, it also has workstation duties, yet even if those were removed, it would probably choke by mid 2013. It would appear bitcoin has some *serious* scalability hurdles coming down the road. Most certainly if the user expects to independantly build, manage, and trust their own blockchain.