Post
Topic
Board Development & Technical Discussion
Re: Bitcoin XT code enabling bigger blocks
by
iCEBREAKER
on 05/07/2015, 11:19:34 UTC
A soft fork adds limitations that make previously-valid blocks invalid, so miners who aren't enforcing _any_ limitations are effectively on the "didn't upgrade" side. But a hard fork makes blocks that were previously invalid valid, so if 75% are advertising big-block support but some miners who haven't advertised that aren't validating at all, you'll actually have more than 75% mining the big-block main chain.

PS. In reality you'll have much more than 75% advertising big-block support once the switch-over comes (if it ever does) because most miners will upgrade during the 2-week grace period rather than be left mining dead coins.

PPS. After losing money this way I doubt many miners will continue running with verification completely switched off; They have much better alternatives either by getting blocks propagated faster and mining normally or by at least verifying in parallel and giving up trying to mine on top of blocks once they've found that they're invalid.

Fair enough, but don't forget MPEX, etc. plan to sabotage any attempt to raise max_blocksize.  IE, they will falsely advertise >1MB compliance in order to (prematurely) bait the hard fork into a prearranged GavinCoin Short kill box.

As for losing money on invalid blocks, only the pool ops know exactly what strategy they're using and whether or not 'loss leader' invalid blocks are ultimately in the aggregate profitable.