Keyhunt - development requests - bug reports

[albert0bsd]

There are 2 processors installed on the motherboard. The program only works with one. I specify all cores, but only one processor is used. The program can't work with multiple processors?

That depend of the Operating System.

It is not related the program.

[1714285442]

1714285442

[1714285442]

1714285442

[1714285442]

1714285442

[1714285442]

1714285442

[AliBah]

Thanks to Alberto for this nice tool

I tried to test my speed with puzzle 120 which you put on github for test and thats working.
But when i try to start scan puzzle 130 the processing stuck in 0%


I changed the -k from 256 to 128 now thats working...
in windows -k 256 worked

[albert0bsd]

I tried to test my speed with puzzle 120 which you put on github for test and thats working.
But when i try to start scan puzzle 130 the processing stuck in 0%

I changed the -k from 256 to 128 now thats working...
in windows -k 256 worked

The issue may be some configuration of the WSL enviroment sometimes it is capped at a certain percentage of the Host RAM please check:

https://www.aleksandrhovhannisyan.com/blog/limiting-memory-usage-in-wsl-2/

[AliBah]

I tried to test my speed with puzzle 120 which you put on github for test and thats working.
But when i try to start scan puzzle 130 the processing stuck in 0%

I changed the -k from 256 to 128 now thats working...
in windows -k 256 worked

The issue may be some configuration of the WSL enviroment sometimes it is capped at a certain percentage of the Host RAM please check:

https://www.aleksandrhovhannisyan.com/blog/limiting-memory-usage-in-wsl-2/

Thank you Alberto, the problem fixed now.

now , random mode is more useful or sequential mode?
is it good that we start at beginning of range or start from 10% or more of range?

[albert0bsd]

Thank you Alberto, the problem fixed now.

now , random mode is more useful or sequential mode?
is it good that we start at beginning of range or start from 10% or more of range?

That depend of your target, for small ranges sequential is good, but for largest ranges random is the best choice.

[AliBah]

Thank you Alberto, the problem fixed now.

now , random mode is more useful or sequential mode?
is it good that we start at beginning of range or start from 10% or more of range?

That depend of your target, for small ranges sequential is good, but for largest ranges random is the best choice.

May please explain alittle how random mode working? is it different every time we start random?

[albert0bsd]

May please explain alittle how random mode working? is it different every time we start random?

It is always random, check your self with the -M option

[AliBah]

i have a server with 8 cores and 16gb Ram
Im using -t 8 -k 1024, the speed is 115 pkeys/s.
should I still using random mode or with this speed its good to use sequential mode?

is there any recommended command with this server for faster speed?

[albert0bsd]

is there any recommended command with this server for faster speed?

I have no idea, btw the speed is not good, to be honest with you not even some hundreds exakeys are enough for this.

[AliBah]

how much is your speed with your pc Alberto?

[albert0bsd]

how much is your speed with your pc Alberto?

My speed is no important, I get 1 Exakeys/s as far i can remember.

[AliBah]

how much is your speed with your pc Alberto?

My speed is no important, I get 1 Exakeys/s as far i can remember.

If i asked its because i want to buy new pc and need your advice for choose hardwares.

[_Counselor]

Hi, Alberto.

xpoint mode does not work at full possible speed, because FLAGSEARCH has default value of 2 (SEARCH_BOTH); then at thread_process you have following condition:

Code:

calculate_y = FLAGSEARCH == SEARCH_UNCOMPRESS || FLAGSEARCH == SEARCH_BOTH || FLAGCRYPTO  == CRYPTO_ETH;

If you add an exception there for xpoint, unnecessary calculations of Y-coordinate will not occur and this will at least 1.5x speed in xpoint mode I think.

[albert0bsd]

Hi, Alberto.

xpoint mode does not work at full possible speed, because FLAGSEARCH has default value of 2 (SEARCH_BOTH); then at thread_process you have following condition:

Code:

calculate_y = FLAGSEARCH == SEARCH_UNCOMPRESS || FLAGSEARCH == SEARCH_BOTH || FLAGCRYPTO  == CRYPTO_ETH;

If you add an exception there for xpoint, unnecessary calculations of Y-coordinate will not occur and this will at least 1.5x speed in xpoint mode I think.

Hi, thank you very much to point to this, yes you are right with this it is not working at full speed. A big facepalm for me.

I will correct it ASAP and update the code.

Maybe i should use separate functions for those modes to also avoid unnecesary switch-case opcions.

Regards!

[cryptoperson678]

Say, I'm willing to randomly waste electricity on one of the puzzles using keyhunt in bsgs random mode. Is there a way to somehow store progress with the goal to not check already scanned keys/ranges...

Currently I am using this command keyhunt -m bsgs -f tests/130.txt -b 130 -R -n 0x100000000000 -k 2048  -q -t 8 -s 10 -S

