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 method by a miner system in a blockchain environment, the miner system including (i) a database table including a set of randomly distributed table entries, and (ii) a hardware processor including a cache memory that is smaller in size than the database table, the method comprising the steps of:
(A) receiving a blockchain transaction data; and
(B) performing a proof-of-work algorithm comprising:
(i) obtaining a nonce;
(ii) using a hashing algorithm, generating a hash value based on the received blockchain transaction data and on the obtained nonce;
(iii) identifying a location in the database table corresponding to a random value;
(iv) obtaining a table entry at the identified location;
(v) generating a randomized hash value using the obtained table entry; and
(vi) producing a proof-of-work output if the generated randomized hash value meets a predetermined criterion;
wherein a time delay in arriving at the proof-of-work output is based mostly on the hardware processor incurring an at least one cache miss.
2. The method of claim 1 , wherein the step of performing a proof-or-work algorithm comprises repeating steps (B)(iii) through (B)(v) a predetermined number of additional cycles prior to executing step (B)(vi), and wherein the generated randomized hash value used in step (B)(vi) is the randomized hash value that is generated during step (B)(v) of the last cycle of the predetermined number of additional cycles.
3. The method of claim 2 , wherein the random value in step (B)(iii) of an initial cycle is determined using the generated hash value, and wherein the random value in step (B)(iii) 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 method of claim 2 , further comprising repeating steps B(i) through (B)(v) if the generated randomized hash value does not meet the predetermined criterion in step (B)(vi).
5. The method of claim 1 , wherein the hashing algorithm comprises a SHA-256 encryption algorithm.
6. The method of claim 1 , wherein step (B)(vi) comprises calculating the predetermined criterion using a difficulty algorithm.
7. The method of claim 1 , wherein step (B)(v) comprises a bit manipulation operation.
8. A miner system associated with a blockchain environment, the miner system comprising a database table including a set of randomly distributed table entries and
a hardware processor with a cache memory that is smaller in size than the database table,
the miner system storing instructions that, when executed by the hardware processor, perform operations comprising:
(A) receiving a blockchain transaction data; and
(B) performing a proof-of-work algorithm comprising:
(i) obtaining a nonce;
(ii) using a hashing algorithm, generating a hash value based on the received blockchain transaction data and on the obtained nonce;
(iii) identifying a location in the database table corresponding to a random value;
(iv) obtaining a table entry at the identified location;
(v) generating a randomized hash value using the obtained table entry; and
(vi) generating a proof-of-work output if the generated randomized hash value meets a predetermined criterion;
wherein a time delay in arriving at 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 (B)(iii) through (B)(v) for a predetermined number of additional cycles prior to operation (B)(vi), and wherein the generated randomized hash value used in operation (B)(vi) is the randomized hash value that is generated during operation (B)(v) of the last cycle of the predetermined number of additional cycles.
10. The miner system of claim 9 , wherein the random value in operation (B)(iii) of an initial cycle is determined using the generated hash value, and wherein the random value in operation (B)(iii) 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 B(i) through (B)(v) if the generated randomized hash value does not meet the predetermined criterion in operation (B)(vi).
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 (B)(vi) comprises calculating the predetermined criterion using a difficulty algorithm.
14. The miner system of claim 8 , wherein operation (B)(v) comprises a bit manipulation operation.
15. A memory structure comprising (i) a cache memory in a hardware processor and (ii) 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:
(A) receiving a blockchain transaction data; and
(B) performing a proof-of-work algorithm comprising:
(i) obtaining a nonce;
(ii) using a hashing algorithm, generating a hash value based on the received blockchain transaction data and on the obtained nonce;
(iii) 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;
(iv) obtaining a table entry at the identified location;
(v) generating a randomized hash value using the obtained table entry; and
(vi) generating a proof-of-work output if the generated randomized hash value meets a predetermined criterion;
wherein a time delay in arriving at 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 (B)(iii) through (B)(v) for a predetermined number of additional cycles prior to operation (B)(vi), and wherein the generated randomized hash value used in operation (B)(vi) is the randomized hash value that is generated during operation (B)(v) of the last cycle of the predetermined number of additional cycles.
17. The memory structure of claim 16 , wherein the random value in operation (B)(iii) of an initial cycle is determined using the generated hash value, and wherein the random value in operation (B)(iii) 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 B(i) through (B)(v) if the generated randomized hash value does not meet the predetermined criterion in operation (B)(vi).
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 (B)(vi) comprises calculating the predetermined criterion using a difficulty algorithm.
21. The memory structure of claim 15 , wherein operation (B)(v) comprises a bit manipulation operation.