Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
WanderingPhilospher
on 17/01/2024, 13:50:39 UTC
Hello, I tried to calculate (using AI help) and I get that at 48 exa keys per second the range will be completed shortly. Where is the mistake?

(2^130 - 1) - 2^129

2^130 is 340282366920938463463374607431768211456

Subtracting 1 gives us:

340282366920938463463374607431768211455

2^129 is 170141183460469231731687303715884105728

Subtracting the start from the end:

340282366920938463463374607431768211455 - 170141183460469231731687303715884105728

= 170,141,183,460,469,231,731,687,303,715,884,105,727

Total keys / Keys scanned per second

170,141,183,460,469,231,731,687,303,715,884,105,727 / 48,000,000,000,000,000,000

= 3,542 seconds


Bsgs is now holding 18 exa keys/s stable.

Running a program to searches 18 exa keys/s is impressive!

I have 16 GB and Core i7, and get only 70 Peta key/s  

18 ExKeys/s this is a drop in the ocean, the range is huge, brute force is currently not the best choice for solving the puzzle. Even if random is not a very good idea, you need to look for another approach

P.s.


Your calculator is broke lol.

(2^129/48000000000000000000) / 86400 (seconds in one day) = 164,102,221,701,841 days to scan entire range.

Also, 2^129 = 680564733841876926926749214863536422912, not 170141183460469231731687303715884105727 as you stated.

But even with your numbers:

(170141183460469231731687303715884105728/48000000000000000000) / 86400 = 41,025,555,425,460 days.