v1.0.2 - Dependency Updates and Browser Build

• Updated dependencies to latest, added browser build, PR #157

Included Source Files

Source files from the src folder are now included in the distribution build. This allows for a better debugging experience in debug tools like Chrome DevTools by having working source map references to the original sources available for inspection.

v1.0.1 - Bugfix Release

• Fixed a browser issue in Wallet.fromV3() and Wallet.toV3() triggered when using web bundlers using Buffer v4 shim (Webpack 4),
  see PR #135

v0.6.5 - Crypto Update (ethereum-cryptography)

• Replaced native hdkey dependency with ethereum-cryptography that doesn't require native dependency compiling, PR #130

v1.0.0 - TypeScript Release

This is the first TypeScript release on the library (thanks @the-jackalope for the rewrite! ❤️), see PR #93 for the main PR here. The release comes with various breaking changes.

Libray Import / API Documentation

The way submodules are exposed has been changed along the TypeScript rewrite and you will likely have to update your imports. Here is an example for the hdkey submodule:

Node.js / ES5:

const { hdkey } = require('ethereumjs-wallet')

ESM / TypeScript:

import { hdkey } from 'ethereumjs-wallet'

See README for examples on the other submodules.

Together with the switch to TypeScript the previously static documentation has been automated to now being generated with TypeDoc to reflect all latest changes, see PR #98. See the new docs for an overview on the TypeScript based API.

API Changes

The API of the library hasn't been changed intentionally but has become more strict on type input by the explcit type definitions from the TypeScript code in function signatures together with the introduction of the ethereumjs-util v7 library within the Wallet library, which behaves more strict on type input on the various utility functions.

This leads to cases where some input - while not having been the intended way to use the library - might have been worked before through implicit type conversion and is now not possible any more.

One example for this is the Wallet.fromPublicKey() function, here is the old code of the function:

Wallet.fromPublicKey = function(pub, nonStrict) {
  if (nonStrict) {
    pub = ethUtil.importPublic(pub)
  }
  return new Wallet(null, pub)
}

and here the new TypeScript code:

public static fromPublicKey(publicKey: Buffer, nonStrict: boolean = false): Wallet {
  if (nonStrict) {
    publicKey = importPublic(publicKey)
  }
  return new Wallet(undefined, publicKey)
}

This function worked in the v0.6.x version also with passing in a string, since the ethereumjs-util v6 importPublic method converted the input implicitly to a Buffer, the v1.0.0 version now directly enforces the fromPublicKey input to be a Buffer first hand.

There will likely be more cases like this in the code since the type input of the library hasn't been documented in the older version. So we recommend here to go through all your function signature usages and see if you uses the correct input types. While a bit annoying this is a one-time task you will never have to do again since you can now profit from the clear TypeScript input types being both documented and enforced by the TypeScript compiler.

Pure JS Crypto Dependencies

This library now uses pure JS crypto dependencies which doesn't bring in the need for native compilation on installation. For scrypt key derivation scrypt-js from @ricmoo is used (see PR #125).

For BIP-32 key derivation the new ethereum-cryptography library is used which is a new Ethereum Foundation backed and formally audited libray to provide pure JS cryptographic primitives within the Ethereum ecosystem (see PR #128).

Removed ProviderEngine

Support for Provider Engine has been removed for security reasons, since the package is not very actively maintained and superseded by json-rpc-engine.

If you need the removed functionality, it should be relatively easily possible to do this integration by adopting the code from provider-engine.ts.

See also: PR #117

Other Changes

Bug Fixes

• Fixes a bug where salt, iv and/or uuid options - being supplied as strings to Wallet.toV3() - could lead to errors during encryption and/or output that could not be decrypted, PR #95

Refactoring & Maintenance

• ES6 class rewrite, PR #93 (TypeScript PR)
• Added support for Node 12, 13, and 14, upgraded CI provider to use GH Actions in place of Travis, PR #120
• Updated ethereumjs-util dependency from v6 to [v7.0.2](https://github.com/ethereumjs/ethereumjs-util/releases/tag/v7.0.2 (stricter types), PR #126
• Refactored Wallet.deciperBuffer(), PR #82

Development & CI

• Integrated the ethereumjs-config EthereumJS developer configuration standards, PR #93 (TypeScript PR)
• Added org links and Git hooks, PR #88

v0.6.4 - Maintenance Release

This is the last release from the v0.6.x release series. It adds Node 12 compatibility while maintaining compatibilitydown to Node 6. To be able to do so the scrypt.js key derivation library is exchanged with scryptsy. While this solution is backwards-compatible the changed library only provides a pure JS implementation and no native bindings. If you need native performance pin your dependency to v0.6.3 or update to the v1.0.0 library version to be released shortly after this release.

Change Summary:

• v0.6.x back patch: added node v12 support, switched to scryptsy key derivation library (pure JS implementation), PR #114
• Updated hdkey to v1.1.1, PR #87
• Refactored decipherBuffer(), PR #82
• Added more tests for Wallet.fromEthSale(), PR #80

v0.6.3

• Fixed installation errors for certain packaging tools, PR #67
• Remove dependency on crypto.randomBytes and use randombytes package instead, PR #63
• Add comprehensive test coverage for fromV3, PR #62
• Remove excess parameter from decipherBuffer usage, PR #77
• Update dependencies, including a fixed scrypt.js, which should resolve more installation issues, PR #78

v0.6.2 - Bugfix Release

• [PLEASE UPDATE!] Fixes a critical import bug introduced in v0.6.1 accidentally
  changing the import path for the different submodules, see PR #65

v0.6.1

• Added support for vanity address generation, PR #5
• Fixed typo in provider-engine, PR #16
• Accept the true range of addresses for ICAP direct, PR #6
• Switched to babel ES5 build, PR #37
• Improve test coverage (at 88% now), PR #27
• Various dependency updates, PR #25