Are 2.0 wallets deterministic when claiming keys?

Started by speedy, October 27, 2015, 11:40:25 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

speedy

#4
Quote from: jcalfee1 on October 28, 2015, 05:19:21 PM
Newly created keys are deterministic.  The old brain keys are not compatible so you need to save your backups...  Improvements to this process is in progress.

Thanks, so when a 1.0 balance is imported, is it transfered to a new address created from that deterministic wallet key? It then shouldnt matter if the wallet backup was made pre or post importing of the 1.0 keys.


jamesc

Quote from: speedy on October 27, 2015, 11:40:25 PM
When keys are imported and claimed, their ownership goes to a new address which is derived from the wallet key (as I understand). So can those private keys be re-generated deterministically from the wallet key? Or after every address import do we have to make a new backup?

Thats what these docs seem to imply:

QuoteAfter importing your accounts and balances, we recommend to make a new backup of your wallet that will then contain access to your newly imported accounts and corresponding balances.

If thats the case then the docs should be more explicit. I wonder if this is where I messed up...

Newly created keys are deterministic.  The old brain keys are not compatible so you need to save your backups...  Improvements to this process is in progress.

sittingduck

If you importers bts 1 account then the keys didn't change. 

speedy

When keys are imported and claimed, their ownership goes to a new address which is derived from the wallet key (as I understand). So can those private keys be re-generated deterministically from the wallet key? Or after every address import do we have to make a new backup?

Thats what these docs seem to imply:

QuoteAfter importing your accounts and balances, we recommend to make a new backup of your wallet that will then contain access to your newly imported accounts and corresponding balances.

If thats the case then the docs should be more explicit. I wonder if this is where I messed up...