Josh Rickmar 3dc9b175d0 Use correct hash algorithm for chained addresses. ... btcwallet originally correctly copied the behavior of armory when chaining new private keys off the previous private key, but this regressed in commit e8265eca41 with a switch from double sha256 to a single sha256. This change reverts the behavior (using the clearly-named function btcwire.DoubleSha256) to match armory's and old btcwallet's address chaining algorithm. If you have flipped the switch to use btcwallet on mainnet, any newly generated addresses created for the keypool after Jan 6, 2014 (the date the regression was committed) should be backed up with dumpprivkey (using btcctl) and a new wallet backup should be made of your current wallet file (~/.btcwallet/mainnet/wallet.bin on unix) to avoid the possibility of losing any real money.		2014-01-15 18:25:19 -05:00
..
wallet.go	Use correct hash algorithm for chained addresses.	2014-01-15 18:25:19 -05:00
wallet_test.go	Fix tests for new NewWallet func signature.	2014-01-15 18:23:02 -05:00