Separating hashing from proof-of-work 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 in a blockchain environment, the method comprising:
receiving, by a computer having a hardware processor, a proof-of-work target scheme associated with the blockchain environment;
using an electronic data, generating by the computer a hash value via a hashing algorithm, wherein the electronic data comprises at least one blockchain transaction; and
using the hash value as an input to a proof-of-work algorithm, executing by the computer the proof-of-work algorithm to generate a proof-of-work result,
wherein a time delay in generating the proof-of-work result is achieved mostly by the proof-of-work algorithm causing a cache miss.
2. The method of claim 1 , further comprising the step of determining whether the proof-of-work result satisfies the proof-of-work target scheme.
3. The method of claim 1 , wherein the step of executing the proof-of-work algorithm comprises using a database table that exceeds a storage capacity of a cache memory of the hardware processor.
4. The method of claim 3 , wherein the step of using a database table comprises (i) identifying a location in the database table corresponding to a random value, and (ii) obtaining a table entry at the identified location.
5. The method of claim 4 , wherein the step of executing a proof-of-work algorithm comprises generating a randomized hash value using the obtained table entry.
6. The method of claim 5 , wherein the step of generating a randomized hash value using the obtained table entry comprises a bit manipulation operation.
7. The method of claim 4 , further comprising repeating the step of using a database table a predetermined number of cycles.
8. The method of claim 1 , further comprising generating a difficulty value by executing a difficulty algorithm.
9. A miner system in a blockchain environment, the miner system comprising:
a hardware processor; and
a memory device storing instructions that, when executed by the hardware processor, perform operations comprising:
receiving a proof-of-work target scheme associated with the blockchain environment;
using an electronic data, generating a hash value via a hashing algorithm, wherein the electronic data comprises at least one blockchain transaction; and
using the hash value as an input to a proof-of-work algorithm, executing the proof-of-work algorithm to generate a proof-of-work result,
wherein a time delay in generating the proof-of-work result is achieved mostly by the proof-of-work algorithm causing a cache miss.
10. The miner system of claim 9 , wherein the operations further comprise determining whether the proof-of-work result satisfies the proof-of-work target scheme.
11. The miner system of claim 9 , wherein the operation of executing the proof-of-work algorithm comprises using a database table that exceeds a storage capacity of a cache memory of the hardware processor.
12. The miner system of claim 11 , wherein the using a database table comprises (i) identifying a location in the database table corresponding to a random value, and (ii) obtaining a table entry at the identified location.
13. The miner system of claim 12 , wherein the operation of executing a proof-of-work algorithm comprises generating a randomized hash value using the obtained table entry.
14. The miner system of claim 13 , wherein the generating a randomized hash value using the obtained table entry comprises a bit manipulation operation.
15. The miner system of claim 12 , further comprising repeating the operation of using a database table a predetermined number of cycles.
16. A non-transitory memory storing instructions that, when executed by a hardware processor, perform operations comprising:
receiving a proof-of-work target scheme associated with a blockchain environment;
using an electronic data, generating a hash value via a hashing algorithm, wherein the electronic data comprises at least one blockchain transaction; and
using the hash value as an input to a proof-of-work algorithm, executing the proof-of-work algorithm to generate a proof-of-work result,
wherein a time delay in generating the proof-of-work result is achieved mostly by the proof-of-work algorithm causing a cache miss.
17. The non-transitory memory of claim 16 , wherein the operations further comprise determining whether the proof-of-work result satisfies the proof-of-work target scheme.
18. The non-transitory memory of claim 16 , wherein the operation of executing the proof-of-work algorithm comprises using a database table that exceeds a storage capacity of a cache memory of the hardware processor.
19. The non-transitory memory of claim 18 , wherein the using of a database table comprises (i) identifying a location in the database table corresponding to a random value, and (ii) obtaining a table entry at the identified location.
20. The non-transitory memory of claim 19 , wherein the operation of executing a proof-of-work algorithm comprises generating a randomized hash value using the obtained table entry.
21. The non-transitory memory of claim 20 , wherein the generating a randomized hash value using the obtained table entry comprises a bit manipulation operation.
22. The non-transitory memory of claim 19 , further comprising repeating the operation of using a database table a predetermined number of cycles.