|
Title: Bitcoin QT Asking For Passphrase to Receive BTC Post by: seafarer124 on August 31, 2013, 12:15:15 PM 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. Title: Re: Bitcoin QT Asking For Passphrase to Receive BTC Post by: jackjack on August 31, 2013, 12:38:41 PM 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 Title: Re: Bitcoin QT Asking For Passphrase to Receive BTC Post by: Stephen Gornick on August 31, 2013, 07:16:40 PM 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. Title: Re: Bitcoin QT Asking For Passphrase to Receive BTC Post by: Abdussamad on September 01, 2013, 03:16:29 AM 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? Title: Re: Bitcoin QT Asking For Passphrase to Receive BTC Post by: jackjack on September 01, 2013, 09:35:14 AM 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? Then to keep the same pool size it generates a pool key Title: Re: Bitcoin QT Asking For Passphrase to Receive BTC Post by: gmaxwell on September 01, 2013, 10:15:04 AM 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 (https://github.com/bitcoin/bitcoin/commit/20469d83dd2fd7d8efacf94f017b926be7c92e63) 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! |