Bitcoin QT Asking For Passphrase to Receive BTC

[seafarer124]

Why does BTC QT ask for "passphrase" to generate a new receive address?

I have only used two address to date.

I only thought "passphrase" was needed to send not receive BTC.

Thanks for any help.

[jackjack]

Because in your wallet the private keys are encrypted with your passphrase
So when you generate a private key, bitcoin-qt needs the passphrase so that it can write it (after encrypting it with the passphrase) in the wallet

[Stephen Gornick]

I only thought "passphrase" was needed to send not receive BTC.

The logic for that is that you don't want a key added to your wallet without your explicit permission.

[Abdussamad]

Because in your wallet the private keys are encrypted with your passphrase
So when you generate a private key, bitcoin-qt needs the passphrase so that it can write it (after encrypting it with the passphrase) in the wallet

Does it generate a new key for the key pool right away?

[jackjack]

Because in your wallet the private keys are encrypted with your passphrase
So when you generate a private key, bitcoin-qt needs the passphrase so that it can write it (after encrypting it with the passphrase) in the wallet

Does it generate a new key for the key pool right away?

Yes, actually the new address is not generated, it takes an unused key from the pool to give it to you as a "new" one
Then to keep the same pool size it generates a pool key

[gmaxwell]

The logic for that is that you don't want a key added to your wallet without your explicit permission.

No, it's a bug and it's already fixed in git and will be in 0.9.  (It's pulling keys from the keypool in any case, after the fix it will only prompt if the keypool becomes empty)

I was shocked that it had gone unreported for so long!