eth-keyring-controller - npm Package Versions

[9.0.0] [DEPRECATED]

Added

• Add support for keyring init method (#163).
  • If a keyring has an init method, it will be called automatically upon construction. It is called with await, so it can be asynchronous.

Changed

• BREAKING: Replace constructor option and public property keyringTypes with keyringBuilders (#163).
  • The constructor now takes keyring builder functions rather than classes. Each builder function should return a keyring instance when called, and it must have a type string property set to the keyring type name. See the newly exported keyringBuilderFactory function for an example. The builder functions must be synchronous; use an init method for asynchronous initialization steps.
• BREAKING: KeyringController is now a named export instead of a default export (#163).
• BREAKING: Update @metamask/eth-simple-keyring from v4 to v5 (#171).
  • This keyring type is included as a default. If you are using this keyring API directly, see the @metamask/eth-simple-keyring release notes for details on required changes.
• BREAKING: Replace getKeyringClassForType method with getKeyringBuilderForType (#163).
• BREAKING: Update @metamask/eth-hd-keyring to v5 (#177)
  • This keyring type is included as a default. If you are using this keyring API directly, see the @metamask/eth-hd-keyring release notes for details on required changes.
• BREAKING: Require support for ES2020 (#177, #180)
  • As a result of some dependency updates made in this release, this package now requires ES2020 support. If using this package in an environment that does not support ES2020 completely, consider investigating these two dependency changes and transpiling any packages using ES2020 syntax.
• Update @metamask/eth-sig-util to v5 (#180)
• Update minimum supported version of @metamask/browser-passworder from v4.0.1 to v4.0.2 (#182)
• Remove bip39 dependency (#179)

Fixed

• Fix support for asynchronous addAccounts HD Keyring method (#176)
  • This method was asynchronous, but was called synchronously. Currently the method does not do anything asynchronous so this should have no functional impact, but this ensures any future errors or asynchronous steps added to that method work correctly in the future.

[8.1.0]

Changed

• Allow deserializing vaults with unrecognized keyrings (#169)
  • When deserializing a vault with an unrecognized keyring, the controller will no longer crash. The unrecognized keyring vault data will be preserved in the vault for future use, but will otherwise be ignored.

[8.0.1]

Fixed

• Restore full state return value (#161)
  • Some methods were accidentally changed in v8.0.0 to return nothing, where previously they returned the full KeyringController state.
  • The affected methods were:
    • createNewVaultAndKeychain
    • submitPassword
    • submitEncryptionKey
    • addNewAccount
    • removeAccount
  • They now all return the full state, just as they did in earlier versions.

[8.0.0] [DEPRECATED]

Added

• Allow login with encryption key rather than password (#152)
  • This is required to support MetaMask extension builds using manifest v3.
  • This is enabled via the option cacheEncryptionKey.
  • The encryption key and salt have been added to the memStore as encryptionKey and encryptionSalt. The salt is used to verify that the key matches the vault being decrypted.
  • If the cacheEncryptionKey option is enabled, the encryption key and salt get cached in the memStore whenever the password is submitted.
  • The encryption key can be submitted with the new method submitEncryptionKey.
  • The unlockKeyrings method now accepts additional parameters for the encryption key and salt, though we don't recommend using this method directly.

Changed

• BREAKING: Update minimum Node.js version to v14 (#146)
• BREAKING:: Remove password parameter from persistAllKeyrings and createFirstKeyTree (#154)
  • The password or encryption key must now be set already before these method are called. It is set by createNewVaultAndKeychain, createNewVaultAndRestore, and submitPassword/submitEncryptionKey.
  • This change was made to reduce redundant state changes.

Fixed

• Fix a typo in the duplicate account import error (#153)

[7.0.2]

Fixed

• createNewVaultAndRestore now accepts a seedphrase formatted as an array of numbers (#138)

[7.0.1]

Fixed

• Fix breaking change in addNewKeyring function that was accidentally introduced in v7.0.0 (#136)
  • We updated the method such that keyrings were always constructed with constructor arguments, defaulting to an empty object if none were provided. But some keyrings (such as the QR Keyring) relied upon the options being undefined in some cases.

[7.0.0]

Added

• Add forget Keyring method for some hardware devices (#124)
• Add @lavamoat/allow-scripts (#109)

Changed

• BREAKING: Bump eth-hd-keyring to latest version (#132)
  • When calling the addNewKeyring method, an options object can no longer be passed containing a numberOfAccounts property without also including a mnemonic. Not adding any option argument will result in the generation of a new mnemonic and the addition of 1 account derived from that mnemonic to the keyring.
• When calling createNewVaultAndKeychain all keyrings are cleared first thing (#129)
• Validate user imported seedphrase across all bip39 wordlists (#77)