Lauda,
Sorry, I wasn't trying to show your figures as inaccurate, just that 100% full blocks on average will not happen.
I have removed ref to you in OP. (I only used your name to show I hadn't "made up numbers".) I see it might have been misread.
I have also tried to clarify and edited my request for figures in OP. (i was not asking for "more accurate figures than Lauda's 70%" but "how many empty blocks will be produced on average")
I think it is clearer now and hope that resolve your issue?
My time frame is a bit sketchy, 2 weeks, that is guesswork. But surely soon, before segwit anyway, if bitcoin adoption is growing.
How "extremely bad" it gets depend on personal and communal thresholds/viewpoint/outcome. I never said those words.
But a fork to Classic becomes far more likely if things do get "extremely bad".
My point, Core will force a fork to Classic, as the only option to quick consensus, before things get "extremely bad".
Of course 2mb without limitations is unsafe. But those limitations could be applied. Core could have solved this.
Anyway, Core need not have planned to double the block size to 2mb. I am not calling for 2mb here.
I am saying Core could have had small block size increase/s "planned and tested" for release "if needed", as a safety net. (foresight) While they work on segwit.
Then a sudden fork to classic is less likely.
Segwit is not a done deal yet. Do core have a planned safety net option "if needed" before segwit is resolved?