Any input would be appreciated.

Also, does anyone have comments on the params I'm running? I have 64GB of RAM, however if I set k to 4096 I start to swap for a couple of Gigabytes, with k = 2048 the RAM is filled only to half, is there a way to use around 60GB of RAM to realize the full potential of my setup?

[_ic0nic_]

 
I'm fairly new to the internal functionalities (which I'm trying to figure out as I go lol).
So, I've gone thru the demo shown in the readme but when I ran the command, I get the error:

Code:

$ time ./keyhunt -m bsgs -t 6 -f tests/in.txt -r 49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e0000000000000000:49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5effffffffffffffff -n 0x1000000000000000 -M -s 0
[+] Version 0.2.230519 Satoshi Quest (legacy), developed by AlbertoBSD
[+] Threads : 6
[+] Matrix screen
[+] Turn off stats output
[+] Mode BSGS sequential
[+] Opening file tests/in.txt
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
[E] The file don't have any valid publickeys

real	0m0.081s
user	0m0.044s
sys	0m0.007s

I am on a macbook (I should've invested in a dam hp laptop or something, but oh well) and it's the legacy version.
I used the same file and same command prompt as shown in the readme so I don't know what the problem could be.

Thanks in advance though, if a solution arises. 

[albert0bsd]

Thank you for report this I will check it ASAP

[kosiosl]

Hey community!

Does anyone knows how to search ETH ADDRESS with prefix? Something like that ./KeyHunt -g --gpui 0 --gpux 256,256 -m address --coin eth -r 1 0x1ffb. The code only accept a whole ETH ADDRESS for searching.

[Ovixx]

I'm fairly new to the internal functionalities (which I'm trying to figure out as I go lol).
So, I've gone thru the demo shown in the readme but when I ran the command, I get the error:

Code:

$ time ./keyhunt -m bsgs -t 6 -f tests/in.txt -r 49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e0000000000000000:49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5effffffffffffffff -n 0x1000000000000000 -M -s 0
[+] Version 0.2.230519 Satoshi Quest (legacy), developed by AlbertoBSD
[+] Threads : 6
[+] Matrix screen
[+] Turn off stats output
[+] Mode BSGS sequential
[+] Opening file tests/in.txt
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve)
[E] The file don't have any valid publickeys

real	0m0.081s
user	0m0.044s
sys	0m0.007s

I am on a macbook (I should've invested in a dam hp laptop or something, but oh well) and it's the legacy version.
I used the same file and same command prompt as shown in the readme so I don't know what the problem could be.

Thanks in advance though, if a solution arises.  

It works for me on WSL. Check if the public keys in the in.txt file are valid.

Code:

ovidiu@#########:~/keyhunt$ time ./keyhunt -m bsgs -t 6 -f tests/in.txt -r 49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e0000000000000000:49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5effffffffffffffff -n 0x1000000000000000 -M -s 0
[+] Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
[+] Threads : 6
[+] Matrix screen
[+] Turn off stats output
[+] Mode BSGS sequential
[+] Opening file tests/in.txt
[+] Added 16 points from file
[+] Range
[+] -- from : 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e0000000000000000
[+] -- to   : 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5effffffffffffffff
[+] N = 0x1000000000000000
[+] Bloom filter for 1073741824 elements : 3680.66 MB
[+] Bloom filter for 33554432 elements : 115.02 MB
[+] Bloom filter for 1048576 elements : 3.59 MB
[+] Allocating 16.00 MB for 1048576 bP Points
[+] processing 1073741824/1073741824 bP points : 100%
[+] Making checkums .. ... done
[+] Sorting 1048576 elements... Done!
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e0000000000000000
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e4000000000000000
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e6000000000000000
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e2000000000000000
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5e8000000000000000
[+] Thread 0x49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5ea000000000000000

[Airfin Same]

I want to open this thread to talk about the tool that i develop Keyhunt available on github.

https://github.com/albertobsd/keyhunt

Keyhunt use the BSGS algorimth to find privatekeys with the publickey, the program runs on CPU and make several use of RAM to boost the speed.

Current Version 0.2.230430 Satoshi Quest
Lastest changes on development branch


How to use

Download and build
Run againts puzzle 66 (addres mode) 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 6.6 BTC

Code:

./keyhunt -m address -f tests/66.txt -b 66 -l compress -R -q -s 10

You need to add -t numberThreads to get better speed

Run againts Puzzle 130 (bsgs mode) 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua 13 BTC

Code:

./keyhunt -m bsgs -f tests/130.txt -b 130 -q -s 10 -R

You need to add -t numberThreads and -k factor to get better speed

Best regards!

hi albert0bsd
i want to try keyhunt
is there a compiled copy of keyhunt to work on windows