Quote from: iamnotback on April 03, 2017, 11:53:32 PM

Quote from: Carlton Banks on April 03, 2017, 11:50:45 PM

By example let's say we increase the blocksize from 1MB to 2MB, that's increasing the average amount of transactions from 300,000 per day to 600,000 per day.

So, 1MB:300,000, 2MB:600,000.

And that's the same ratio, for 1MB or 2MB. i.e. 1:3 is exactly equivalent to 2:6

So that's not scaling, the scale is identical. All blocksize changes do to change the capacity is change the amount of resources the Bitcoin network uses at the exact same scale, no matter how much the blocksize changes.

That is incorrect.

Block size increases, exponentially increase hashrate wastage due to exponential orphan rate increase.

It doesn't scale because the frictional costs of raising the block size are exponentially bad.

Have you guys ever looked at the equation for orphan rate. It relates block size to block period in an exponential relationship.

doesnt matter if its PoS or PoW.
the orphan rate due to block data is a separate thing.

infact by costing so much electric. pools are probably going to do a better job at validating the data before creating a has that needs to be SHA'd ..
compared to a block that just needs to be signed thus decreasing orphan risk because they know how much work is involved in securing the data

oh. and here is the fnny part

if you have a block with 10 transactions or 1000 transactions. does not mean the PoW difficulty changes or the amount of hashes needed.