So I should receive my 2 x GiantN in a few hours (according to the courier). I will report back. I do have a question about the Monero fork though. We know from the X10 reverse engineering thread that even X10's shipped in November have references to the Giant-N and cryptonight in their code, so it is fair to assume Baikal has been hashing cryptonight since November. Now what would YOU do if you were baikal, facing the hard fork? We know the X10 is ASIC's, not FPGA's, we don't know about the Giant-N (yet; I might take it apart), but assuming the Giant-N is ASIC, then the obvious thing for Baikal to do would be to switch all their (hundreds) of Giant-N machines to Monero (off of all other cryptonight coins), and set up some master nodes and gain 51% of the network hash rate. Then, when the fork happens, the fork fails because the V7 algorithm doesn't have 51% of the hash rate. Am I missing something here? I mean the fact that Bitmain doesn't even know the exact hash rate or power consumption of their X3 means it isn't even online yet, so it is fair to assume Baikal is the only company capable of attacking the V7 fork with real hardware. At the current Monero net hash rate it would take Baikal 21,880 Giant-N machines to gain 51% of the hashrate-- assuming not a single of their Giant-N are already hashing Monero. Perhaps that's unrealistic.
- A 51% attack will not prevent the hardfork fork. A 51% attack could attempt to alter the chain before the fork creating some issues. Either way the old chain is still going to be alive, so ASIC miners can continue on it. However, there will be no one to sell to, and no exchanges supporting the old chain( I assume). No community consensus. The majority of the Monero community don't just "dislike" ASICs and Bitmain, they "hate" them. It's War.
- Don't assume just because Bitmain haven't released exact hash rates/ power consumption that there x3 isn't online yet! That probably just means there are firmware updates to come before the public release.