Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1StDAk-0001M3-FV for bitcoin-development@lists.sourceforge.net; Mon, 23 Jul 2012 07:35:18 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.47 as permitted sender) client-ip=209.85.160.47; envelope-from=gmaxwell@gmail.com; helo=mail-pb0-f47.google.com; Received: from mail-pb0-f47.google.com ([209.85.160.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1StDAg-00077k-Rx for bitcoin-development@lists.sourceforge.net; Mon, 23 Jul 2012 07:35:18 +0000 Received: by pbbrq2 with SMTP id rq2so9745913pbb.34 for ; Mon, 23 Jul 2012 00:35:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.219.162 with SMTP id pp2mr32909487pbc.85.1343028908724; Mon, 23 Jul 2012 00:35:08 -0700 (PDT) Received: by 10.68.59.6 with HTTP; Mon, 23 Jul 2012 00:35:08 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 03:35:08 -0400 Message-ID: From: Gregory Maxwell To: grarpamp Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.1 (-) 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 (gmaxwell[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.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1StDAg-00077k-Rx Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [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: Mon, 23 Jul 2012 07:35:18 -0000 On Sun, Jul 22, 2012 at 6:37 PM, grarpamp wrote: > It already takes a month to build a new blockchain, let alone keep up > with new incoming blocks. Please fix your software stack. Something is wrong with your system and I doubt it has much to do with bitcoin. A full sync here takes something like an hour. There are certainly lots of scalability things going on, but there is no cause for concern for regular hardware being unable to _keep up_ without a hardforking change to the protocol first.