RAM hashing in blockchain environments
Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.
1. A proof-of-work method by a miner system in a blockchain environment, the miner system including (a) a database table and (b) a hardware processor, the proof-of-work method comprising the steps of:
(i) utilizing a hashing algorithm, generating a hash value based on a blockchain transaction data;
(ii) identifying a location in the database table corresponding to a random value;
(iii) obtaining a table entry at the identified location;
(iv) utilizing a bit replacement operation, generating a randomized hash value using the obtained table entry; and
(v) producing a proof-of-work output based on the randomized hash value;
wherein a time delay in producing the proof-of-work output is based mostly on the hardware processor incurring an at least one cache miss.
2. The proof-of-work method of claim 1 , further comprising:
repeating steps (ii) though (iv) a predetermined number of additional cycles prior to executing step (v), wherein the generated randomized hash value used in step (v) is the randomized hash value that is generated during step (iv) of the last cycle of the predetermined number of additional cycles.
3. The proof-of-work method of claim 2 , wherein the random value in step (ii) of an initial cycle is determined using the generated hash value, and
wherein the random value in step (ii) of each additional cycle is determined using an at least one of:
(a) the randomized hash value generated during the immediately prior cycle; and
(b) the location, in the database table, identified during the immediately prior cycle.
4. The proof-of-work method of claim 2 , further comprising repeating steps (i) through (iv) if the generated randomized hash value does not meet a predetermined criterion.
5. The proof-of-work method of claim 1 , wherein the hashing algorithm comprises a SHA-256 encryption algorithm.
6. The proof-of-work method of claim 1 , wherein step (v) comprises calculating a predetermined criterion using a difficulty algorithm.
7. The method of claim 1 , wherein step (iv) comprises a bit manipulation operation.
8. A miner system associated with a blockchain environment, the miner system comprising a database table and a hardware processor,
the miner system storing instructions that, when executed by the hardware processor, perform operations comprising:
(i) utilizing a hashing algorithm, generating a hash value based on a blockchain transaction data;
(ii) identifying a location in the database table corresponding to a random value;
(iii) obtaining a table entry at the identified location;
(iv) utilizing a bit replacement operation, generating a randomized hash value using the obtained table entry; and
(v) generating a proof-of-work output based on the generated randomized hash value;
wherein a time delay in generating the proof-of-work output is based mostly on the hardware processor incurring an at least one cache miss.
9. The miner system of claim 8 , further comprising instructions repeating operations (ii) though (iv) for a predetermined number of additional cycles prior to operation (v), and wherein the generated randomized hash value used in operation (v) is the randomized hash value that is generated during operation (iv) of the last cycle of the predetermined number of additional cycles.
10. The miner system of claim 9 , wherein the random value in operation (ii) of an initial cycle is determined using the generated hash value, and wherein the random value in operation (ii) of each additional cycle is determined using an at least one of:
(a) the randomized hash value generated during the immediately prior cycle; and
(b) the location, in the database table, identified during the immediately prior cycle.
11. The miner system of claim 9 , further comprising instructions repeating operations (i) through (iv) if the generated randomized hash value does not meet a predetermined criterion.
12. The miner system of claim 8 , wherein the hashing algorithm comprises a SHA-256 encryption algorithm.
13. The miner system of claim 8 , wherein operation (v) comprises calculating a predetermined criterion using a difficulty algorithm.
14. The miner system of claim 8 , wherein operation (iv) comprises a bit manipulation operation.
15. A memory structure comprising (a) a cache memory in a hardware processor and (b) a non-cache memory, the memory structure storing instructions that, when executed by the hardware processor, perform operations that mine a blockchain block associated with a blockchain environment, the operations comprising:
(i) utilizing a hashing algorithm, generating a hash value based on a blockchain transaction data;
(ii) identifying a location in a database table corresponding to a random value, the database table being larger in size than the cache memory and comprising a set of randomly distributed table entries;
(iii) obtaining a table entry at the identified location;
(iv) utilizing a bit replacement operation, generating a randomized hash value using the obtained table entry; and
(v) generating a proof-of-work output based on the generated randomized hash value;
wherein a time delay in generating the proof-of-work output is based mostly on the hardware processor incurring an at least one cache miss.
16. The memory structure of claim 15 , further comprising instructions repeating operations (ii) through (iv) for a predetermined number of additional cycles prior to operation (v), and wherein the generated randomized hash value used in operation (v) is the randomized hash value that is generated during operation (iv) of the last cycle of the predetermined number of additional cycles.
17. The memory structure of claim 16 , wherein the random value in operation (ii) of an initial cycle is determined using the generated hash value, and wherein the random value in operation (ii) of each additional cycle is determined using an at least one of:
(a) the randomized hash value generated during the immediately prior cycle; and
(b) the location, in the database table, identified during the immediately prior cycle.
18. The memory structure of claim 16 , further comprising instructions repeating operations (i) through (iv) if the generated randomized hash value does not meet a predetermined criterion.
19. The memory structure of claim 15 , wherein the hashing algorithm comprises a SHA-256 encryption algorithm.
20. The memory structure of claim 15 , wherein operation (v) comprises calculating a predetermined criterion using a difficulty algorithm.
21. The memory structure of claim 15 , wherein operation (iv) comprises a bit manipulation operation.