Quote from: franky1 on July 01, 2016, 01:08:09 AM

Quote from: RealBitcoin on July 01, 2016, 12:46:17 AM

Yea and what about orphan blocks, you just said that by ignoring the side-effects in entirety.

We can measure the risk-reward situation, but we also need to analyze side-effects as well.

Every top-down control system is inneficient since it always ignores sideeffects and unknown sideeffects, so only the market can decide what is best for bitcoin.

http://bitcoinocracy.com/arguments/the-block-size-limit-should-be-constrained-only-by-technology-that-grows-exponentially

http://bitcoinocracy.com/arguments/if-non-core-hard-fork-wins-major-holders-will-sell-btc-driving-price-into-the-ground

I fear if a fork happens bitcoin's price will crash very hard. So yes everyone votes with his money.

your opinion. and it sounds more like scare mongering rather than researched info..
by the way..
https://blockchain.info/charts/n-orphaned-blocks?timespan=2year
this may help..
https://blockchain.info/charts/avg-block-size?timespan=2year

orphans go down as blocksize goes up.

this is because miners have money on the line. they are not going to risk it, instead they are going to look for methods to be more efficient and ensure their work gets paid off..(they learned their lesson in july 2015) and became more efficient afterwards

for instance.. lets say the blocklimit was 2mb today.. pools are not going to jump to 2mb tomorrow... just like they didnt jump to 1mb back in 2013 when it was finally possible to go beyond the 500k DB bug of v0.7-v0.8 era and able to then utilise the 1mb maxblocksize buffer
it was slow natural growth at a pace they deemed safe. at a pace they deemed efficient

Actually there is no correlation, so i deleted that post.

We either need more data, but i doubt that we have time for that. Also if we increase it to 2mb, and then a lot of ophans will appear, it's not like we can decrease it back to 1 mb.

SO that will be a 1 way deal, therefore if a hardfork were to happen, it should be better tested out and simulated before implemented, because we cant roll back if something bad happens.