Did you lose all the DPs @ 31, when you dropped to 28?

I also shared some files earlier.
Can you please upload your files to here: https://gofile.io
You can do it without registration, and you can delete them with your admin link at any time. Unfortunately google does not allow do download your file without google account.

I was testing "directory merge" function and RAM memory is quickly exhausted. I was thinking that I forgot to free temp HashTable in each reading iteration; but I changed the code and the problem remains
The merged saveFile is 5GB, and in merge process takes up about 14GB of RAM.

I think the more obvious solution is to sort files from bigger to smallest when are merged; or use only small saveFiles.


On the other hand, the -ws flag I think is problematic when using -wsplit, generating larger files than necessary. Do you think it is interesting to separate the DP and the kangaroos into different save files?


As next improvements, I will work on improving the export of the DPs and the possibility of modifying the DP bits in a save file to reduce its size if we have chosen a too low DP value. It can also be interesting to remove from a save file the distances to share it without gifting the prize.

It is not a problem, if CRC32 invalid, that file will be send in next time.

I tested dir merge on PC with 24GB RAM and 10 dir files that were probably 500MB a piece but I didn't check the RAM usage.

Alek76's version is similar to what you are talking about as far as separating files. He has (in current version) 8 text files that are generated, 4 tames and 4 wild. I modified it a little bit and used 2 tames and 4 wilds. Then, he has a python comparator that compares all the files to check for a solved key. I tried/trying to figure out how to merge that with JP's (this) version, but can't figure out how to read the files well enough to understand how to build the python comparator.

I think if you fined key in 64 bit, you not need next 64 bit, but if you fined only on 3*64 bits false and after only 1  BINGO 64 bit, this is I  think not = 256 bytes key and fourth 64 bits with private key will be not 256 bytes key too.........

Hardware, how long are you running your precomp for? You have a set # of DPs or a percentage? 2/3 ops?

Can you explain me this, please.
Searching key 0xa123fe3456
Searching pub key 0xe6dabff2705a80acc23ae121956873c4ff9fd31cb0faca522c33624e23657e04125c04d29ea83 874332ea8aef3b3467f22665a4970df415be756bcdf5675e569
range 0..fffffffffffff  (so there no shifting and working pubkey=original pubkey)
Look to hashtable..
x=0x7760a4827fcb4d02210c4fb962f48c49
d=0x40000000000000000006a6bdf014bd68
that mean that type wild and sign +
ok let`s verify (0x0a123fe3456+0x6a6bdf014bd68)*G = 0xd4814ad2a48ec5f0f1fdce8832800007760a4827fcb4d02210c4fb962f48c49 result corrrect
let`se other DP
x=0x3c628f41e76f5bce8566c3dfa2c3fff0
d=0xc000000000000000000617445c562205
that mean that type wild and sign -
But 0x617445c562205>0x0a123fe3456.. And here is question how it can be that key - distance is out of range???
Ok. it is addidng point not addiding key + distance
(0xe6dabff2705a80acc23ae121956873c4ff9fd31cb0faca522c33624e23657e04,0x125c04d29ea83874332ea8aef3b3467f22665a4970df415be756bcdf5675e569)
+ (fb12e2e7eba822db7582b91da81c0f1d991a6fec79d170733a1eceb039b3e1f9,ee2e79d5326d178c91ed36ca52f9be4f04c42e3cf7cabb3299e070bc1231bb05)
=(dcbae520622e89bd4c0062bb82400003c628f41e76f5bce8566c3dfa2c3fff0,b6fdc18b5be9048e837759b86efa422511b717ed9e7bc2d7b1936c06a0620cfe)
and x coordinate is correct,, but any way tame will never get this point becouse it is out of range 0..fffffffffffff
So not all wild can be tame. We can tame all wild with sign + but each wild with sign - should be verifid with range.
In that case we can add tamed wild to experience.

Split range it is bad idea. kangaroo never say that there no key, you can check this range even with 4sqrt(n) and break opereation after a lot of operations
but this does not guarantee that there is no key. And in that case you will lose chance to get prize forever.