add multiple starting point

[makabress]

excelent combination , i like your work

just a suggestion :
-add multiple starting point to divide the keyspace

little bug

• if you add (ex: --keyspace 1:1000000000) the search of the prifix will go out of this range

[Telariust]

->just a suggestion
I’m no longer interested in this fork, I won’t support or improve it anymore

->little bug
..hmm
This is because of the symmetrical pack.
(from the START point half a pack down and half a pack up)
If the START point is so small that half a pack down gives a point less than zero, which is not permissible.
(the same problem will be on the upper boundary when half the packet exceeds the module value)
I forgot to add these checks, since initially this GPU tool was designed to work in the middle of the range.
Just don't use a very small START point.

[axe777]

Hi,
How did you calculate for VanitySearch-1.15_bitcrack the start of 0000000000000000000000000000000000000000000000000000000000000000000000000A00000000 for this address 1CABDYTie48wXV93XJ4Bdk7MFSTyshTXxg or is it a search start for all addresses?

[Comarro753]

->just a suggestion
I’m no longer interested in this fork, I won’t support or improve it anymore

->little bug
..hmm
This is because of the symmetrical pack.
(from the START point half a pack down and half a pack up)
If the START point is so small that half a pack down gives a point less than zero, which is not permissible.
(the same problem will be on the upper boundary when half the packet exceeds the module value)
I forgot to add these checks, since initially this GPU tool was designed to work in the middle of the range.
Just don't use a very small START point.

Buddy, I think your project very good. Please see my Issues.

Project has litle bags I think, but project is good to continue and end work Bro. Please, fix problem with multiple GPU, and complilation in Linux ????

[thearthouse]

->just a suggestion
I’m no longer interested in this fork, I won’t support or improve it anymore

->little bug
..hmm
This is because of the symmetrical pack.
(from the START point half a pack down and half a pack up)
If the START point is so small that half a pack down gives a point less than zero, which is not permissible.
(the same problem will be on the upper boundary when half the packet exceeds the module value)
I forgot to add these checks, since initially this GPU tool was designed to work in the middle of the range.
Just don't use a very small START point.

hi i know you wan't support. but you know c++ and you can help me in this little question . normally its icreasing by 1 but i want to set it like increase by 3 in which code section it is i couldnt find that increament