<p>I am not familiar with digibyte's wallet implementation specifically, but I can probably shed some general light:</p>

<p>Your passphrase is not stored in the wallet.dat - the passphrase is the <em>encryption key</em> that can be used to decrypt the wallet.dat. The wallet.dat itself stores private keys that can be used to sign transactions with the associated addresses.</p>

<p>When you run JTR or hashcat on the wallet.dat, you are brute forcing the passphrase itself to gain access to the private keys inside the wallet (trying to find a passphrase that when used as a decryption key is successfully able to decrypt the wallet)</p>

<p>Briefly looking at the digibyte core wallet, the wallet.dat appears to be in a standard format just like for any other wallet based on Bitcoin Core. You should start here if you want to know more about what information is stored inside the wallet.dat and how (look under Bitcoin Core): <a href="https://en.bitcoin.it/wiki/Wallet" rel="nofollow noreferrer">https://en.bitcoin.it/wiki/Wallet</a></p>

<p>If Bitcoin2John and hashcat don't work on the wallet.dat, this is probably due to minor differences in storage, but it should be fundamentally the same.</p>

CC BY-SA 3.0
2018-01-02T22:55:07.443Z
2018-01-02T22:55:07.443Z
mxbi
<p><br/>
I recently invested in digibyte.<br/>
As someone of IT-security field, I'd love to know how the passphrase is stored in digibytes wallet.dat.<br/>
The <a href="https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/run/bitcoin2john.py" rel="nofollow noreferrer">Bitcoin2John</a> doesn't work on it and hashcat, too, has no support for the wallet.<br/>
I couldn't find any information on how storage is done, so I'm asking you.<br/>
Best wishes and thanks in advance</p>

<altcoin><wallet-security><passphrase>
Digibyte Wallet Hash
Morpheus
# Digibyte Wallet Hash

(Asked by: username_0 on 2018-01-02)

I recently invested in digibyte.  
As someone of IT-security field, I'd love to know how the passphrase is stored in digibytes wallet.dat.  
The [Bitcoin2John](https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/run/bitcoin2john.py) doesn't work on it and hashcat, too, has no support for the wallet.  
I couldn't find any information on how storage is done, so I'm asking you.  
Best wishes and thanks in advance

**Tags:** altcoin, wallet-security, passphrase


---

## 1 answers

### Answer by username_1 on 2018-01-02. Score: 0 | Accepted answer

I am not familiar with digibyte's wallet implementation specifically, but I can probably shed some general light:

Your passphrase is not stored in the wallet.dat - the passphrase is the *encryption key* that can be used to decrypt the wallet.dat. The wallet.dat itself stores private keys that can be used to sign transactions with the associated addresses.

When you run JTR or hashcat on the wallet.dat, you are brute forcing the passphrase itself to gain access to the private keys inside the wallet (trying to find a passphrase that when used as a decryption key is successfully able to decrypt the wallet)

Briefly looking at the digibyte core wallet, the wallet.dat appears to be in a standard format just like for any other wallet based on Bitcoin Core. You should start here if you want to know more about what information is stored inside the wallet.dat and how (look under Bitcoin Core): <https://en.bitcoin.it/wiki/Wallet>

If Bitcoin2John and hashcat don't work on the wallet.dat, this is probably due to minor differences in storage, but it should be fundamentally the same.


---

