Quote from: vpitcher07 on May 06, 2015, 12:07:07 AM

Quote from: achow101 on May 05, 2015, 11:55:36 PM

Quote from: benjamindees on May 05, 2015, 09:07:55 PM

That's what 20 MB blocks require. That means, you receive the blockchain, that's 84 gigabytes per month. You send the blockchain to one peer, that's another 84 gigabytes per month.

There is only one time that one node has to upload or download all of the blockchain, and that is when a new full node comes online. It downloads the blockchain from one other node, and that is its only full blockchain download. If you don't want to be the node that has to upload the full blockchain, you can change that in your config file. The full blockchain download is definitely under the monthly caps. Those 84 gigabytes happens only once in the nodes lifetime, and the blockchain won't be 84 gigs even when 20 MB blocks are accepted. The 20 MB blocks just mean that the maximum block size accepted by the network is 20 MB, not that every block is 20 MB. Get your facts straight.

I was about to ask the same thing but you answered my question. I don't understand why everyone is freaking out over 20MB blocks as if it's going to happen right when this is implemented. Look at the last blocks mined on blockchain.info. None of them are even 1MB yet (most of them not even close). So unless I'm missing something, I really don't understand the bandwidth/storage argument against this.

Looking at another chart :
https://blockchain.info/en/charts/n-transactions-excluding-chains-longer-than-10?showDataPoints=false×pan=&show_header=true&daysAverageString=7&scale=0&address=

Seems like there are only 30k real transactions per day in bitcoinland.
Let's assume 1 pf every 100 McDonalds customers would pay in bitcoin....

Care to tell me what would be the size of the blocks?