When running the software using docker I get to see the following:
VanitySearch v1.17 Linux with BitCrack integration [HEX=57XEC98]
[keyspace] start=57XEC9800000000000 [HEX=57XEC98]
[keyspace] end=57XEC99FFFFFFFFFFF [HEX=57XEC98]
Output File: [HEX=57XEC98]
Search: 7 addresses (Lookup size 7,[1,1]) [Compressed] [HEX=57XEC98]
Current task START time: Wed Jul 30 17:25:23 2025 [HEX=57XEC98]
If we look at the range it is not just 7 characters as it should be 57XEC9800000000000 - 57XEC98FFFFFFFFFFF as per my current understanding.
Please note ending is 57XEC99FFFFFFFFFFF meaning we might be doubling the work but just accounting for half of it??
Checking API response to get a range:
"workloadStart": "00000000000",
"workloadEnd": "1fffffffffff"
I can see workload start has 11 characters but workload end has 12 characters.
Please check this looks like a possible bug on API side causing double processing.
When running the software using docker I get to see the following:
VanitySearch v1.17 Linux with BitCrack integration [HEX=57XEC98]
[keyspace] start=57XEC9800000000000 [HEX=57XEC98]
[keyspace] end=57XEC99FFFFFFFFFFF [HEX=57XEC98]
Output File: [HEX=57XEC98]
Search: 7 addresses (Lookup size 7,[1,1]) [Compressed] [HEX=57XEC98]
Current task START time: Wed Jul 30 17:25:23 2025 [HEX=57XEC98]
If we look at the range it is not just 7 characters as it should be 57XEC9800000000000 - 57XEC98FFFFFFFFFFF as per my current understanding.
Please note ending is 57XEC99FFFFFFFFFFF meaning we might be doubling the work but just accounting for half of it??
Checking API response to get a range:
"workloadStart": "00000000000",
"workloadEnd": "1fffffffffff"
I can see workload start has 11 characters but workload end has 12 characters.
Please check this looks like a possible bug on API side causing double processing.