j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMí<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1332.msg14925#msg14925">Quote from: Anonymous on October 02, 2010, 12:46:14 AM</a></div><div class="quote">How many Ghash's do you think Google would do if it started to generate?<br/><br/></div><br/>Probably all of them, but difference would it make? Even if they are willing to commit the full brunt of their computing resources to overtake the generation of new coins, they can't make them faster than the difficulty system would permit. At least not for more than two weeks. Nor can they do anything to manipulate the value of the coins already in existance, beyond the effects of the regular generation awards. That's the beauty of the design, even Google couldn't do more than disrupt the system temporarily. Even at this early stage, the total proof-of-work represents a supercomputing class cluster. For what gain would anyone do such a thing? For a max return of 50K coins over two weeks of supercomputing time? Even Google doesn't have the computing power to rebuild the blockchain from the beginning. Even if they did, to what end? To steal a quarter million dollars in wealth? Which would likely collapse the system if it could be done at all, so that value would drop to zero. As we have seen, that difficulty level increases as the user base increases, regardless of an analysis as to the economics of each person generating.<br/><br/>I can accept that, however unlikely, a takeover of the system is possible; but if such a thing were to happen, it certainly wouldn't go unnoticed by the Bitcoin community. From where I stand, the odds that the Federal Reserve will cease to exist and the FRN collapse is more likely to occur first. For that matter, I would consider a worldwide extinction-level-event to be about as likely; but I'm not going to let the risks of a meteor strike stop me from walking out on the surface of the Earth. </div> text/html
https://whatsonchain.com/tx/1972d79041f96f1cf3d7e17cf6c5a0d27a2134ef069fd39b78cd6a7c8bbcb585