Exploring Probabilistic Prefix Search in Crypto

22 replies 326 views
m1kes4tFull Member
Posts: 167 · Reputation: 252
#1Jan 3, 2022, 06:44 PM
This method revolves around calculating the chances of a specific prefix showing up in a set of hashes, while ignoring the less likely outcomes.
2 Reply Quote Share
diamond51Senior Member
Posts: 3 · Reputation: 850
#2Jan 3, 2022, 11:28 PM
So how do you determine if that partial match actually indicates the target is in that range?
1 Reply Quote Share
Posts: 18 · Reputation: 209
#3Jan 4, 2022, 01:17 AM
I honestly can't grasp what this code is trying to do or how to utilize it.
4 Reply Quote Share
its_matrixSenior Member
Posts: 264 · Reputation: 899
#4Jan 4, 2022, 06:12 AM
Can you show a demo or example?
3 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#5Jan 4, 2022, 08:38 AM
You can't really be sure about anything with probabilistic software. Just because some ranges are less likely doesn’t mean you’ll definitely succeed.
0 Reply Quote Share
diamond51Senior Member
Posts: 3 · Reputation: 850
#6Jan 4, 2022, 02:26 PM
So you’re basically hunting for the hex prefix of the address?
3 Reply Quote Share
falcon2019Full Member
Posts: 90 · Reputation: 425
#7Jan 4, 2022, 07:20 PM
No way, it's super unlikely to find 5 "abcde" prefixes in a 65536 range.
3 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#8Jan 4, 2022, 09:55 PM
Actually, it’s 93.94% likely that you won’t find any "abcde" prefix in that range. So 6.06% is the chance of finding it at least once.
2 Reply Quote Share
Posts: 18 · Reputation: 209
#9Jan 5, 2022, 12:10 AM
What about the claim of 3% you mentioned earlier?
2 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#10Jan 5, 2022, 01:56 AM
Yes, I’m focused on h160 prefixes.
4 Reply Quote Share
falcon2019Full Member
Posts: 90 · Reputation: 425
#11Jan 5, 2022, 02:57 AM
You’re misreading the stats, dude. 3% of 65536 is like 2000. The collisions are way more than just a few. Did you even test the script?
1 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#12Jan 5, 2022, 04:50 AM
I’ve been working on a similar thing for another puzzle... Sometimes had 2000 keys between two "145d" points and at other times, 120k. It varies a lot.
4 Reply Quote Share
falcon2019Full Member
Posts: 90 · Reputation: 425
#13Jan 7, 2022, 11:14 AM
Haven't tried with public keys yet. They’ve got similarities, but they’re not identical to hashes. Testing is key here.
2 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#14Jan 7, 2022, 11:45 AM
Let’s reset things. So you got to 2000 collisions based on your 65537 keys. Is that where the 3% number is from?
3 Reply Quote Share
falcon2019Full Member
Posts: 90 · Reputation: 425
#15Jan 7, 2022, 03:03 PM
That’s not how uniform distribution works. Check your math.
3 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#16Jan 7, 2022, 04:20 PM
You need to rethink the theoretical approach. Prefixes work differently depending on the set of hashes used.
1 Reply Quote Share
falcon2019Full Member
Posts: 90 · Reputation: 425
#17Jan 7, 2022, 10:32 PM
So... what’s the conclusion? Your theory seems solid but show me the proof.
0 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#18Jan 7, 2022, 10:45 PM
My script does track how often prefixes show up. It’s all about the frequency of those appearances compared to what’s expected.
2 Reply Quote Share
dan.walletSenior Member
Posts: 12 · Reputation: 848
#19Jan 7, 2022, 11:25 PM
You're estimating based on your setup. The longer the prefix, the lesser chance of collisions. Are we on the same page?
1 Reply Quote Share
m1kes4tFull Member
Posts: 167 · Reputation: 252
#20Jan 8, 2022, 03:15 AM
That’s not true! My script calculates the frequency of each prefix consistently.
0 Reply Quote Share

Related topics