public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Harding <tomh@thinlink•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Is there a way to estimate the maximum number of transactions per minute Bitcoin can handle as it is today?
Date: Sat, 31 Jan 2015 22:50:41 -0800	[thread overview]
Message-ID: <54CDCCC1.7090309@thinlink.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1501311341580.21504@nzrgulfg.ivfhpber.pbz>

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



  reply	other threads:[~2015-02-01  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31  0:48 Angel Leon
2015-01-31  2:58 ` Nick Simpson
2015-01-31 13:11   ` Wladimir
2015-02-01  6:50     ` Tom Harding [this message]
2015-01-31  2:58 ` Allen Piscitello
2015-01-31 17:04 ` Mike Hearn
2015-01-31 20:08   ` Angel Leon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54CDCCC1.7090309@thinlink.com \
    --to=tomh@thinlink$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox