There is an article in the help explaining how to import keys like vanity keys:
https://multibit.org/en/help/v0.5/help_importASingleKey.html
You can specify a date (the 'birthdate' of the private key) and it will only rescan from that date. Actually it scans from the last checkpoint before that date which can be a couple of weeks beforehand.
When you download blocks the blocks are bloom filtered so you are only downloading a tiny fraction of the blockchain.
Topic: multibit - rescan ALL BLOCKCHAIN after importing key - wtf madness is it?... (Read 863 times)
December 12, 2013, 09:14:04 AM
December 11, 2013, 11:03:25 AM
I generated/imported a vanity address and for some reason not only it triggered a blockchain rescan, but FULL rescan, starting with 2009. Can we have a feature to:
1. Optionally tell client to not rescan blockchain when importing address? This is useful when we have a known fresh address where we don't expect to see balance
2. If it rescans, then at least scan from the client default checkpoint block, not download the whole whatever petabytes is in the blockchain now. That's the whole reason I'm using multibit instead of reference client - to avoid having to manage the full blockchain
1. Optionally tell client to not rescan blockchain when importing address? This is useful when we have a known fresh address where we don't expect to see balance
2. If it rescans, then at least scan from the client default checkpoint block, not download the whole whatever petabytes is in the blockchain now. That's the whole reason I'm using multibit instead of reference client - to avoid having to manage the full blockchain
Jump to: