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

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.

This can be caused y one of three problems

• Not enough privilegies on the current directory
• Not enough space
• WSL configuration

List the current directory with ls -lah to see if "." (current directory) have  your same user and write permissions.
Use df -h to see how many disk space is available.

For the last one please check https://learn.microsoft.com/en-us/windows/wsl/wsl-config.


Let me check how to get one, I also plan to add a Monero wallet.

Hello Alberto,

Can you please add the in GitHub ZEC donation address?

Addicted to the program, also I think you should accept private donations not everybody wants to reveal their wallets to the world.

THX

Hello Alberto. I built a new computer with better performance than the old one, in order to establish a higher value of the K factor. I have 192 GB DDR5 memory and Intel i9-14900K CPU. After I installed Windows 11, I installed the keyhunt application on WSL, but any of the K value I put, it gives me an error when saving the *.blm file. I ask you for advice to solve the problem. I tried from K = 8192, 4096 I went down to K = 256 and in vain. The problem is not from the value of K. I mention that I have enough free space, 1.28TB on a Samsung PRO SSD with 7000 MB read/write. Thank you in advance!

Thanks for the answer and help, I'm just a newbie but could play around a little bit!

Nice, not much people test it because not much knows that the server exists 


To keep the best performance in the server i should recommend not to look for this on the server side.

Instead of it i should recommend to this on client side, in the BSGSD.md file i post a small python client, since performance is not required on client python fit perfectly for this situation, you can send small chunks of work to the server something like 50 to 55 bits of subrange and edit the client output to print the speed:


In that code you need to set the sub-range value, this require to know what are you doing but you can get more or less the speed that you are getting in each time.
I hope this workaround fit your needs because to be honest i don't see any necessary to print the speed on the server side, it was made to attend clients without the need to be in front the same terminal.


For CPU i doubt it, I already did a lot of improvements compared against the BSGS of JLP i think that i realdy reach the CPU speed limit.
The only possible improvement will be implement another faster storage for the Baby table and bloom filters or the use of GPU (It need to rewrite all the code)


Thanks, you're more than welcome.

Regards!

Hello,

I have been testing and playing with keyhunt, very impressive and fast.  Recently, I tested bsgsd sever and it also is pretty fast:

time echo "0365ec2994b8cc0a20d40dd69edfe55ca32a54bcbbaa6b0ddcff36049301a54579 4000000000000000:8000000000000000" | nc -v localhost 8080
Ncat: Version 7.80
Ncat: Connected to 127.0.0.1:8080.
7cce5efdaccf6808Ncat: 101 bytes sent, 16 bytes received in 2.95 seconds.
real    0m2.961s
user    0m0.022s
sys     0m0.004s

I know printing to screen will cause lost of speed but, is there any way I can check exactly how many keys/s are running  in bagsd? With debug or something similar to what keyhunt shows, just for testing. I was able to run bsgsd from a little shell scrip so I can handle some specific ranges without restarting bsgsd each time (it takes half an hour for server to startup), after that, I could get 5E.

Will be any speed improvement in the future for bsgsd or bsgs key generator?

albert0bsd, thanks for all your work!!!

I've been using Keyhunt for a long time. It's a great program.
Are there any plans to incorporate an option to also search segwit, native segwit, and taproot addresses simultaneously along with the current legacy compressed/uncompressed addresses?
For example, if you wanted to use Keyhunt, in address mode, to do random searching in the full keyspace against Loyce Club's funded wallet list.
./keyhunt -m address -f tests/Bitcoin_addresses_LATEST.txt -l all -R -t 32 -s 10 (where "-l all" would be compressed, uncompressed, segwit, native segwit, taproot)

I know people say it's pointless but it'd be fun to try.

I just understand a little of Portuguese. I Only know Spanish and English.



It is not necessary to broadcast the transaction before mining the block.

Once that miners found a valid hash for their private block, they need to broadcast their full block data, only at that time the transaction will be public. (We are talking of private transactions that are only public once that they are already inside of a mined block).
Obviously that need to be a Custom miner software

You need to learn the full mining process, you need to know about the merkle trees and how block headers need to be build:
https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch12_mining.adoc#constructing-the-block-header

yeah, you need just some tons of hashpower, better some Exahashes/sec and a lot of patience