|
Title: Why people keep recomputing hashes? Post by: pornluver on May 21, 2013, 10:55:38 AM Huge amount of CPU power is in the hash.
Why not store all computed hashes in databases and see if one match up? What am I missing? In fact every nonce is probably computed again and again and again.... So why not store it for future uses? Title: Re: Why people keep recomputing hashes? Post by: os2sam on May 21, 2013, 11:03:10 AM Who is hashing with CPU? Botnets.
If a hash doesn't meet or exceed the current difficulty why store for later when the difficulty is even higher? Title: Re: Why people keep recomputing hashes? Post by: crazyates on May 21, 2013, 01:47:04 PM Try reading this little article: https://en.bitcoin.it/wiki/Block_hashing_algorithm
The nonce is not the only thing that changes. There are actually 6 "parts" that get grouped together and hashed, and the nonce range is only one of those. The other 5 all get updated at different intervals, but it's designed so that we're never working on the same work twice. Ever. Also, see Here (https://en.wikipedia.org/wiki/SHA-2#Examples_of_SHA-2_variants). I like the way they worded it: "Even a small change in the message will result in a mostly different hash, due to the avalanche effect." You can see their examples in the wiki article that illustrate this point. Title: Re: Why people keep recomputing hashes? Post by: GenTarkin on May 24, 2013, 05:59:07 AM yeah, to put quite simply... there is no "might get used again"
plus making a database that huge... yeah, no... lol |