Quote from: sunnyprince on July 04, 2014, 06:53:10 PM

I'm in the final stages of testing the wallet RAM fix. It will be a non-forking change, but I encourage everybody to update their nodes as soon as possible. The github will be updated in a few hours.

The solution I found is to assign a hash-signing private key. The node who owns this key verifies that the ramhog hash for a particular block is accurate, and then signs it. Any node that trusts that key uses the signed hash instead of computing it itself. All nodes propagate these signed hashes so that they are easily accessible. The result will be that anybody can run a wallet without needing to run the ramhog algorithm. This will also make sync times near-instant. For the security of the network, I suggest that those who have the RAM not use the signed hashes, or perhaps only use them to sync and then let their wallet verify all the hashes itself.

I will also hard-coded the genesis block info and the seed nodes in the OP and set the default to not run any ramhogthreads, so the average user can just download and run the binary without needing a special computer. These nodes still fully validate all transactions as usual. The only difference is they don't compute the proof-of-work hash themselves.

Laxori666, instacash, could you please recompile the Windows and Mac wallets once the source is posted?

Awesome work. So only if ramhogthreads=0, it will use the signed hashes?