Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I've tried keyhunt random on CPU very slow.
And cubitcrack counting random ranges I give it time to time gave me about 10x speed of keyhunt, but without the random option, I don't like it.
I've tried to find any relation or pattern between the previous puzzles and got absolutely nothing!
I'd like to have that random option on GPU! is there any tool for that please?
Good thing I've learned some Python and found it's actually slow
I started to learn C++ and CUDA hopefully to create a better tool, is there any libraries you can recommend to work with?
Looking at the puzzles that are still unsolved and how big those ranges are! there's no way in our life time! But it's fun to play!
And cubitcrack counting random ranges I give it time to time gave me about 10x speed of keyhunt, but without the random option, I don't like it.
I've tried to find any relation or pattern between the previous puzzles and got absolutely nothing!
I'd like to have that random option on GPU! is there any tool for that please?
Good thing I've learned some Python and found it's actually slow
I started to learn C++ and CUDA hopefully to create a better tool, is there any libraries you can recommend to work with?
Looking at the puzzles that are still unsolved and how big those ranges are! there's no way in our life time! But it's fun to play!
vanbitcracken2 or KeyHuntCuda
but mind you, random option resets your chance to 100 times the initial time to find the key you are looking for withing the specified 66 bit range
for example
If it'd take you 300 years to scan the range
expect 30,000 years on a random search and you will still not stand the chance either, except you're able to program the random to note the range it had already scanned which is impossible because why would it be called random then?
rrandom option is the least thought anyone should be thinking about right now
only except you'd want to scan a specific 50 bit range randomly which you'd have to not down just like the puzzle 66 pool.
so if you want to consent to Random search for the puzzle 66
It's best to resort to the specific bit range search where you'd have to note every defeated range in order for you not to multiscan the range you've already scanned