All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- 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:
createNewVaultAndKeychainsubmitPasswordsubmitEncryptionKeyaddNewAccountremoveAccount
- They now all return the full state, just as they did in earlier versions.
8.0.0 [DEPRECATED]
- 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
memStoreasencryptionKeyandencryptionSalt. The salt is used to verify that the key matches the vault being decrypted. - If the
cacheEncryptionKeyoption is enabled, the encryption key and salt get cached in thememStorewhenever the password is submitted. - The encryption key can be submitted with the new method
submitEncryptionKey. - The
unlockKeyringsmethod now accepts additional parameters for the encryption key and salt, though we don't recommend using this method directly.
- BREAKING: Update minimum Node.js version to v14 (#146)
- BREAKING:: Remove password parameter from
persistAllKeyringsandcreateFirstKeyTree(#154)- The password or encryption key must now be set already before these method are called. It is set by
createNewVaultAndKeychain,createNewVaultAndRestore, andsubmitPassword/submitEncryptionKey. - This change was made to reduce redundant state changes.
- The password or encryption key must now be set already before these method are called. It is set by
- Fix a typo in the duplicate account import error (#153)
createNewVaultAndRestorenow accepts a seedphrase formatted as an array of numbers (#138)
- Fix breaking change in
addNewKeyringfunction 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.
- BREAKING: Bump eth-hd-keyring to latest version (#132)
- When calling the
addNewKeyringmethod, an options object can no longer be passed containing anumberOfAccountsproperty without also including amnemonic. 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 the
- When calling
createNewVaultAndKeychainall keyrings are cleared first thing (#129) - Validate user imported seedphrase across all bip39 wordlists (#77)