Keyhunt-CUDA - searching for predefined list of keys

[citb0in]

Hello community,

does anyone know a Keyhunt-CUDA version that is able to read a file that has a hexkey per line and searches this list sequentially?

Example:
unordered.lst is a 500MB file and contains a private key per line in hexadecimal form. Now Keyhunt-Cuda should read this file instead of a range and process it sequentially, e.g:

./KeyHunt-Cuda -t 0 -g -m address --keylist privkey.lst 123btcaddress...

but it should also be possible to specify several wallet addresses using the "-m addresses" switch, e.g:

./KeyHunt-Cuda -t 0 -g -m addresses --keylist privkey.lst walletaddress.lst

Does anyone know of such a modified KeyHunt-Cuda version that may already exist? Or is someone able to implement this modification in the latest KeyHunt-Cuda version? I look forward to constructive feedback and wish you all a nice weekend.

[1714513920]

1714513920

[1714513920]

1714513920

[1714513920]

1714513920

[1714513920]

1714513920

[1714513920]

1714513920

[1714513920]

1714513920

[digaran]

then do your homework and don't beg others to do it for you. This is not a job market portal

I believe you said this yourself, right? So what has changed since? you are either a beggar or a hypocrite or both.
But I do like to see improvements on brute force tools, so lets see who is willing to help here.😉

[WanderingPhilospher]

I am a little confused as to what you want.

contains a private key per line in hexadecimal form

You have a file of private keys in hex form and want keyhuntcuda to take each line and change it to it's BTC address or searches for them??

It can't be to search for them because you already know the private key, so you must want to take the private keys and transform them to an address, right?

Please advise.

[citb0in]

KH should not generate sequential or random keys, it should use a predefined list of keys. No other changes in KH operation, everything else remains the same.

[WanderingPhilospher]

KH should not generate sequential or random keys, it should use a predefined list of keys. No other changes in KH operation, everything else remains the same.

By “Keys” you mean public keys or Hash160s, as it is now?

If you have this predefined list of x, what is KeyHunt Cuda doing with it?

[citb0in]

Imagine you have a list with 10^18 private keys which you want to check if they match the wallet address 123btc...
Python is no alternative because it's way too slow. I like to have it in CUDA (GPU) and that's why I think KeyHunt-Cuda may the way to go. If you have a better idea which you suggest, I'd appreciate to hear about. Thank you.

[WanderingPhilospher]

Imagine you have a list with 10^18 private keys which you want to check if they match the wallet address 123btc...
Python is no alternative because it's way too slow. I like to have it in CUDA (GPU) and that's why I think KeyHunt-Cuda may the way to go. If you have a better idea which you suggest, I'd appreciate to hear about. Thank you.

I hope 10^18 is just a number because even with a GPU turning 12M/sec it would take 26 years to complete the list. Wow!

But I now know what you are after.

I don’t think it exists, but would need some mod work with reading a file and mod work with the next key function.

[digaran]

So he wants to first generate 10^18 private keys, then stores them on a file, and then load them on to keyhunt just to generate rmd160/addresses to compare for a possible match? why not set a range to do that on step 1?

[kosiosl]

Is it possible to search for ETH ADDRESS with prefix, not whole address?