Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
yes your scanning litterly trillions of page data but are you not also trying trillions of key combos in brute force 
?? all im saying is that using brute force you guessing randomly a 17 digit code. my way your scanning a 17 digit code looking for the last letter error or skipped character in sequence. id say your odds at finding one random character and guessing the whole 17 digit code is ,much easier.
If you dont believe me just do what i said gto look everything up its all there except for non cracked keys every other page is in order no skipped lines eventually on some pages finding in the list the other puzzles that were solved. again theres no way possible those keys were added to that list with a gab being there litterly no possible way. even though they arent say what your saying is true. there is no data base that holds all keys. then how is puzzle #65 found on page 509472955201070048 there had to be a skip in the keys to fill the gap. if not you could just go use CTRL F search the entire webpage data base for a p2pkh address if you type 66 its nothing found if you type any cracked puzzles p2pkh itll go to that page. if someone wants to talk over discord and i can computer screen share for a group thatd be alot easier than typing it out my discord is Otw2f#9888
You really do not understand how those sites work.?? all im saying is that using brute force you guessing randomly a 17 digit code. my way your scanning a 17 digit code looking for the last letter error or skipped character in sequence. id say your odds at finding one random character and guessing the whole 17 digit code is ,much easier.If you dont believe me just do what i said gto look everything up its all there except for non cracked keys every other page is in order no skipped lines eventually on some pages finding in the list the other puzzles that were solved. again theres no way possible those keys were added to that list with a gab being there litterly no possible way. even though they arent say what your saying is true. there is no data base that holds all keys. then how is puzzle #65 found on page 509472955201070048
there had to be a skip in the keys to fill the gap. if not you could just go use CTRL F search the entire webpage data base for a p2pkh address if you type 66 its nothing found if you type any cracked puzzles p2pkh itll go to that page. if someone wants to talk over discord and i can computer screen share for a group thatd be alot easier than typing it out my discord is Otw2f#9888We have tried explaining it to you.
The reason 65 is there, is because the site put it there.
If there are 1 million keys (keep it small); and each page contains 100 keys. And a puzzle/challenge key had a private key of 23212; then I know it's on page 232. I can then simply go there in my html file and update that page.
Every time you click on a page, the site uses your CPU to fill in that page via privkey, pubkey, rmd160, all the way to pubaddress.
It's all good. I wish you luck in your endeavor!
this is a small fraction of the list that the page #65 was found on but if from page 1 the key start at 2^1 bit and goes up in range starting at 0-9 then a-f once reaching 0 again it goes up 1bit? am i wrong here ? no im not you can clearly see if you looked at the website. for puzzle #65 to be added in there it had to not be there in the first place am i right or wrong again? if its not there you could simply do what ive been saying find the skipped key and input it.
000000000000000000000000000000000000000000000001a838b13505b26864
000000000000000000000000000000000000000000000001a838b13505b26865
000000000000000000000000000000000000000000000001a838b13505b26866
000000000000000000000000000000000000000000000001a838b13505b26867 this is #65 key
000000000000000000000000000000000000000000000001a838b13505b26868
000000000000000000000000000000000000000000000001a838b13505b26869
000000000000000000000000000000000000000000000001a838b13505b26864
000000000000000000000000000000000000000000000001a838b13505b26865
000000000000000000000000000000000000000000000001a838b13505b26866
000000000000000000000000000000000000000000000001a838b13505b26867 #65s private key had to be missing right before it was cracked so we would take the key before take the ending character off and add the missing one which was 7.
000000000000000000000000000000000000000000000001a838b13505b26868
000000000000000000000000000000000000000000000001a838b13505b26869