Quote from: singlethread1 on March 22, 2025, 10:11:16 PM

Quote from: nomachine on March 22, 2025, 08:53:36 PM

However, I’m not responsible for what happens after that.

The script processes keys in batches (e.g., POINTS_BATCH_SIZE). A large stride might cause the batch size to be exceeded, leading to incomplete or incorrect processing, progress calculation or even crashing the entire program.

That’s why I don’t like to mess with other people’s scripts. It’s easier for me to rebuild a new one from scratch than to try to support someone else’s script that works in a way they think is well-designed. Grin

Hey nomachine, maybe you already mentioned this in an earlier message, and if so I apologize. Why am I getting almost twice the MKeys/s with your program than I get with the original Cyclone program? Have you optimized for this much of a speed increase, or am I doing something wrong? Thanks!

Which version and from where? Use the latest version from GitHub. It doesn’t go beyond 4.80 Mkeys/s per core, which is the same as in the original version.

Quote

================= WORK IN PROGRESS =================
Puzzle/Bits : 68
Target Hash160: e0b8a2baee1b77fc703455f39d51477451fc8cfc
Prefix length : 5 bytes
Mode : Random
CPU Threads : 1
Mkeys/s : 4.80
Total Checked : 110313472
Elapsed Time : ∞
Range : 80000000000000000:fffffffffffffffff
Progress : ∞
Progress Save : 0
Stride : 1