Yeah, I think I'm out. The problem is I didn't even think about brute force tools. Last puzzle I spent hours and hours on, and I think I screwed myself because when I couldn't get the last clues (and it was not too easy. If only $50 is up for grabs, 5 hours is max one could spend on it) I came here as you see and made the huge mistake of posting this: SETL54M6YT5Q7MUVL?DQ??LT3G3B9 It wasn't long after that the money was taken and not a word about it. Why? Easy... the person that took the btc did no work other than put my hard work into a brute force tool and take what I had worked on away from me. So, if I ever do decide to take a look, I won't post here and honestly, it just frustrates me that a brute force tool can be used. Maybe you could have people submit the password in a comment and allow each person 5 guesses or something. I'm not wasting another 5 hours so some ass clown who can write a script can just let his computer solve it for them
I get your frustration. However, a brute force tool is only going to buy you a few characters.
Plus the prize isn't the only reason. This is supposed to be fun...
A bruce force tool isn't bad...
It is just the equivalent of your lifelines in Who wants to be a millionaire.
Answer 24 , get 6 answered for you
Exactly. However, you've got to be pretty sure the answers you've got are right, otherwise you're wasting time brute forcing the wrong key!
I don't know how much time it would take to guess each one, though I'd think that ~6 characters was worthwhile. I don't know whether hashing is the right analogy or not. You've got to convert the key to the address, which I think is a more complex function than a hash (someone correct me here?), then check it against the known address.
Regardless, other episodes won't be so amenable to brute forcing.
Well , my analogy is done to the speed taken to generate a vanity address.
This generates using random private keys , and can create 10 million addresses per second ( atleast on average ).
The program maintains this speed , while also checking if the key corresponds to the specified vanity address.
The same program will need to be applied but instead of specifying the first few digits , you would need to specify the entire address and part of the hash.
I calculated 6 characters would take 1.5 minutes , so even if an answer was wrong , you are set back only one minute.
By the way , these timings mentioned are those needed to uncover all possible private keys with a certain number of characters missing.
It should take on average half as long.