Time.Estimated, does this estimate look accurate ?

[JimBob]

Hello All,

Hashcat newbie here with a single AMD Sapphire 7970.   Using a sample bitcoin / litecoin hash, I'm attempting
a bruteforce attack on 10 character password.  The following estimate of 3 years, 61 days seems low to me
considering the keyspace is over 3.6 trillion.   Does this look accurate? would anyone care to guess / compute
how long an 8 x GTX 1080 TI rig would take to complete this?

Thank You.

hashcat (v3.5.0) starting...


OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Tahiti, 2816/3072 MB allocatable, 32MCU
* Device #2: AMD Phenom(tm) II X4 840 Processor, skipped.

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger disabled.
Watchdog: Temperature retain trigger disabled.

[s]tatus [p]ause [r]esume ypass [c]heckpoint [q]uit =>

Session..........: 1
Status...........: Running
Hash.Type........: Bitcoin/Litecoin wallet.dat
Hash.Target......: $bitcoin$96$d011a1b6a8d675b7a36d0cd2efaca32a9f8dc1d...760525
Time.Started.....: Sat May 06 15:54:41 2017 (19 secs)
Time.Estimated...: Tue Jul 07 01:41:40 2020 (3 years, 61 days)
Guess.Mask.......: ?1?1?1?1?1?1?1?1?1?1 [10]
Guess.Charset....: -1 ?l?d, -2 Undefined, -3 Undefined, -4 Undefined
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:     2800 H/s (75.14ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0/3656158440062976 (0.00%)
Rejected.........: 0/0 (0.00%)
Restore.Point....: 0/101559956668416 (0.00%)
Candidates.#1....: sarinanera -> smlu198898

[undeath]

There might be some overflow happening. 3y is definitely off.

(26+10)**10 / 2800 / 60 / 60 / 24 / 365 = 41405.7227121722 (years)

even with a high end rig this kind of keyspace is not realistic.

[epixoip]

Well, it's not an overflow, it fits fine in a uint64: http://www.wolframalpha.com/input/?i=36%...2%5E64+-+1

And the Progress line is correct (36^10 == 3656158440062976), confirming that it is not an overflow.

But 3 years is definitely wrong, it would in fact be 41k years. So I'm not sure where the error lies. Might want to open an issue on Github.