Josh Rickmar 5edd01e8a5 Unmark addresses as requiring private keys next unlock. ... The flag marking chained addresses as needing private keys be generated on the next wallet unlock was not being correctly unset after creating and encrypting the private key. After serializing/deserializing the wallet, on next unlock, recreating missing private keys would begin too early in the chain and fail due to trying to encrypt an already encrypted address. This change correctly unsets the flag and bumps the version so a special case can be created for ignoring duplicate encryption attempts when reading an old wallet file. Tests have also been added to the chained pubkey test to test for this error case.		2014-02-04 10:37:28 -05:00
..
wallet.go	Unmark addresses as requiring private keys next unlock.	2014-02-04 10:37:28 -05:00
wallet_test.go	Unmark addresses as requiring private keys next unlock.	2014-02-04 10:37:28 -05:00