Time prediction about finderouter HOT 5 CLOSED

It basically breaks down the entire work into little chunks then requests a new thread from a pool of threads and spreads the work to maximize efficiency.

from finderouter.

Whenever the missing characters are all from the end of the private key WIF string the code automatically chooses an optimized method that only has to check a very small fraction of the total variations in normal method. But it can only work if the number of missing keys is small (up to 12 chars for compressed WIFs).
The problem with this optimized method is that when the number of missing chars goes past the limit (eg. 13+) it becomes a lot slower than the normal method. So for anything bigger, the normal method is used automatically.

25 characters missing, that's a lot, do you think that with a 256-core processor extremely possible, I can recover?

A compressed private key WIF is 52 characters, 25 missing is nearly half of it which is more than 100 bits. It is not possible to brute force this.
Currently there is no benchmark option but you can always solve a simpler example to see your CPU speed. For example you can use L53fCHmQhbNp1B4JipfBtfeHZH7cAib*G9oK19*fiFzxH**kz6*K, then do a simple math to get the rough idea how long it would take to finish the search for any other number of missing characters. There are 1.21e44 keys to check for 25-missing chars with the speed of 26 million (you may get different value here) it takes 1.4e29 years to finish the search:
1.21e44/ 26 million / 60 / 60 / 24 / 365 = 1.4e29 years

i left it a few days, it appeared that it found "a possible key". This was about three times, then he kept checking.

This recovery method doesn't check its results against anything since in any normal case there won't be any more than 2 or 3 possible results. It is faster this way and the code will print all the results. In a key with much more number of missing keys the number of valid variations it finds will be a lot bigger.
These are all valid keys with a valid checksum, you'll have to manually check if they match the address you have.

from finderouter.

Currently with the software today it would be impossible to discover 25 characters that are missing from the private key? Another thing, does it not work with multi thread?

from finderouter.

Currently with the software today it would be impossible to discover 25 characters that are missing from the private key?

As far as I can tell, yes.

Another thing, does it not work with multi thread?

Yes it does. If you check your CPU usage while FinderOuter is working on such a key it should be using 100% of your CPU.

from finderouter.

Does the program use several tasks in each processor core to speed up the process?

from finderouter.