View Single Post
  #89  
Old 03-05-2026, 23:57
cjack's Avatar
cjack cjack is offline
Family
 
Join Date: Jan 2002
Posts: 170
Rept. Given: 196
Rept. Rcvd 176 Times in 34 Posts
Thanks Given: 332
Thanks Rcvd at 219 Times in 64 Posts
cjack Reputation: 100-199 cjack Reputation: 100-199
Quote:
Originally Posted by WhoCares View Post
I confirmed there is only one process for solver_fast.exe.

My command is:
solver_fast.exe --server ecdlp.protect.cx --worker-name "WhoCares" --gpu-limit 100 --worker-notes "RTX 4070" --resume

And I have no 5070 Ti card. Only one NVIDIA card.

Shall I remove "--gpu-limit 100"?
I originally set it to 50, but later I got lazy and just changed it to 100 without removing that parameter.
Thanks for checking! Good news — the issue wasn't on your end at all. We tracked it down to a bug in the solver itself.

The problem: init_worms() used a deterministic hash based only on thread ID. This meant every time an agent reconnected (server restart, network hiccup, etc.), it replayed the exact same random walks from the exact same starting points — producing identical DPs. Since there were several server restarts yesterday, most iterations across ALL agents were duplicated work.

Your --gpu-limit 100 is fine, no need to remove it (100 = no throttling, same as not having the flag).

The fix is in agent v1.4.0 and above — worm initialization now uses a session-unique seed (time ^ PID), so every session and every agent gets different starting points.

Download the new agent directly from the server here:
https://ecdlp.protect.cx/download/ArmadilloSolver.zip

Just replace solver_fast.exe and restart. Your same command line works perfectly.

Last edited by cjack; 03-06-2026 at 00:04.
Reply With Quote
The Following User Says Thank You to cjack For This Useful Post:
WhoCares (03-06-2026)