While dropping to v0.7 was a method to resolve this in a manner which protected v0.7 users it wasn't necessary. Miners could have continued to mine v0.8 chain. Transactions from the v0.7 blocks would be included in v0.8…
Not really. For example if 51% (or even 99.99999999999%) of miners decided they wanted to go back to 50 BTC block reward (or even a new 5,000 BTC block reward) that would simply create an incompatible fork. A fork which…
The fork was at the block level not transaction level. The transactions are on both chains. While they may be in v0.8 blocks and still unconfirmed in the v0.7 fork they do exist in the v0.7 fork. The only transactions…
> If this were an unlucky edge case, I could understand. But it seems like they allowed larger block sizes without testing them on pre v0.8 miners That is not entirely correct. Multiple large blocks were tested on…
While dropping to v0.7 was a method to resolve this in a manner which protected v0.7 users it wasn't necessary. Miners could have continued to mine v0.8 chain. Transactions from the v0.7 blocks would be included in v0.8…
Not really. For example if 51% (or even 99.99999999999%) of miners decided they wanted to go back to 50 BTC block reward (or even a new 5,000 BTC block reward) that would simply create an incompatible fork. A fork which…
The fork was at the block level not transaction level. The transactions are on both chains. While they may be in v0.8 blocks and still unconfirmed in the v0.7 fork they do exist in the v0.7 fork. The only transactions…
> If this were an unlucky edge case, I could understand. But it seems like they allowed larger block sizes without testing them on pre v0.8 miners That is not entirely correct. Multiple large blocks were tested on…