j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1925.msg24623#msg24623">Quote from: bugmenot on November 26, 2010, 12:08:00 PM</a></div><div class="quote">Nice work.<br/><br/>But :<br/><div class="quoteheader">Quote</div><div class="quote">DBG: found zeroes in hash:<br/>6c1e0d9af9b06eab5aae7fbe058760708c1c7869870142b91b9c0ae300000000<br/>PROOF OF WORK FOUND? submitting...<br/>PROOF OF WORK RESULT: false (booooo)<br/>[...]<br/>DBG: found zeroes in hash:<br/>c155613cbd70edad88bf56b06cbd788329a2a741b27ee78f25abdb2e00000000<br/>PROOF OF WORK FOUND? submitting...<br/>PROOF OF WORK RESULT: false (booooo)<br/></div><br/>I don't know if this is a bug or not.<br/>The miner has been compiled with cygwin, I don't know if it matters.<br/></div><br/>Not a bug. The miner finds a hash with "several" zeroes in it, but then relies on bitcoin to do the full 256-bit hash < target value comparison. It's normal that some hashes will be found by the CPU miner, then rejected by bitcoin. We call those almost-solutions <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/></div> text/html
https://whatsonchain.com/tx/488a04d396e52e35c0133e5ebe3e7b9f38ea7f1db738b5f27cd6fd4d515d853d