If a 1MB block takes 30 seconds to verify and validate, with the current code, wouldn't a 1GB block take 50 minutes to verify? Or is it not linear like that? I don't know, 1 block with transactions in it followed by 5 empty blocks seems inefficient. However, it appears the BCH team is working on this bottleneck, so why are we debating about my original concerns? The concern is no longer valid.
With Current Cable Bandwidth of 100 Mbits , 1 MB block can be transmitted in less than 1 second
100Mbits/8 = 12.5 megabytes per second
Even 8 MB blocks are nothing at modern internet speeds.
Correction: Original Node Verification was squared after every time interval ,
The Correct Verification is a Doubling with every increase in time interval
1 second= 2 Nodes Verified
2 second= 4 Nodes Verified
3 second= 8 Nodes Verified
4 second= 16 Nodes Verified
5 second= 32 Nodes Verified
6 second= 64 Nodes Verified
7 second=128 Nodes Verified
8 second=256 Nodes Verified
9 second=512 Nodes Verified
10 second=1024 Nodes Verified
11 second=2048 Nodes Verified
12 second=4096 Nodes Verified
13 second=8192 Nodes Verified
14 second=16384 Nodes Verified
15 second=32728 Nodes Verified
16 second=65456 Nodes Verified
17 second=130912 Nodes Verified
*Neither Bitcoin has over 20000 Full Nodes at the present time*Once the normal is 1 Gbps
1 Gbps/8 = 125 megabytes per second
Once the normal is 10 Gbps
10 Gbps/8 = 1.25 gigabytes per second
(This can easily support 1 Gigabyte Blocks and some providers are running at this speed today.)
(Within 17 seconds the 1 Gigabyte block could propagate through ~130912 Nodes.)Once the normal is 100 Gbs
100 Gbs/8 =12.5 Gigabytes per second
╥Aztek
The current bottleneck has nothing to do with the bandwidth of the internet connection. The current bottleneck has to do with the way the present BCH software, (and all other coins that derive from the BTC codebase) handles the mempool. In order for a miner to start including new transactions, they have to verify and validate the transactions in the most recently mined block. During this process, the miner's software must verify which transactions in the current mempool have already been included in a block, and those transactions are removed from the mempool. That way they don't include them in the current block they are mining, and end up mining an invalid block with duplicated transactions. However, it appears the BCH coding team, specifically nChain, is working on removing this bottleneck.
