user21351: It's widely known that Bitcoin has a limit of 1 MB per block.
However, the average block size is currently about 0.6 MB:

(original data)
According to this thread, Bitcoin transactions has an average size of 512 B. For the sake of simplicity, I'm not considering the 80 B of block header.
Given that, it's possible to fit about 1200 transactions in a block today. Considering that a new block will be mined every 10 minutes, the current capacity of the network is 2 tps:
1200 transactions/block / 10 min/block / 60 sec/min = 2 transactions/s

This seems like a very low throughput, specially when compared to Paypal's average rate of ~115tps and Visa's average rate of ~2000 tps.
Now imagine that I want to build a side chain that can handle as much traffic as Visa network. I want to mantain most of the parameters of the Bitcoin's blockchain (10 min/block, ~512 B/transaction), but being able to process 2000 tps.
In this case, my block size would be the following:
2000 transaction/s * 512 B/transaction * 60 s/min * 10 min/block = 586 MB/block

Is the estimate above correct, or am I missing something?
If it's correct, what are the impacts of switching from a 1 MB block size to 586 MB?

user31844: 
Is the estimate above correct, or am I missing something?

Your estimations seem (more or less) fine.

If it's correct, what are the impacts of switching from a 1 MiB block size to 586 MiB?

The two major ones I see are:

large blocks make full nodes more difficult/expensive to operate (i.e. requires better specs and better upload/download speeds); thus bad for decentralization as not many people will be able to run a full node
the blocks will take longer to propagate through the network, thus it increases the chances of orphan blocks and double spends.

For a more detailed list see here.
Note, that these concerns/drawbacks for an increased block size were raised for a 4, 8 or 32MBs increase... a 586MB increase would be way too excessive. And if you keep the parameters similar to bitcoin you would have the same issues in the side chain.

user5292: This is what the current block size debate is about and has been for more than a year now. I'll try not to repeat all of that here.
Your numbers seem roughly correct. Whether 600MB blocks are possible in your side chain depends on how your side chain would work. If you get rid of the Proof-of-Work security and it's all data center grade hardware and bandwidth between parties that trust each other to some degree, then there is no problem. It would probably make sense to lower the block time in that case too, for example 60MB every 1 minute. In fact, blocks probably wouldn't make sense at all anymore, why not just an append-only database of single transactions with some checksums for security?
Sidechains can trade some properties to gain other properties, which could make perfect sense. In the above example you trade decentralized trustless for high efficiency but trusted (users need to trust you and some other parties involved, and the government(s), and... ).
Bitcoin itself has as primary property that it's decentralized. Uncensorable, low barrier to entry for miners and for full nodes, peer2peer and all those good things are very much related and intertwined with that primary property. 600MB per block would completely destroy all that.
That is not to say there aren't many way cooler tricks that Bitcoin has up its sleeve. SegWit is currently being rolled out and will make making blocks smaller for certain nodes and better prunable, while making the effective blocksize around 1.75MB. As well as opening up paths to many more cool efficiency improvements like making multi-sig transactions significantly smaller.
An even bigger step will be made with two-way payment channels and networks built using those. Lightning Network is most well known name in this space. The idea is to cache hundreds and thousands (or orders more) of small transactions over weeks or months without putting a single one in a block. Only at the very beginning when opening such a channel and at the end when closing the channel will a transaction actually end up in a block. Organising these channels in a peer2peer network allows anyone to send and forward money through multiple hops, thus allowing everyone to pay anyone else without having to trust a single node and even having true instant and trustless payments (no need to wait for block confirmations).
Scaling is seldom simply turning one dial merely making an existing thing larger. Clever solutions have a much bigger impact while offering better trade offs.
Excuse me for not answering your exact question of listing all impacts of switching to a large block size. They are numerous and each can lead to its own endless bike shedding and handwaving discussion. The most important is that once a block has been mined it needs to propagate ASAP around the world or there's a risk that another miner will find another block where one of those blocks will be "orphaned" (wasted). More orphaned blocks leads to more centralized mining, as bigger miners have a bigger chance to win such an orphan race. "ASAP" in the case of a 10 minute interval is therefore on the order of seconds. Now that doesn't mean that the whole 600MB would need to be transferred to all nodes around the world within a few seconds, but it's still quite a challenge.
Currently 2MB is deemed the maximum safe blocksize, which SegWit pretty much covers. After further enhancements and efficiency improvements another doubling is likely possible in one or two years.

21351: <p>It's widely known that Bitcoin has a limit of <code>1 MB</code> per block.</p>

<p>However, the average block size is currently about <code>0.6 MB</code>:</p>

<p><img src="https://i.stack.imgur.com/jbH9G.png" alt="Bitcoin average block size"></p>

<p>(<a href="https://blockchain.info/charts/avg-block-size" rel="nofollow noreferrer">original data</a>)</p>

<p>According to this <a href="https://tradeblock.com/bitcoin/historical/1h-f-tsize_per_avg-01101" rel="nofollow noreferrer">thread</a>, Bitcoin transactions has an average size of <code>512 B</code>. For the sake of simplicity, I'm not considering the <code>80 B</code> of block header.</p>

