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

[marssystems]

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?

[AndreasSchaek]

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

[marssystems]

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

[marssystems]

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

[AndreasSchaek]

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]

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]

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]

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