Branch: refs/heads/intwaddrmgr
Home: https://github.com/btcsuite/btcwallet
Commit: 8f9f53a618ea8b6e6176977c8f05a083f434e81b
https://github.com/btcsuite/btcwallet/commit/8f9f53a618ea8b6e6176977c8f05a083f434e81b
Author: Dave Collins <[email protected]>
Date: 2015-03-02 (Mon, 02 Mar 2015)
Changed paths:
M btcwallet.go
M chain/chain.go
M chainntfns.go
M config.go
M createtx.go
M createtx_test.go
M rescan.go
M rpcserver.go
M snacl/snacl.go
M waddrmgr/common_test.go
M waddrmgr/manager.go
M waddrmgr/manager_test.go
M wallet.go
A walletsetup.go
Log Message:
-----------
Switch to new waddrmgr package
This commit converts the wallet to use the new secure hierarchical
deterministic wallet address manager package as well as the walletdb
package.
The following is an overview of modified functionality:
- The wallet must now be created before starting the executable
- A new flag --create has been added to create the new wallet using wizard
style question and answer prompts
- Starting the process without an existing wallet will instruct now
display a message to run it with --create
- Providing the --create flag with an existing wallet will simply show an
error and return
In addition the snacl package has been modified to return the memory after
performing scrypt operations to the OS.
Previously a runtime.GC was being invoked which forced it to release the
memory as far as the garbage collector is concerned, but the memory was
not released back to the OS immediatley. This modification allows the
memory to be released immedately since it won't be needed again until the
next wallet unlock.
Commit: b44f48882fb27e4dda1c48b906e24dd58ab90b93
https://github.com/btcsuite/btcwallet/commit/b44f48882fb27e4dda1c48b906e24dd58ab90b93
Author: Dave Collins <[email protected]>
Date: 2015-03-02 (Mon, 02 Mar 2015)
Changed paths:
M walletsetup.go
Log Message:
-----------
Add conversion from legacy keystore if it exists.
Commit: 45a33353b0ec368a8cd84e5d4a9350c163a12604
https://github.com/btcsuite/btcwallet/commit/45a33353b0ec368a8cd84e5d4a9350c163a12604
Author: Javed Khan <[email protected]>
Date: 2015-03-02 (Mon, 02 Mar 2015)
Changed paths:
M walletsetup.go
Log Message:
-----------
Turn echo off when reading passwords
Commit: e2a7f16a9b8d9ce6e8072683672d8f5c2f00a676
https://github.com/btcsuite/btcwallet/commit/e2a7f16a9b8d9ce6e8072683672d8f5c2f00a676
Author: Josh Rickmar <[email protected]>
Date: 2015-03-02 (Mon, 02 Mar 2015)
Changed paths:
M rpcserver.go
M wallet.go
Log Message:
-----------
Implement several btcd RPCs in wallet as well.
Wallet should handle these so that wallet clients don't end up
creating requests to btcd about the latest processed block, which is
not the same as wallet's most recently processed block.
By providing wallet clients with this info, we avoid a race where the
client thinks wallet has processed N blocks, but in fact is still
synced to N-1 (and perhaps currently processing transactions from
block N). This can cause unexpected results for many of the
bitcoind-compatible RPC APIs due to their reliance on number of
confirmations, rather than using absolute block heights.
Commit: 5c7f4f6bd7929a5c06b27aa2b613efdbc6852e5b
https://github.com/btcsuite/btcwallet/commit/5c7f4f6bd7929a5c06b27aa2b613efdbc6852e5b
Author: Josh Rickmar <[email protected]>
Date: 2015-03-02 (Mon, 02 Mar 2015)
Changed paths:
M rpcserver.go
M wallet.go
Log Message:
-----------
Use the correct synced block when calculating confs.
This was previously using the most recently notified (by the chain
package) block, but transaction processing from this block may not be
finished yet. Using this block's height to calculate the number of
confirmations is therefore incorrect, and can result in every RPC
handler missing transactions or returning transactions from the wrong
block.
Compare:
https://github.com/btcsuite/btcwallet/compare/2d194a4e290d...5c7f4f6bd792
