Based on our previous discussions, does this mean the key is likely between D1xxx and EFxxx? Or could it still be in lowercase?
I also had an idea for filtering:
Skip keys with 4 or more repeating characters, like xxxx, aaaa, bbbb.
Skip keys with 4 or more consecutive sequences, like abcd, 1234.
Skip keys with 4 or more descending sequences, like 4321, 5432.
Skip keys with 3 or more repeating patterns, such as ababab, acacac, 121212, abcabcabc.
Any ideas on how to implement these filters in BitCrack? It might help reduce a lot of unnecessary checks 😅.
No, this Vanity Search does not prove anything, it can be 8 , it can be f
I'm also looking for the same thing, as the so called random is not perfect and have noticed some pattens in other keys.
I can filter out about 91% bs attempts but still have a 90% chance of cracking it, this would still take 256 gpus 4-5 months, so its no easy task and would probably have to team up with someone. I guess you can hire 256 GPU but that would get pricy.
Before anyone says I'm talking bs, my filtering would of worked on about 93% of previous keys. So I have no reason to believe it would not work on either 68 or 69 or 71, one of them worst case I would say.
68 27,000,000,000,000,000,00 With filtering
68 295,147,905,179,352,825,856 Total combinations
But as Wandering kindly pointed out you probably only have to check 50% of your possible guesses till you find the answer. So
68 13,600,000,000,000,000,00 With filtering + like 50% checked around about.
Yeah, I think this is the most realistic approach for now. There’s no solved key that contains patterns like aaaa, bbbb, 1111, or other sequences I mentioned above. But even after reducing the keyspace by 80%, it's still huge.
From the last discussion on this forum about finding similar addresses, I still don’t quite understand—it still looks random to me 😅.