Branch: refs/heads/intwaddrmgr
  Home:   https://github.com/btcsuite/btcwallet
  Commit: 130e44c7611c0103b84672f7bc1becf7ab239f04
      
https://github.com/btcsuite/btcwallet/commit/130e44c7611c0103b84672f7bc1becf7ab239f04
  Author: Dave Collins <[email protected]>
  Date:   2015-03-02 (Mon, 02 Mar 2015)

  Changed paths:
    M chain/chain.go
    M chainntfns.go
    M createtx.go
    R keystore/keystore.go
    R keystore/keystore_test.go
    A legacy/keystore/keystore.go
    A legacy/keystore/keystore_test.go
    M rescan.go
    M rpcserver.go
    M wallet.go

  Log Message:
  -----------
  Move keystore to legacy directory.


  Commit: deaf11904b823c8d31bbd1989836bbacd18242f0
      
https://github.com/btcsuite/btcwallet/commit/deaf11904b823c8d31bbd1989836bbacd18242f0
  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


  Commit: 1e7eb1790601d78b0775be1c927dd34ea3727488
      
https://github.com/btcsuite/btcwallet/commit/1e7eb1790601d78b0775be1c927dd34ea3727488
  Author: Dave Collins <[email protected]>
  Date:   2015-03-02 (Mon, 02 Mar 2015)

  Changed paths:
    M walletsetup.go

  Log Message:
  -----------
  Add conversion from legacy txstore if it exists.


  Commit: 7e11db10c82b99dbe06c0b657c27afc3228b7ef7
      
https://github.com/btcsuite/btcwallet/commit/7e11db10c82b99dbe06c0b657c27afc3228b7ef7
  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: 3840c0a8a7e1223831707d78f8d075282c5b7234
      
https://github.com/btcsuite/btcwallet/commit/3840c0a8a7e1223831707d78f8d075282c5b7234
  Author: Dave Collins <[email protected]>
  Date:   2015-03-02 (Mon, 02 Mar 2015)

  Changed paths:
    M snacl/snacl.go

  Log Message:
  -----------
  Return the memory after scrypt 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: d399d2d0ee3a0a920fa26b35eb861b02a6111808
      
https://github.com/btcsuite/btcwallet/commit/d399d2d0ee3a0a920fa26b35eb861b02a6111808
  Author: Josh Rickmar <[email protected]>
  Date:   2015-03-02 (Mon, 02 Mar 2015)

  Changed paths:
    M wallet.go

  Log Message:
  -----------
  Prevent deadlock when changing passphrases.


  Commit: 66a83a50f0856c8f43014467b3eedeee93837de4
      
https://github.com/btcsuite/btcwallet/commit/66a83a50f0856c8f43014467b3eedeee93837de4
  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: 2d194a4e290d13e660d2c8d6c60d01cd00b810dc
      
https://github.com/btcsuite/btcwallet/commit/2d194a4e290d13e660d2c8d6c60d01cd00b810dc
  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/ed46efc16883...2d194a4e290d

Reply via email to