Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMH<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=43.msg541#msg541">Quote from: Suggester on February 26, 2010, 01:35:08 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=43.msg540#msg540">Quote from: satoshi on February 25, 2010, 11:06:29 PM</a></div><div class="quote">I don't know what you're talking about accepting easier difficulties.<br/></div><br/>We were essentially discussing Sabunir's question about what prevents someone from messing with the program's source code to adjust block-generating difficulty to be very easy, then make a network on his own and create a, say, 50,000-block proof-of-work within seconds then finally propagate it across the real network to steal "votes" towards his new fake blocks as technically, his proof would be "the longest". So is there a way to verify how much work was actually put into a given PoW (for eg. how many zero's are at the beginning of each hash or something)?<br/></div><br/>I am also wondering about Suggester's question.&nbsp; It seems like modifying the code to give a node an advantage in generating coins might be possible.<br/><br/>I am confused as to why each node on the network is actually doing when set to generate coins.&nbsp; What problem are they solving that takes 100% CPU?</div> text/html