Quote from: jonny1000 on May 18, 2016, 02:43:51 AM

This is why we should do it form a position of strength. The Classic node count is down to 15% and the hashrate is around 5.5%. I still think these metrics are too high for a hardfork to 2MB. However if they fall further and Core looks stronger, then I think we should implement a hardfork to 2MB.

You've come back to this point several times, and for some reason you seem to really believe that an increase in the physical blocksize limit is actually necessary.

I have not seen any actual evidence that it is actually necessary, and it does not solve any real world problem to increase the physical blocksize limit while potentially adding more bloat, so why implement a change that is not needed and that also has some downsides including bloat? except if you happen to believe the loud screams that there is some kind of a real and actual problem

Further seg wit seems to be fairly soon around the corner, and there is likely a certain level of uncertainty regarding how much capacity in practice seg wit is going to cause.... If seg wit is a fairly major change, then why make two changes simultaneously? Why not just see how seg wit plays out and then let's say that down the road it does become apparent that an actual blocksize limit increase is needed, then yes it could be added at any time that it is actually needed, no?