Keyhunt - development requests - bug reports

[albert0bsd]

What is the solution to get this error? BSGS mode

Get more RAM or use a different K or N parameters

[AndrewWeb]

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

Code:

2 G -k 128
4 G -k 256
8 GB -k 512
16 GB -k 1024
32 GB -k 2048
64 GB -n 0x100000000000 -k 4096
128 GB -n 0x400000000000 -k 4096
256 GB -n 0x400000000000 -k 8192
512 GB -n 0x1000000000000 -k 8192
1 TB -n 0x1000000000000 -k 16384
2 TB -n 0x4000000000000 -k 16384
4 TB -n 0x4000000000000 -k 32768
8 TB -n 0x10000000000000 -k 32768

Thanks, I got 2 exa (2 quintillion) 2,000,000,000,000,000,000 keys per second with:

./keyhunt -m bsgs -f tests/135.txt -b 135 -R -q -S -n 0x400000000000 -k 4096 -t 24

[powerusa]

tests/135 solved

[h3ll0n0n4m3]

What is the solution to get this error? BSGS mode

Get more RAM or use a different K or N parameters

Hi, @albert0bsd

What parameters for BSGS with 56GB of RAM ?

AND

Is there a guide to compile keyhunt for MacOS with ARM CPU (like M1, M2, M3...) ?

(Noob tutorial will be nice)

Thanks for your reply by advance.

[albert0bsd]

What parameters for BSGS with 56GB of RAM ?

It may be something with -k 3072

Is there a guide to compile keyhunt for MacOS with ARM CPU (like M1, M2, M3...) ?
(Noob tutorial will be nice)

Sadly no, there is not a complete one... If you are developer for MAC there are some issues open or closed:

https://github.com/albertobsd/keyhunt/issues/268
https://github.com/albertobsd/keyhunt/issues/244
https://github.com/albertobsd/keyhunt/issues/202
https://github.com/albertobsd/keyhunt/issues/155
https://github.com/albertobsd/keyhunt/issues/137
https://github.com/albertobsd/keyhunt/issues/87
https://github.com/albertobsd/keyhunt/issues/7

To be honest, with the money that you use to buy a MAC you can buy one or two High end PCs with the last hardware and having 0 issues.

[jmr270492]

@albert0bsd Could you explain how the -z parameter works?

[albert0bsd]

@albert0bsd Could you explain how the -z parameter works?

It was an experiment, but it don't bring any speed boost as I expected so please don't use it.

[jmr270492]

@albert0bsd Could you explain how the -z parameter works?

It was an experiment, but it don't bring any speed boost as I expected so please don't use it.

Got it friend. I made a PR on GitHub, rate it Kindness, it is a version that solves compilation problems on Mac OS and Add a Compile for Windows too

[digir0n]

@albert0bsd

I compared the files unsolvedpuzzles.txt and unsolvedpuzzles.rmd and concluded that
67.txt value should be 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
and
67.rmd value should be 739437bb3dd6d1983e66629c5f08c70e52769371
So I created the 2 files in tests folder.
 
I am using this command
./keyhunt -m rmd160 -f tests/67.rmd -r 40000000000000000:40044FB67BC000000 -l compress -t 6 -s 10
which should take about 4 hours on my pc, but it is still running after passing 40044FB67BC000000

I want to scan a portion of a range sequentially in about 20 hour increments
so I can still game 4 hours a day and then continue next portion of range from where it stopped previously.
Is there a way to do it with rmd160?

[albert0bsd]

I am using this command
./keyhunt -m rmd160 -f tests/67.rmd -r 40000000000000000:40044FB67BC000000 -l compress -t 6 -s 10
which should take about 4 hours on my pc, but it is still running after passing 40044FB67BC000000

add

Code:

-n 1000000

default value is 0x100000000 (32 bits)

Got it friend. I made a PR on GitHub, rate it Kindness, it is a version that solves compilation problems on Mac OS and Add a Compile for Windows too

Did you know if your changes also compile on Linux in a Non-MAC hardware?


There is as brand called OSX: https://github.com/albertobsd/keyhunt/tree/osx

Where all changes for mac versions should go to no affect others versions, that is only if your changes affect the compilation for Linux.

I haven't checked it yet, I've been busy.

[digir0n]

@albert0bsd

add

Code:

-n 1000000

default value is 0x100000000 (32 bits)

Thank you for pointing me in the right direction.
Adding -n 0x1000000 after range worked

[lasaro_lima]

digir0n

Friend, how did you find this value 739437bb3dd6d1983e66629c5f08c70e52769371 to insert in 67.rmd? There was an error with this value in Keyhunt and this 67.rmd file with this value. Before, it was running with the value of the wallet address.


@albert0bsd

Can "-l compress" be used with bsgs mode? How to convert puzzle wallet addresses to use within the text file, for exemple 67.rmd?

[albert0bsd]

@albert0bsd

Can "-l compress" be used with bsgs mode? How to convert puzzle wallet addresses to use within the text file, for exemple 67.rmd?

No. that flag is only for address/rmd for BSGS that flag is ignored

[AliBah]

i tried to scan this range by bsgs mode

414ebfe886361d9e9cb2f5d46bfe1c3f1523fe80830600000000000000000000:414ebfe886361d9e9cb2f5d46bfe1c3f1523fe80830700000000000000000000

and the distance is only 600000000000000000000 to 700000000000000000000 keys.

Keyhunt still working for couple of days and 1676094623431730292326400 keys scanned which is more than 138% of range scanned.

how its possible? is there any bug?

Image:
https://bashify.io/i/bscwkF

[albert0bsd]

Keyhunt still working for couple of days and 1676094623431730292326400 keys scanned which is more than 138% of range scanned.

how its possible? is there any bug?

Some things, remove -l compress  it is complete ignored by the bsgs method

Second. READ the documentation: https://github.com/albertobsd/keyhunt?tab=readme-ov-file#valid-n-and-maximun-k-values-for-specific

It clearly said:

If you exceed the max value of K the program can have a unknow behavior, the program can have a suboptimal performance, or in the wrong cases you can missing some hits and have an incorrect SPEED.

So increment your N value and adjust K according to that table

[AliBah]

Keyhunt still working for couple of days and 1676094623431730292326400 keys scanned which is more than 138% of range scanned.

how its possible? is there any bug?

Some things, remove -l compress  it is complete ignored by the bsgs method

Second. READ the documentation: https://github.com/albertobsd/keyhunt?tab=readme-ov-file#valid-n-and-maximun-k-values-for-specific

It clearly said:

If you exceed the max value of K the program can have a unknow behavior, the program can have a suboptimal performance, or in the wrong cases you can missing some hits and have an incorrect SPEED.

So increment your N value and adjust K according to that table

my server cpu is : (2x) Xeon E5-2680 v2 (40 threads)
ram : 320 GB

whats the correct command for bsgs mode and address mode?

[albert0bsd]

I have NO IDEA, test it by yourself

[AliBah]

I have NO IDEA, test it by yourself

I calculated the k value like this :

I have 320GB ram so each 1GB is 64 for k value and k is 20480 for 320GB ram. was it wrong? and i just should use table value ?

[AliBah]

according to the table I should use :

256 GB -n 0x400000000000 -k 8192

and rest of my Ram capacity will be in free

[albert0bsd]

Sorry guys to make a program difficult to use.

I hope come back some day with a better and easy version for dummy people just to copy commands and run it.