Quote from: bible_pay on March 19, 2019, 12:52:47 AM

Quote from: thesnat21 on March 19, 2019, 12:39:14 AM

Quote from: bible_pay on March 19, 2019, 12:24:33 AM

Quote from: secoccular on March 18, 2019, 11:59:51 PM

My money is on thesnat21 to be able to make a GPU miner for BBP. He solved the riddle of the BLE headers and made a GPU for that.

TheSnat, can you execute the AES512 encryption algorithm in your GPU miner and can you load the full KJV bible into its memory and duplicate the chaincalls?

What if I up the reward to 3 MM bbp?

oy, I was not going to worry about it ... lol i smell a conspiracy

Just take a look at the BibleHash algo and how much estimated memory it would take to load the KJV array in the GPU executing environment (this is from kjv.cpp), and tell is if you believe its technically possible to duplicate the chained bible hash calls, the AES512 call, the hash call and the concatenated result call in a GPU. And how secure or not secure you feel that someone will figure it out knowing what you know about c libraries and GPU code programming.

Im not too worried about ASIC, I heard they have such limited memory that loading the bible in it would be preposterous also you need a specific designed chip with the bible that would cost a lot of R&D for the first batch.

Edit: btw guys when you execute one biblehash, it uses 33,000 verses of the bible in a certain hashed order (depending on each hash its different). IE its memory intensive since the entire bible is memorized.

ah, so "memorizing prayers" while the wallet is loading means that the whole bible is being stored into RAM?