I#ve just found that Cyclone wrongly reads the ranges from file and/or changee them.
For example, I have small ranges with an amplitude of 0x1000000 and Cyclone changes the ranges to an amplitude of 0x10000000000
- Fixed range parsing in `readRangesFromFile`:
- Normalized hex values to uppercase.
- Removed whitespace from ranges.
- Added hex character validation.
- Resolved discrepancies between file and direct input.
./Cyclone -h e0b8a2baee1b77fc703455f39d51477451fc8cfc -f list.txt -t 1 -b 5 -S
================= WORK IN PROGRESS =================
Puzzle/Bits : 29
Target Hash160: e0b8a2baee1b77fc703455f39d51477451fc8cfc
Prefix length : 5 bytes
Mode : Sequential
CPU Threads : 1
Mkeys/s : 4.44
Total Checked : 88743936
Elapsed Time : 00:00:20
Range : af6e3791fc0000000:af6e3791fcfffffff
Progress : 33.059692 %
Progress Save : 0
Stride : 1
^C
https://github.com/NoMachine1/Cyclone/tree/mainWhat do you mean by this stride? Is it working here? By default, it makes sense in a sequential search, but does the function still work if we increase it?