I'm trying to find out if this is different to the last gavin update, where the rolling increase was proposed 20mb first and X% per increment after. Or if this new proposal is a different hacked increase to 20mb, thus requiring another hard fork in the future should this new limit need changing?
thanks
The new proposal is similar to Satoshi's original 2010 example where the max block size increases after a predetermined block height (115,000).
Instead, Gavin has
code allowing a one-off increase, blocks up to 20MB which are later than a predetermined timestamp (1st March 2016 00:00:00 UTC). Block timestamps can only vary +/- a couple of hours from UTC. The advantage is that everyone will know the date by which they need to have their full node upgraded. Working with block height means that the cut-over could vary, a couple of weeks earlier or later, depending on difficulty changes.
Hopefully, this will get unanimous consensus in core dev (the 5 people with commit access) so that there is not a split. In theory Gavin could commit this change and someone else reverse it in an "edit war". That would be a sad situation. However, Gavin has a trump card which means he *should* be able to prevail even if he were to be in a minority of 4:1 against. Satoshi gave him the key to broadcast
alerts to all the instances of BitcoinCore. So, he could fork the code and create, say "Bitcoin20", and advise all BitcoinCore users that they need to upgrade to Bitcoin20 (or BitcoinXT). I really hope it does not come to that.
He has consulted many stakeholders and indications are that major miners, exchanges, wallet providers, 3rd party services, and BitcoinXT will be on-board with the change. Those that want to see how 1MB affects fees might get their wish, because March 2016 is a fair way off and there may be long periods of nearly-full 1MB blocks. The resulting problems for ordinary users will create an avalanche of demand for the 20MB change, or Bitcoin20, if that is what it takes.
It is worth repeating: just because the max block size increases does not mean the blocks immediately get bigger. The 1st 20MB block may be 5 years away.
edit: the last point about future limit changes. Yes, other hard-forks may be necessary, however, 20MB is large enough that it buys time for alternative scaling methods to be fully developed and implemented, such as the Lightning Networks.