<p>When you encrypt the wallet, only the private keys are actually being encrypted. You will be prompted to enter your encryption passphrase when the private keys are needed.</p>

<p>Public keys in the keypool, transaction information, and other metadata remain unencrypted because they are either public information or have no effect on the security of your Bitcoin. This means that you will be able to get new addresses (they come from precomputed public keys in the keypool) and receive transactions. It is only when you try to spend any of your Bitcoin or when the keypool runs out that you will need to enter your passphrase.</p>

<hr>

<p>It is actually safer to prompt for the passphrase when needed because then the actually important things that are encrypted (i.e. the private keys) are unencrypted in memory for as little time as possible. This reduces the risk of them being exposed.</p>

CC BY-SA 4.0
2019-08-24T21:14:28.940Z
so I'll be asked for them when, for instance, I make transactions?
Felipe
CC BY-SA 4.0
2019-08-24T21:15:24.967Z
I updated my answer. You will need the passphrase when you try to send Bitcoin or when the keypool runs out.
Ava Chow
CC BY-SA 4.0
2019-08-24T21:13:27.957Z
2019-08-24T21:14:59.507Z
2019-08-24T21:14:59.507Z
Ava Chow
<p>I've just encrypted my <code>wallet.dat</code> file using the <strong>"Settings -> Encrypt Wallet"</strong> menu option.</p>

<p>I then closed the client and re-opened it.</p>

<p>I was expecting to be prompted to put in the wallet password once I reopened the client.</p>

<p>I was asked for no password. I don't understand, what is the point of my having set up a wallet password if I can just use it without unlocking?</p>

<bitcoin-core><security><client><encryption><wallet-security>
Why doesn't the Bitcoin-qt client ask for the Wallet passphrase upon startup?
Felipe
# Why doesn't the Bitcoin-qt client ask for the Wallet passphrase upon startup?

(Asked by: username_0 on 2019-08-24)

I've just encrypted my `wallet.dat` file using the **"Settings -> Encrypt Wallet"** menu option.

I then closed the client and re-opened it.

I was expecting to be prompted to put in the wallet password once I reopened the client.

I was asked for no password. I don't understand, what is the point of my having set up a wallet password if I can just use it without unlocking?

**Tags:** bitcoin-core, security, client, encryption, wallet-security


---

## 1 answers

### Answer by username_1 on 2019-08-24. Score: 2 | Accepted answer

When you encrypt the wallet, only the private keys are actually being encrypted. You will be prompted to enter your encryption passphrase when the private keys are needed.

Public keys in the keypool, transaction information, and other metadata remain unencrypted because they are either public information or have no effect on the security of your Bitcoin. This means that you will be able to get new addresses (they come from precomputed public keys in the keypool) and receive transactions. It is only when you try to spend any of your Bitcoin or when the keypool runs out that you will need to enter your passphrase.

---

It is actually safer to prompt for the passphrase when needed because then the actually important things that are encrypted (i.e. the private keys) are unencrypted in memory for as little time as possible. This reduces the risk of them being exposed.

> **Comments:**
> **username_0**: so I'll be asked for them when, for instance, I make transactions?  
> **username_1**: I updated my answer. You will need the passphrase when you try to send Bitcoin or when the keypool runs out.  

---

