-rescan likely did nothing at all. It goes through the blockchain to find transactions that are missing from your wallet. It is only very rarely needed (like when you manually changed things in wallet.dat).
-reindex throws away the block chain index and chain state (the database of all unspent transaction outputs), and rebuilds those from scratch. It is ...
Press Cmd + Shift + G
Edit bitcoin.conf with TextEdit
Add this line:
Save it, then run Bitcoin-qt.
After you the rescan ends and you quit don't forget to revert the bitcoin.conf
Right click Bitcoin-qt
Choose "Show package contents"
Go to Contents/MacOS/...
Yes. txindex=1 is not related to the wallet and the wallet does not know about the txindex nor does it care. What the wallet really cares about is transaction output information and which transactions are related to addresses stored in the wallet. The txindex does not store any of that information, all it stores is the location of each transaction identified ...
This answer might help: https://bitcoin.stackexchange.com/a/1251/11026
The gist is that a -rescan was needed, when you were restoring an older backed up wallet that didn't have all the transactions in your current blockchain reflected. Basically the client then goes through your blockchain to see if there are any transactions that affect your wallet.
To supplement George's answer:
It would help if you would clarify what you mean by "crash" and describe exactly what happens. (To many people, "crash" means a segfault or similar abnormal termination, but it sounds like that's not what you mean.)
If the issue is that the program appears unresponsive, this is normal: it's a well-known annoyance (perhaps ...
Calling importaddress will rescan the whole blockchain in default according to bitcoin.org
Set rescan parameter to false to not rescan the block database
(rescanning can be performed at any time by restarting Bitcoin Core
with the -rescan command-line argument). Rescanning may take several
importaddress "address" (...
Generally, the wallet shipped with Bitcoin Core only keeps copies of any transactions that directly involve the wallet. When you import a key, your node scans the entire blockchain to see if any transactions involved that key.
A pruned node has processed the whole blockchain, but only keeps the tail end of the data. This means that when you import a private ...
No, you essentially have to do exactly that: test the block filter for each address that might have gotten used by your wallet. That might not be quite as bad as you seem to think, though.
Deterministic wallet backups usually come with a master secret and the derivation path. If you have both these pieces of information, only one derivation path needs to be ...
I don't think so. If the transaction is removed from the blockchain, it means it was never confirmed.
Thus the UTXO is still unspent, and should still be in your wallet. Are you sure your wallet is updated?
Maybe see if you can find the adresses by executing
listreceivedbyaddress 0 true
Or, if that doesn't show anything, dump all the private keys of your ...
The QT terminal (RPC) rescan option will be available in 0.16 (not release by the time of writing). https://github.com/bitcoin/bitcoin/pull/7061
Manual rescans should generally not be required, though, if you are missing transactions in an old wallet, the rescan may help.
In Core < 0.16 you need to rescan either by startup argument or by a configuration ...
No additional rescan is required in that case.
Though there is a little bug in Bitcoin-Qt: the balance will not get properly updated if you import a private keys where you already have a watch-only script.
Bitcoind (listtransactions, getbalance, etc.) are not affected.
The only way to avoid a full resync is to make sure your backup contains the blockchain as it was when you made the backup; not just your wallet.
Then the core should only need to update with any more recent transactions.
Here is a good article on the subject: http://bitzuma.com/posts/moving-the-bitcoin-core-data-directory/
And here it is from the Wiki:...
Importing a private key causes a rescan (so that the correct balance will be displayed in your wallet once the import is through), which can make the UI unresponsive until it completes, when executed through the debug console.
Importing your key(s) with rescan set to false should fix this:
importprivkey bitcoinprivkey label rescan=false