<p>Given that, it's possible to fit about <code>1200</code> transactions in a block today. Considering that a new block will be mined every 10 minutes, the current capacity of the network is <code>2 tps</code>:</p>

<pre><code>1200 transactions/block / 10 min/block / 60 sec/min = 2 transactions/s
</code></pre>

<p>This seems like a very low throughput, specially when compared to Paypal's average rate of <code>~115tps</code> and Visa's average rate of <code>~2000 tps</code>.</p>

<p>Now imagine that I want to build a side chain that can handle as much traffic as Visa network. I want to mantain most of the parameters of the Bitcoin's blockchain (10 min/block, ~512 B/transaction), but being able to process <code>2000 tps</code>.</p>

<p>In this case, my block size would be the following:</p>

<pre><code>2000 transaction/s * 512 B/transaction * 60 s/min * 10 min/block = 586 MB/block
</code></pre>

<p>Is the estimate above correct, or am I missing something?</p>

<p>If it's correct, what are the impacts of switching from a <code>1 MB</code> block size to <code>586 MB</code>?</p>
 31844: <blockquote>
  <p>Is the estimate above correct, or am I missing something?</p>
</blockquote>

<p>Your estimations seem (more or less) fine.</p>

<blockquote>
  <p>If it's correct, what are the impacts of switching from a 1 MiB block size to 586 MiB?</p>
</blockquote>

<p>The two major ones I see are:</p>

<ul>
<li>large blocks make full nodes more difficult/expensive to operate (i.e. requires better specs and better upload/download speeds); thus bad for decentralization as not many people will be able to run a full node</li>
<li>the blocks will take longer to propagate through the network, thus it increases the chances of orphan blocks and double spends.</li>
</ul>

<p>For a more detailed list see <a href="https://en.bitcoin.it/wiki/Block_size_limit_controversy#Arguments_in_opposition_to_increasing_the_blocksize" rel="nofollow">here</a>.</p>

<p>Note, that these concerns/drawbacks for an increased block size were raised for a 4, 8 or 32MBs increase... a 586MB increase would be way too excessive. And if you keep the parameters similar to bitcoin you would have the same issues in the side chain.</p>
 5292: <p>This is what the current block size debate is about and has been for more than a year now. I'll try not to repeat all of that here.</p>

<p>Your numbers seem roughly correct. Whether 600MB blocks are possible in your side chain depends on how your side chain would work. If you get rid of the Proof-of-Work security and it's all data center grade hardware and bandwidth between parties that trust each other to some degree, then there is no problem. It would probably make sense to lower the block time in that case too, for example 60MB every 1 minute. In fact, blocks probably wouldn't make sense at all anymore, why not just an append-only database of single transactions with some checksums for security?</p>

<p>Sidechains can trade some properties to gain other properties, which could make perfect sense. In the above example you trade decentralized trustless for high efficiency but trusted (users need to trust you and some other parties involved, and the government(s), and... ).</p>

<p>Bitcoin itself has as primary property that it's decentralized. Uncensorable, low barrier to entry for miners and for full nodes, peer2peer and all those good things are very much related and intertwined with that primary property. 600MB per block would completely destroy all that.</p>

<p>That is not to say there aren't many way cooler tricks that Bitcoin has up its sleeve. SegWit is currently being rolled out and will make making blocks smaller for certain nodes and better prunable, while making the effective blocksize around 1.75MB. As well as opening up paths to many more cool efficiency improvements like making multi-sig transactions significantly smaller.</p>

<p>An even bigger step will be made with two-way payment channels and networks built using those. Lightning Network is most well known name in this space. The idea is to cache hundreds and thousands (or orders more) of small transactions over weeks or months without putting a single one in a block. Only at the very beginning when opening such a channel and at the end when closing the channel will a transaction actually end up in a block. Organising these channels in a peer2peer network allows anyone to send and forward money through multiple hops, thus allowing everyone to pay anyone else without having to trust a single node and even having true instant and trustless payments (no need to wait for block confirmations).</p>

<p>Scaling is seldom simply turning one dial merely making an existing thing larger. Clever solutions have a much bigger impact while offering better trade offs.</p>

<p>Excuse me for not answering your exact question of listing all impacts of switching to a large block size. They are numerous and each can lead to its own endless bike shedding and handwaving discussion. The most important is that once a block has been mined it needs to propagate ASAP around the world or there's a risk that another miner will find another block where one of those blocks will be "orphaned" (wasted). More orphaned blocks leads to more centralized mining, as bigger miners have a bigger chance to win such an orphan race. "ASAP" in the case of a 10 minute interval is therefore on the order of seconds. Now that doesn't mean that the whole 600MB would need to be transferred to all nodes around the world within a few seconds, but it's still quite a challenge.</p>

<p>Currently 2MB is deemed the maximum safe blocksize, which SegWit pretty much covers. After further enhancements and efficiency improvements another doubling is likely possible in one or two years.</p>
