Quote from: Ovixx on June 28, 2024, 02:43:14 PM

I tried with an older version keyhunt, compiled for windows, in two instances simultaneously but it is limited to k=4096. 8192 gives me an error.

Code:

c:\Crypto\keyhunt-win-main\keyhunt-win-main>keyhunt.exe -t 4 -m bsgs -f tests/130.txt -r 200000000000000000000000000000000:2ffffffffffffffffffffffffffffffff -q -s 10 -S -k 4096 -R
[+] Version 0.2.211222 SSE Server Edition ,modify Dusky Kam 3,compiled by @XopMC for t.me/brythbit, developed by AlbertoBSD, developed by AlbertoBSD
[+] Threads : 4
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] K factor 4096
[+] Random mode
[+] Mode BSGS random
[+] Opening file tests/130.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x200000000000000000000000000000000
[+] -- to : 0x2ffffffffffffffffffffffffffffffff
[+] N = 0x100000000000
[+] Bloom filter for 17179869184 elements : 58890.60 MB
[+] Bloom filter for 536870912 elements : 1840.33 MB
[+] Bloom filter for 16777216 elements : 57.51 MB
[+] Allocating 256.00 MB for 16777216 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_4_17179869184.blm .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_6_536870912.blm .... Done!
[+] Reading bP Table from file keyhunt_bsgs_2_16777216.tbl .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_7_16777216.blm .... Done!
[+] Total 293337334983847575552 keys in 1430 seconds: ~205 PetaKeys/s (205131003485208094 keys/s)

Code:

[+] Bloom filter for 34359738368 elements 0 [main] keyhunt 1032 cygwin_exception::open_stackdumpfile: Dumping stack trace to keyhunt.exe.stackdump

c:\Crypto\keyhunt-win-main\keyhunt-win-main>keyhunt.exe -t 4 -m bsgs -f tests/130.txt -r 300000000000000000000000000000000:3ffffffffffffffffffffffffffffffff -q -s 10 -S -k 4096 -R
[+] Version 0.2.211222 SSE Server Edition ,modify Dusky Kam 3,compiled by @XopMC for t.me/brythbit, developed by AlbertoBSD, developed by AlbertoBSD
[+] Threads : 4
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] K factor 4096
[+] Random mode
[+] Mode BSGS random
[+] Opening file tests/130.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x300000000000000000000000000000000
[+] -- to : 0x3ffffffffffffffffffffffffffffffff
[+] N = 0x100000000000
[+] Bloom filter for 17179869184 elements : 58890.60 MB
[+] Bloom filter for 536870912 elements : 1840.33 MB
[+] Bloom filter for 16777216 elements : 57.51 MB
[+] Allocating 256.00 MB for 16777216 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_4_17179869184.blm .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_6_536870912.blm .... Done!
[+] Reading bP Table from file keyhunt_bsgs_2_16777216.tbl .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_7_16777216.blm .... Done!
[+] Total 240737507951601778688 keys in 1190 seconds: ~202 PetaKeys/s (202300426850085528 keys/s)

The problem is that it has raised the CPU to 104 degrees Celsius.

Ovixx, here is what I'm getting with Keyhunt, 96GB DDR5 RAM and i7-14900F (8 Pcores, 12 Ecores, 28 threads):

Code:

./keyhunt -m bsgs -f tests/130.txt -b 130 -l compress -s 1 -t 28 -R -k 2048 -S
[+] Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
[+] Search compress only
[+] Stats output every 1 seconds
[+] Threads : 28
[+] Random mode
[+] K factor 2048
[+] Mode BSGS random
[+] Opening file tests/130.txt
[+] Added 1 points from file
[+] Bit Range 130
[+] -- from : 0x200000000000000000000000000000000
[+] -- to : 0x400000000000000000000000000000000
[+] N = 0x100000000000
[+] Bloom filter for 8589934592 elements : 29445.30 MB
[+] Bloom filter for 268435456 elements : 920.17 MB
[+] Bloom filter for 8388608 elements : 28.76 MB
[+] Allocating 128.00 MB for 8388608 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_4_8589934592.blm .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_6_268435456.blm .... Done!
[+] Reading bP Table from file keyhunt_bsgs_2_8388608.tbl .... Done!
[+] Reading bloom filter from file keyhunt_bsgs_7_8388608.blm .... Done!
[+] Thread 0x36d5aa497e15200fb15197db5c2416eaa Total 906491569871551201280 keys in 399 seconds: ~2 Ekeys/s (2271908696419927822 keys/s)

If you're running Keyhunt in a WSL terminal on Windows, remember to create a file named [Suspicious link removed]lconfig" in your C:\Users\Currentuser folder that contains:

Code:

[wsl2]
memory=96GB

In my case, memory=96GB but replace that with your system RAM value i.e. memory=192GB

Also, use Task Manager to watch how much memory is being consumed. If you go over 100% the system will start using your SSD as virtual RAM, which will make the program run very slow (and wear your SSD). For me, my max k value is 2048, if I go to k=4096, it exceeds my available RAM and actually runs slower than with k=2048.

Use Intel Extreme Tuning Utility to adjust the wattage your CPU runs at to keep it cooler, or upgrade your cooler. My i7-14700F can run at 150 watts continuously and never goes above 75C, with liquid cooler installed.

On vast I rented a system to mess around with different settings. The best I got was this, but it took 7 hours just to make the bloom filter (part of the output got lost when I had to refresh webpage terminal):

System specs:
Xeon® E7-8890 v4
48.0/192 cpu
501/564 GB

Code:

root@C.11278182:/app/keyhunt$ ./keyhunt -m bsgs -f tests/130.txt -b 130 -l compress -R -s 1 -t 96 -k 256 -n 0x400000000000000

[+] processing 137438953472/137438953472 bP points : 100%
[+] Making checkums .. ... done
[+] Sorting 134217728 elements... Done!
[+] Thread 0x2a99f4e4b2a3493b4c5a136c294e120ee Total 38794655708515793895424 keys in 1635 seconds: ~23 Ekeys/s (23727618170346051312 keys/s)

There are some higher end systems you can rent with 1TB+ of RAM but they're expensive. But while you're waiting for Keyhunt to make the bloom filters, you can run something else on the GPU's at the same time.