Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1StCzo-0006b4-Mf for bitcoin-development@lists.sourceforge.net; Mon, 23 Jul 2012 07:24:00 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.175 as permitted sender) client-ip=209.85.217.175; envelope-from=raphbot@gmail.com; helo=mail-lb0-f175.google.com; Received: from mail-lb0-f175.google.com ([209.85.217.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1StCzj-0005bU-5A for bitcoin-development@lists.sourceforge.net; Mon, 23 Jul 2012 07:24:00 +0000 Received: by lbol5 with SMTP id l5so8164803lbo.34 for ; Mon, 23 Jul 2012 00:23:48 -0700 (PDT) Received: by 10.152.135.200 with SMTP id pu8mr15508264lab.8.1343028228624; Mon, 23 Jul 2012 00:23:48 -0700 (PDT) Received: from [192.168.91.242] (33.197-14-84.ripe.coltfrance.com. [84.14.197.33]) by mx.google.com with ESMTPS id j5sm2646860lbg.1.2012.07.23.00.23.46 (version=SSLv3 cipher=OTHER); Mon, 23 Jul 2012 00:23:47 -0700 (PDT) Message-ID: <500CFC01.2070802@gmail.com> Date: Mon, 23 Jul 2012 09:23:45 +0200 From: Raphael NICOLLE User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: grarpamp References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.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 (raphbot[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 X-Headers-End: 1StCzj-0005bU-5A 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:24:00 -0000 Hello, Even though I'm not a dev, I can't agree more, and would like to know if they are expected steps being taken, some fixes coming, or whatever? Thank you all for your hard work. Raphael On 07/23/2012 12:37 AM, grarpamp wrote: > 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. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development