With MultiBit Classic the private key is derived from a random number that is created on your machine.
It is not on the blockchain (otherwise anyone could steal your bitcoin).
Is your wallet encrypted ? i.e. does it have a password set ?
If so then in addition to any backups/ rolling backups you have you should also have an encrypted export of all your private keys.
See:
https://multibit.org/en/help/v0.5/help_fileDescriptions.htmlWhen you create a new address in classic a timestamped expoort of your private keys is saved to disk. It is encrypted with your wallet password. As these are never deleted there can be very useful in recovering wallets.
To use them create anew wallet and then run through the steps in :
https://multibit.org/en/help/v0.5/help_importingPrivateKeys.htmlThank you for your reply jim618. Due to my work schedule I have not yet had enough time to do anything with it just yet.
From what your saying that generation process of "the private key is derived from a random number that is created on your machine." That is very helpful and makes this worth pursuing. Im trying now to narrow the search somewhat as I know when it was disrupted but not when that key is supposed to be created. Do you know the sequence that key creation takes place? When does the key generation happen? and when does it get written to backup? after the coin is confirmed or at the beginning of confirmation process? or when the receiving address is generated beforehand?
At what point in time does MultiBit create that private key will be very helpful...when I created a new receiving address or
after a sum of BTC has been confirmed as received? This would be helpful as I am wondering if the key was not created yet. The interruption happened sometime after the confirmation process started but long before completion. If the key is created
after confirmation then it was not created yet, and I wonder if retrieving or manually entering the receiving address somehow into MultiBit wallet would then have it complete and create the key
IF it works in that sequence. As the process never got that far along yet. On the other-hand if the key is generated by my MultiBit wallet at the same time the receiving address was then I will know I must locate that and that time of creation I know and can then narrow the files to look into. Im trying to narrow down which process to use.
I created the new receiving address, sent that address to payer and after the confirmation process started (it was slow) that is when the interruption occurred. When restarting MultiBit I got "null" and had to reopen wallet which then no longer had the receiving address weather it retrieved from last known key set and deleted the partial confirmation Im not knowledgeable enough to figure that one out...The missing receiving address did not appear even after the blockchain was run again...so no more of the confirmation process started either.
The point in the sequence of MultiBit generation of the key for the newly created receiving address would be helpful. If not yet generated would it be possible with getting the receiving address again and running the blockchain get the confirmation key to generate? Thank you again.