update:
v 0.4.7
I have improved memory management, now default configuration for single rtx3090 uses less than 100MB of RAM. previous it was more than 900MB
In the meantime I have added progress indicator, resume from status file and some other minor changes.
v 0.4.8
Support for segwit/p2sh addresses
v 0.5.0
I have changed the way how memory/data transfer is managed and if it is possible I use memory from host. It should not be a problem, even for sets with 4-8 cards on one host. Speed is improved up to 10%, but still it is good to play with number of blocks/threads/steps processed per thread.
On 3080Ti I process around 4000 MKey/s for WIF with missing beginning, I think it is a good result.
v0.5.2
I have prepared a new release, 0.5.2, it could be mini-mini-minimally better, as I decreased some unnecessary latency. But displayed speed probably will be lower - what was until now was a bit too optimistic (I was dividing work done by full seconds, when I divide by miliseconds result is closer to reality). On 3080ti I see speed +-3.830, but now we see it fluctuates every time is displayed - in old version it was 4.096 all the time.
There is also a new parameter "-v" - verbose output - to display WIF processed in status line - but as it is extra work, it slows down the process (not much but still).
And 2 new parameters "-wifStart -wifEnd" for automatic conversion of provided WIF to range start/end
v0.5.3
https://github.com/PawelGorny/WifSolverCuda/releases/tag/v0.5.3
Added support for P2WPKH addresses (bc1...)
v 0.4.7
I have improved memory management, now default configuration for single rtx3090 uses less than 100MB of RAM. previous it was more than 900MB
In the meantime I have added progress indicator, resume from status file and some other minor changes.
v 0.4.8
Support for segwit/p2sh addresses
v 0.5.0
I have changed the way how memory/data transfer is managed and if it is possible I use memory from host. It should not be a problem, even for sets with 4-8 cards on one host. Speed is improved up to 10%, but still it is good to play with number of blocks/threads/steps processed per thread.
On 3080Ti I process around 4000 MKey/s for WIF with missing beginning, I think it is a good result.
v0.5.2
I have prepared a new release, 0.5.2, it could be mini-mini-minimally better, as I decreased some unnecessary latency. But displayed speed probably will be lower - what was until now was a bit too optimistic (I was dividing work done by full seconds, when I divide by miliseconds result is closer to reality). On 3080ti I see speed +-3.830, but now we see it fluctuates every time is displayed - in old version it was 4.096 all the time.
There is also a new parameter "-v" - verbose output - to display WIF processed in status line - but as it is extra work, it slows down the process (not much but still).
And 2 new parameters "-wifStart -wifEnd" for automatic conversion of provided WIF to range start/end
v0.5.3
https://github.com/PawelGorny/WifSolverCuda/releases/tag/v0.5.3
Added support for P2WPKH addresses (bc1...)
i have downloaded the latest version, after i run the interface closed. is there any error running WifSolverCuda v0.5.3 ?? please help to fixed it.
