Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The -w save.work option doesn't save all keys from the in.txt file. #71

Open
marssystems opened this issue Feb 24, 2021 · 7 comments · May be fixed by #79
Open

The -w save.work option doesn't save all keys from the in.txt file. #71

marssystems opened this issue Feb 24, 2021 · 7 comments · May be fixed by #79

Comments

@marssystems
Copy link

When I run the program like this -

C:\SMARTMAINERXXX3\Kangaroo.exe -t 4 -gpu -w save.work -o C:\SMARTMAINERXXX3\result1.txt -wi 600 in.txt
I get this -

Kangaroo v2.2
Start:1
Stop :FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Keys :4
Number of CPU thread: 4
Range width: 2^256
Jump Avg distance: 2^126.99
Number of kangaroos: 2^18.34
Suggested DP: 106
Expected operations: 2^129.09
Expected RAM: 352.8MB
DP size: 64 [0xFFFFFFFFFFFFFFFF]
SolveKeyCPU Thread 1: 1024 kangaroos
SolveKeyCPU Thread 2: 1024 kangaroos
SolveKeyCPU Thread 3: 1024 kangaroos
SolveKeyCPU Thread 0: 1024 kangaroos
GPU: GPU #0 GeForce GTX 1050 (5x128 cores) Grid(10x256) (32.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^18.32 kangaroos [2.7s]
[187.95 MK/s][GPU 154.70 MK/s][Count 2^30.41][Dead 0][09s (Avg 1.22283e+23y)][2.0/4.0MB]

You can see that there are 4 keys in the in.txt file.

When I restart the program like this -

C:\SMARTMAINERXXX3\Kangaroo.exe -t 4 -gpu -w save.work -o C:\SMARTMAINERXXX3\result1.txt -wi 600 -i save.work
I get this -

Kangaroo v2.2
Loading: save.work
Start:1
Stop :FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
Keys :1
LoadWork: [HashTable 2.0/4.0MB] [00s]
Number of CPU thread: 4
Range width: 2^256
Jump Avg distance: 2^126.99
Number of kangaroos: 2^18.34
Suggested DP: 106
Expected operations: 2^129.05
Expected RAM: 1461248387923276.5MB
DP size: 64 [0xFFFFFFFFFFFFFFFF]
SolveKeyCPU Thread 1: 1024 kangaroos
SolveKeyCPU Thread 3: 1024 kangaroos
SolveKeyCPU Thread 0: 1024 kangaroos
SolveKeyCPU Thread 2: 1024 kangaroos
GPU: GPU #0 GeForce GTX 1050 (5x128 cores) Grid(10x256) (32.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^18.32 kangaroos [2.7s]
[204.01 MK/s][GPU 167.95 MK/s][Count 2^36.27][Dead 0][10:01 (Avg 1.09833e+23y)][2.0/4.0MB]

There is only 1 key saved in the save.work file.

Is there a fix for this?
@marssystems marssystems changed the title The -w save.work option doesn't save all keys in the in.txt file. The -w save.work option doesn't save all keys from the in.txt file. Feb 24, 2021
@AndreasSchaek AndreasSchaek linked a pull request Mar 16, 2021 that will close this issue
Open
@AndreasSchaek
Copy link

I had the same problem and created a quick fix for it.

@marssystems
Copy link
Author

That's great! - Thanks!
Just need it to be incorporated into the next release.

@marssystems
Copy link
Author

Any update on this?
Has the fix been implemented yet?

@AndreasSchaek
Copy link

someone with write access has to accept my PullRequest #79, the PR is still open.
But you can also compile it on your own (as I did) ....

@JeanLucPons
Copy link
Owner

Hello,
I had a look at the PR. Could you just put the key.z.SetInt32(1); before the EC check ?
Then I accept the PR.
Thx

@AndreasSchaek
Copy link

Hi Jean,
I'm very sure I had a good reason to do that.
Putting it afterwards was creating some kind of error but its too long ago, and I'd need some time to setup my environment again.
Maybe I can do this next month

@bigvito19
Copy link

Has this ever been updated or what? I really want to search for multiple public keys with kangaroo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

loop over available searchKeys AndreasSchaek/Kangaroo
4 participants
@AndreasSchaek @marssystems @JeanLucPons @bigvito19