Topic: Keyhunt - development requests - bug reports - page 4. (Read 15202 times)

maybe
-n 0x400000000000 -k 3072

Could you recommend a k and n setting for 96 GB?

That depends of your physical memory also of the Operating system. By the whay don't use k above 4096 without SET the N value, any value 4096 without the correct N will lead on a sub-optimal behavior just like your example

That is on the documentation:

https://github.com/albertobsd/keyhunt?tab=readme-ov-file#what-values-use-according-to-my-current-ram

Hi Alberto, I wanted to share my case:


https://i.ibb.co/JHbWbPx/Screenshot-2024-07-18-100911.png





is it normal that when using less memory the search works faster?

it is a Initial random value and N keys secuentially from that point, where default N is 32 bits value is set with -n example


for 24 bits.
Each thread start with a different point


both are the same but -B options are only for BSGS mode.

Friend, I wanted to understand a little about this -R mode and the -B random mode, would the -R mode be completely random? or does it generate a random initial value and continue sequentially? I have this doubt because from time to time, it prints several random points according to the number of threads, but I don't know if this point would be just demonstrative or if it would be a starting point.

and another question would be what is the difference between -R and -B random mode.

Read the F.... Documentation to know what you need to change to do that



To import it on electrum is its possible conver the privatekey to WIF on
https://www.bitaddress.org/bitaddress.org-v3.3.0-SHA256-dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194.html

Option of Wallet Details, then import on electrum following this post:

https://medium.com/@lindseymiles/importing-your-private-keys-into-electrum-bitcoin-wallet-14071ab26dfe

    the t and cpu single core power mathers

2697v4 128gb ram, i guess double... around 3Ekeys/s

• Bloom filter for 34359738368 elements : 117781.20 MB
• Bloom filter for 1073741824 elements : 3680.66 MB
• Bloom filter for 33554432 elements : 115.02 MB
• Allocating 512.00 MB for 33554432 bP Points
• Reading bloom filter from file keyhunt_bsgs_4_34359738368.blm .... Done!
• Reading bloom filter from file keyhunt_bsgs_6_1073741824.blm .... Done!
• Reading bP Table from file keyhunt_bsgs_2_33554432.tbl .... Done!
• Reading bloom filter from file keyhunt_bsgs_7_33554432.blm .... Done!
• Thread 0x3cdf67df043da02a45f3290d7b3eecb9c  conds: ~1 Ekeys/s (1945754752221815642 keys/s)

3970X 128Gb RAM

+] Making checkums .. ... done

• Sorting 33554432 elements... Done!
• Writing bloom filter to file keyhunt_bsgs_4_34359738368.blm .... Done!
• Writing bloom filter to file keyhunt_bsgs_6_1073741824.blm .... Done!
• Writing bP Table to file keyhunt_bsgs_2_33554432.tbl .. Done!
• Writing bloom filter to file keyhunt_bsgs_7_33554432.blm .... Done!
• Thread 0x38c93b54973c7fbb68df07b81d88b50ee  econds: ~1 Ekeys/s (1529332042058244140 keys/s)

testing right now with

2697v4 512GB RAM
3970X 256GB RAM


is my calculation correct ?

130 bit Key = 2^129 keys = 680,564,733,841,876,926,926,749,214,863,536,422,912 keys ?

680,564,733,841,876,926,926,749,214,863,536,422,912 / 1529332042058244140 keys/s = 445.007.830.298.214.485.823 s = 14.111.105.729.902 years ?

It's like asking on the forum what the weather is like outside, when you can open the door, you go out and convince yourself.

who knows??? 🤷

how mutch hash i can get with e5-2699 v4 and 256 gb ram?

I created the .wslconfig file and put 192GB. I started a court and I see that it reached 25% in 15 minutes with the value k 4096. I hope they will get to the end to save the *.blm file
In parallel I also run Wifsolver-CUDA with a pretty good speed of 4.23 Gkeys/sec.

https://www.talkimg.com/images/2024/07/01/odpk9.jpeg

UPDATE: It doesn't work. It shows me the same error.

Thank you too, I got it in the end


You were right. I ran the command with "sudo" and it saved my blm file.[/list]

---

Yesssss. I upgraded to a liquid cooling system. The best results, within normal parameters.
https://www.talkimg.com/images/2024/07/06/o3PNN.jpeg

@Alberto, I promise you that if I get the private key with the help of your application I will give you the best performing PC on the planet

UPDATE  Over 3 Ekeys/s

https://www.talkimg.com/images/2024/07/06/o3zPT.jpeg

[moderator's note: consecutive posts merged]

C:\Users\\.wslconfig

The contents of the file:

Code:

[wsl2]
#Limits VM memory to use no more than 4 GB, this can be set as whole numbers using GB or MB
memory=192GB

More information:
https://learn.microsoft.com/en-us/windows/wsl/wsl-config

Benjaniah, you're right with the CPU cooling system, I should replace it with a liquid one. Now I have a CPU cooler be quiet! Dark Rock 4 that I received as a gift when I bought the processor but it doesn't manage to cool only half of what it needs. At this point, every 6-7 seconds, the CPU goes into Throttling, meaning it lowers the frequency to lower the temperature below 100 degrees Celsius. Of course, the processing with all 32 cores is also affected.
I don't like the idea of renting server systems at all, that's why I made my own PC to my liking.
With wslconfig I didn't really understand in which folder to make the file, with what name of the folder, of the file and with what extension.
Thanks

https://www.talkimg.com/images/2024/07/01/od6Xo.jpeg

Alberto, do you think the space allocated for WSL would be the problem?

any success stories in getting private keys from public addresses on the btc blockchain ?
would like to hear somebody finally getting actual bitcoins from random address on the blockchain

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


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

This will allow WSL to use the full amount of your system RAM. When I upgraded from 32GB to 96GB of RAM, I couldn't figure out why my Windows11 wouldn't exceed using 66% of my new 96GB of RAM, until I read about the (dot)wslconfig file. Once I created the file as shown above, keyhunt could finally utilize all of my RAM. 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


There are some higher end systems you can rent with 512GB+ of RAM but they're expensive and they basically charge by the minute. But while you're waiting for Keyhunt to make the bloom filters, you can compile and run bitcrack, vanitysearch, or whatever to utilize the GPU(s) at the same time.

Alberto.

I recommend https://electriccoin.co/zashi/ or any other supporting shielded and unshielded addresses.


Also how close are you to developing GPU support?

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.

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