I'm a bit confused. The GitHub README says RCKangaroo has no networking or DP save/load support, but your Puzzle #135 post mentions hundreds of GPUs, a 1 TB RAM server, and a 400 GB DP database. Was that done with a private version of RCKangaroo, or did you build separate software around the public release? I'd appreciate any clarification.
Of course he has his setup the way he wanted it, he was nice enough to give you the free ware version to the masses with his SOTA+ ect , you should read the threads if you want to know more and also read the github info Sample command to generate tames:
RCKangaroo.exe -dp 16 -range 76 -tames tames76.dat -max 10
Then you can restart software with same parameters to see less K in benchmark mode or add "-tames tames76.dat" to solve some public key in 76-bit range faster.
From the thread his personal version was set up to be monitored by a personal server not something he should spend the time to explain to every person kinda interested in it.
I'm a bit confused. The GitHub README says RCKangaroo has no networking or DP save/load support, but your Puzzle #135 post mentions hundreds of GPUs, a 1 TB RAM server, and a 400 GB DP database. Was that done with a private version of RCKangaroo, or did you build separate software around the public release? I'd appreciate any clarification.
Ryan here is quote as to your post
“"Why would I stop? Any stops and changes are dangerous, you can lose progress partially or completely when you change something.
Same for splitting whole range into small pieces, it increases total complexity.
So I started the process, made several scripts to automate everything (it's boring to manage many GPUs and systems remotely) and paid bills for five months, it was not cheap and I had no guaranties of success, somebody else on this planet could find the key faster, or I could make an error somewhere in code or calculations and fail, and I would get exactly zero. This game is expensive.
People who think that they can crack 134bits of Secp256k1 with a couple of GPUs don't live in real world. I improved the algo itself and made crazy code using almost undocumented assembler, but anyway I had to rent hundreds of GPUs for months, with "normal" software like JLP's it would take years.
You are correct, K was about 0.35, I used mixed 4090 and 5090 cards. So I was lucky.
Also I remember somebody asked me if I want to share DB. I don't want, it's almost 400GB (I used DP=32 but anyway I had to use PC with 1TB RAM as a server), also I would need to provide all jump tables (they are calculated slightly different than RCKangaroo does for some reasons), just don't have time for this, also it won't help much for #140 that requires x5.5 more DPs. “"