From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YHonS-0008EH-1F for bitcoin-development@lists.sourceforge.net; Sun, 01 Feb 2015 07:18:18 +0000 X-ACL-Warn: Received: from mail-pa0-f53.google.com ([209.85.220.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YHonQ-0002al-8Z for bitcoin-development@lists.sourceforge.net; Sun, 01 Feb 2015 07:18:18 +0000 Received: by mail-pa0-f53.google.com with SMTP id kx10so69341894pab.12 for ; Sat, 31 Jan 2015 23:18:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XzWHu17mTYcwfCawcPQIe05o196VcfqPOZY0lc5Fp8o=; b=Ziym8FPI9+N7zHeafkaKLoa0bRBN3ShVHI7B/d5UzXo8NQ7mG+nzHG07Kcb9/FJhVG ne3+5RPmq2RzE58YDapNfEIarg6mgc3ZUpRxJo/sO6CnAAMkQfGPaA148UW6D5ANO7IP u4z9e+5dt3awXlBRLCzZ//r5CWrvj9AmwMcUb65N8vy0Qio5WgOJdUMeQtjxCl9iBQng eIFiBPeNvvALrcbkckoLQrPgw07isMqYolkXeWsYIjxbr7TjDEV/6R22Zsb9s4n0Xcu0 kxlcyMOTaWMBeRYDoEidVlCjwIIcNgk0R5bdA/74zaZ4TvpR+ILVJUC9VMFcDQitcCy/ kQ6w== X-Gm-Message-State: ALoCoQkK8fqJuBoIkXLYhZaTh4h/idYmotpxzW1hkak9AFGNdiU2hhxpI5hFc2sjWPTZU70XxG70 X-Received: by 10.70.138.77 with SMTP id qo13mr10105354pdb.135.1422773439852; Sat, 31 Jan 2015 22:50:39 -0800 (PST) Received: from [192.168.1.89] (99-6-44-248.lightspeed.sntcca.sbcglobal.net. [99.6.44.248]) by mx.google.com with ESMTPSA id yq5sm15450770pac.15.2015.01.31.22.50.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Jan 2015 22:50:39 -0800 (PST) Message-ID: <54CDCCC1.7090309@thinlink.com> Date: Sat, 31 Jan 2015 22:50:41 -0800 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1YHonQ-0002al-8Z Subject: Re: [Bitcoin-development] Is there a way to estimate the maximum number of transactions per minute Bitcoin can handle as it is today? 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, 01 Feb 2015 07:18:18 -0000 On 1/31/2015 5:11 AM, Wladimir wrote: > The block chain is a single channel broadcasted over the entire world, > and I don't believe it will ever be possible nor desirable to > broadcast all the world's transactions over one channel. > > The everyone-validates-everything approach doesn't scale. It is however > useful to settle larger transactions in an irreversible, zero-trust > way. That's what makes the bitcoin system, as it is now, valuable. > > But it is absurd for the whole world to have to validate every > purchase of a cup of coffee or a bus ticket by six billion others. Well to be fair, nobody suggested 6 billion full nodes. Although some residential connections today do have Angel's 15G/10min... (sadly, not mine). One of the best points Gavin made is, it would be unwise to artificially limit the number of transactions below the technical capabilities of the network. That's how competitions are lost. http://gavintech.blogspot.com/2015/01/twenty-megabytes-testing-results.html