before starting a long running cracking job I would suggest to first make sure that your restrictions about the password candidates are correct and that your expected/test password candidates are even within the set of generated candidates.
For instance, the command above doesn't generate any "a" character like mentioned within your example "Ga8217598ga".
Therefore, you should make sure that:
1. you know that the length of the passwords you are trying is 100% correct (or could it be longer/shorter too?)
2. all characters that you think are within the password are also tested
3. the mask generates all of your test passwords
4. uppercase letters and lowercase letters are used correctly (position is important within the mask)
for instance, you could do something like this:
to see which password candidates are generated and if they look correctly (pipe the output to something like the unix head command and/or a filter like the unix grep command to make it more clear what is going on)
From your description of the examples it is also not clear if it is always "G", "g" and "a" or if it could be any upper- or lower-case letter. It's also not clear if the letters are the same at the start and ending or if they could be completely different, like this: YO4512859hi
Therefore, my suggestion is to make sure that you have a clear picture about what the "rules" of the password candidates are and use them correctly within the mask: https://hashcat.net/wiki/doku.php?id=mask_attack (see also custom characters defined with -1,-2,-3,-4 and used within the mask ?1,?2,?3,?4)
Of course the ethereum algo is a pretty slow one, so you should make the mask very specific and test only what needs to be tested (therefore using ?l and ?u and even ?d might not be the best thing to do here... if you can restrict the charsets even more to the characters you think were used)
For instance, the command above doesn't generate any "a" character like mentioned within your example "Ga8217598ga".
Therefore, you should make sure that:
1. you know that the length of the passwords you are trying is 100% correct (or could it be longer/shorter too?)
2. all characters that you think are within the password are also tested
3. the mask generates all of your test passwords
4. uppercase letters and lowercase letters are used correctly (position is important within the mask)
for instance, you could do something like this:
Code:
hashcat64.exe --stdout -a 3 -1 ?u?l ?1?1?d?d?d?d?d?d?d?1?1to see which password candidates are generated and if they look correctly (pipe the output to something like the unix head command and/or a filter like the unix grep command to make it more clear what is going on)
From your description of the examples it is also not clear if it is always "G", "g" and "a" or if it could be any upper- or lower-case letter. It's also not clear if the letters are the same at the start and ending or if they could be completely different, like this: YO4512859hi
Therefore, my suggestion is to make sure that you have a clear picture about what the "rules" of the password candidates are and use them correctly within the mask: https://hashcat.net/wiki/doku.php?id=mask_attack (see also custom characters defined with -1,-2,-3,-4 and used within the mask ?1,?2,?3,?4)
Of course the ethereum algo is a pretty slow one, so you should make the mask very specific and test only what needs to be tested (therefore using ?l and ?u and even ?d might not be the best thing to do here... if you can restrict the charsets even more to the characters you think were used)