-
Notifications
You must be signed in to change notification settings - Fork 35.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitcoin-QT 0.8.1 Windows client freezing when importing private-key. #2389
Comments
Can you try what happens with this, when you are fully synced with the network and report back. |
is something that's done through the
is not in synch, that the client is prevented from crashing in regards to this issue. Also it
"The private key for [bitcoinaddress] is already imported."
Forgive me for this poorly formatted message, I'm unfamiliar with the github issue system. |
Hah - I managed to accidentally close the issue as well - well I reopened it now - I need input from others, please. |
Importing a private key does immediately start a rescan, which when executed through the debug console will make the UI unresponsive until it completes. This is so the new balance will be shown correctly after importing a key. A progress or busy indicator would be useful when Bitcoin is performing an operation, even if started via RPC, so users don't shut down Bitcoin-Qt while it is performing some database operation. There is an option that allows you to disable the automatic rescan, if for example you have many keys to import before you wish the rescan to happen. importprivkey [label] [rescan=true] |
Same problem. Windows Vista 1 private key ! force "close program" Looking for newer... Nope. Same problem. Locked up after the third import. So the solution is to wait? Is there any other way to import a batch of addresses? This seems awfully inefficient for a merchant. |
After importing a new key, the blockchain is rescanned for missing transactions. This may take 10 minutes or so, depending on hardware. You can disable rescanning by passing an extra 'false' argument to the RPC call, so for example
I've also been working on an "entire wallet" key export/import function, which would export all wallet keys to a file, or import such a file at once. May I ask why you need to import many keys, though? |
So I've imported the private keys per sipa's method and while the solution worked perfectly I later realized that the addresses show up differently in my wallet that I had expected... they show up under the "addresses" tab. ;-) Perhaps I am not doing what I should be doing. My entire purpose is to create a new public address for each transaction the same way mt gox appears to do each time I deposit btc into my account. If the key system is any type of modulus system is it not true that a single private key could have many public solutions? If that is the case... how to I create a batch new public keys from the "original" private key within or outside my wallet? I would like to create: 1publicaddress12345 I expected these to show up under "Receive" so I'm now thinking that I wanted to create new public addresses from the existing key instead of new keys which seem to be called addresses. Is this right? My solution was to use vanitygen + import the newly pressed keys. But I don't think I want/need all the private keys. Thoughts? Better place to ask? (I don't need vanity addresses, just unique ones with a zero balance). |
Every private key has exactly one corresponding public key and address. But why are you importing keys at all? Just do a getnewaddress every time you need a new receive address? |
"Just do a getnewaddress every time you need a new receive address" This is the information I needed, thank you. |
Closing this as it appears to be sufficiently answered. |
how do i get my coins if i closed because i thought it froze |
Could the reason be that the client is rescanning ? I didn't ask it to rescan.
The text was updated successfully, but these errors were encountered: