public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Slurms MacKenzie" <slurms@gmx.us>
To: thomas@thomaszander.se
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
Date: Fri, 24 Jul 2015 11:43:00 +0200	[thread overview]
Message-ID: <trinity-387914cc-b201-48e9-8eb0-8708a8e95199-1437730980193@3capp-mailcom-bs01> (raw)
In-Reply-To: <1536871.OeviznBiyx@coldstorage>

> Sent: Friday, July 24, 2015 at 10:52 AM
> From: "Thomas Zander via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
> To: bitcoin-dev@lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
>
> 
> The reference to bandwidth increases makes no sense, the bandwidth in most of 
> the world is already far exceeding the 8Mb limit. Not everyone lives where you 
> live :)
> 
> In Germany you buy a 150Mbit connection for a flatrate and a cheap monthly 
> rate, for instance.  Not saying that Germany is where all the miners are, but 
> since 150Mbit allows one to comfortably have 16 megabyte blocks, it is a good 
> example of how far off Luke's calculations are from real-world.

I'll have better stats available soon, but this does not reflect the current state of the network. 

Only 4% of my initial crawl presented bandwidth above your stated 18MB/s. 


  reply	other threads:[~2015-07-24  9:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 15:55 [bitcoin-dev] BIP 102 - kick the can down the road to 2MB Jeff Garzik
2015-07-17 16:11 ` Andrew
2015-07-17 16:12 ` Tier Nolan
2015-07-17 16:14   ` Tier Nolan
2015-07-17 17:57 ` Ross Nicoll
2015-07-17 19:06   ` Chris Wardell
2015-07-17 19:13     ` Ross Nicoll
2015-07-19 22:51   ` Ross Nicoll
2015-07-21  9:26     ` Jorge Timón
2015-07-21 13:04       ` Peter Todd
2015-07-21 13:58         ` Peter Todd
2015-07-22 15:51           ` Tom Harding
2015-07-22 17:02           ` Sriram Karra
2015-07-22 17:40             ` Sriram Karra
2015-07-22 17:43           ` Jeff Garzik
2015-07-22 22:30             ` Peter Todd
2015-07-23  5:39               ` jl2012
2015-07-22 17:00         ` jl2012
2015-07-21 22:05       ` Ross Nicoll
2015-07-23 11:24         ` Jorge Timón
2015-07-17 20:29 ` Luke Dashjr
2015-07-17 21:13   ` Angel Leon
2015-07-17 22:25   ` Tier Nolan
2015-07-18  9:22     ` Jorge Timón
2015-07-18  9:24       ` Jorge Timón
2015-07-24  8:52   ` Thomas Zander
2015-07-24  9:43     ` Slurms MacKenzie [this message]
2015-07-18  4:32 ` Venzen Khaosan
2015-07-17 22:40 Raystonn

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=trinity-387914cc-b201-48e9-8eb0-8708a8e95199-1437730980193@3capp-mailcom-bs01 \
    --to=slurms@gmx.us \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=thomas@thomaszander.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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