when you never show your settings/command line, it makes it harder to help you without having to ask you 10 questions to understand what you are doing wrong.
Since you insist 😀 here, I'm testing puzzle 153. What am I doing wrong?
Desktop\WIF>wifsolver.exe -restore filestatus.txt -c -stride 1520000000 -rangestart 100000000000000000000000000000000000000 -rangeend 1ffffffffffffffffffffffffffffffffffffff -a 18192XpzzdDi2K11QVHR7td2HcPS6Qs5vg
WifSolver 0.6.2
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9Mr4DWxM4mCemQa
-rangeStartInit=800000000000000000000000000000000000000000000000000000000000000001014671FC3F
-rangeStart=800000000000000000000000000000000000000000000000000000000CF3D73599014671FC3F
-rangeEnd=80FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD036414101271AA03F
-stride=1520000000
-a=18192XpzzdDi2K11QVHR7td2HcPS6Qs5vg
-checksum=
-c
-b=16
-t=640
-s=5000
Lol, I know I'm looking in a wrong place though.
You would have to actually know a partial of the actual WIF to use this program.
Or at least that's what it seems.
Also, the speed...I am not sure what it is measuring but it is not accurate to me, unless I misunderstand it.
If it is checking 87,000,000,000 keys per second, then this should have solved before it started.
Unless it is checking WIFs and checksums, which could be accurate then.
What I am saying is, it is not checking a private key, like Bitcrack or VBCr does. And in cases where the characters are missing from the end, this is not the fastest program to use.
I ran a test with a known 40 bit key...I removed 7 characters from the end (for quickness), and used a stride of 1.
It found the key in 31 seconds...which is good, but other programs could find this in under a second.
The money for this program is when you are missing characters in the middle and you know the checksum, or have the last x many characters of the wif.
But I know you need a partial of the WIF, and it seems like in the middle is the best...
I do not know if you can use rangestart and end as you have it, let me check real quick...no, you can not, you must use the range like:
-rangeStart 80000000000000000000000000000000000000000000000000000000e9ae4933d4693f8c6500 -rangeEnd 80000000000000000000000000000000000000000000000000000000e9ae4933d66b55a90f7f
Lastly, your stride is based on the last character (from the right) of the WIF you are looking for. If you have no WIF then you can't know what it needs to be.
Test with missing characters at the end:
wifcuda>WifSolverCuda -c -wifStart KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9aFJuCJD1111111 -stride 1 -wifEnd KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9aFJuCJDzzzzzzz -a 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
WifSolver 0.6.2
Use parameter '-h' for help and list of available parameters
Using GPU nr 0:
NVIDIA GeForce GTX 1660 Ti (24 procs)
maxThreadsPerBlock: 1024
Range start: 80000000000000000000000000000000000000000000000000000000E9AE4933D4693F8C6500
Range end : 80000000000000000000000000000000000000000000000000000000E9AE4933D66B55A90F7F
Stride : 1
Target : 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
Target COMPRESSED
number of blocks: 192
number of threads: 640
number of checks per thread: 5000
Work started at Thu Jan 26 16:59:10 2023
87.649 GKey/s, progress: 70.790%
found: 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
key : E9AE4933D6
WIF : KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9aFJuCJDo5F6Jm7
Work finished at Thu Jan 26 16:59:41 2023
I am sure OP can explain better/more than me...but you need to have partial WIF to really use this program.
