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.
- Export
MultichainNetworkControllerGetNetworksWithTransactionActivityByAccountsAction(#8391)
- Bump
@metamask/keyring-controllerfrom^25.3.0to^25.4.0(#8665) - Bump
@metamask/accounts-controllerfrom^37.1.0to^38.0.0(#8325, #8363, #8665) - Bump
@metamask/controller-utilsfrom^11.19.0to^11.20.0(#8344) - Bump
@metamask/messengerfrom^1.0.0to^1.2.0(#8364, #8373, #8632) - Bump
@metamask/base-controllerfrom^9.0.1to^9.1.0(#8457) - Bump
@metamask/keyring-apifrom^21.6.0to^23.1.0(#8464, #8647) - Bump
@metamask/keyring-internal-apifrom^10.0.0to^11.0.1(#8464, #8584, #8647) - Bump
@metamask/network-controllerfrom^30.0.1to^30.1.0(#8636)
- Bump
@metamask/accounts-controllerfrom^37.0.0to^37.1.0(#8317) - Bump
@metamask/base-controllerfrom^9.0.0to^9.0.1(#8317) - Bump
@metamask/messengerfrom^0.3.0to^1.0.0(#8317) - Bump
@metamask/network-controllerfrom^30.0.0to^30.0.1(#8317) - Bump
@metamask/keyring-apifrom^21.5.0to^21.6.0(#8259)
- Bump
@metamask/accounts-controllerfrom^36.0.1to^37.0.0(#8140)
- Bump
@metamask/accounts-controllerfrom^36.0.0to^36.0.1(#7996) - Bump
@metamask/network-controllerfrom^29.0.0to^30.0.0(#7996) - Bump
@metamask/controller-utilsfrom^11.18.0to^11.19.0(#7995)
- Bump
@metamask/accounts-controllerfrom^35.0.2to^36.0.0(#7897) - Bump
@metamask/keyring-apifrom^21.0.0to^21.5.0(#7857) - Bump
@metamask/keyring-internal-apifrom^9.0.0to^10.0.0(#7857)
- Bump
@metamask/accounts-controllerfrom^35.0.1to^35.0.2(#7642) - Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642)
- Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511) - Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
- The dependencies moved are:
@metamask/accounts-controller(^35.0.1)@metamask/network-controller(^28.0.0)
- In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
- For example, this scenario would be valid: a client relies on
@metamask/controller-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583)
- Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202)
- BREAKING: Use new
Messengerfrom@metamask/messenger(#6543)- Previously,
MultichainNetworkControlleraccepted aRestrictedMessengerinstance from@metamask/base-controller.
- Previously,
- BREAKING: Metadata property
anonymousrenamed toincludeInDebugSnapshot(#6543) - BREAKING: Bump
@metamask/accounts-controllerfrom^33.0.0to^34.0.0(#6962) - BREAKING: Bump
@metamask/network-controllerfrom^24.0.0to^25.0.0(#6962) - Bump
@metamask/base-controllerfrom^8.4.2to^9.0.0(#6962)
- Bump
@metamask/base-controllerfrom^8.4.1to^8.4.2(#6917) - Bump
@metamask/network-controllerfrom^24.2.2to^24.3.0(#6883)
- Bump
@metamask/utilsfrom^11.8.0to^11.8.1(#6708) - Bump
@metamask/base-controllerfrom^8.4.0to^8.4.1(#6807) - Bump
@metamask/controller-utilsfrom^11.14.0to^11.14.1(#6807)
- Add two new controller state metadata properties:
includeInStateLogsandusedInUi(#6525) - Add Solana Devnet support to multichain network controller (#6670)
- Bump package version to v1.0 to mark stabilization (#6676)
- Bump
@metamask/controller-utilsfrom^11.12.0to^11.14.0(#6620, #6629) - Bump
@metamask/base-controllerfrom^8.1.0to^8.4.0(#6355, #6465, #6632) - Bump
@metamask/keyring-apifrom^20.1.0to^21.0.0(#6560) - Bump
@metamask/keyring-internal-apifrom^8.1.0to^9.0.0(#6560) - Bump
@metamask/utilsfrom^11.4.2to^11.8.0(#6588)
- BREAKING: Bump peer dependency
@metamask/accounts-controllerfrom^32.0.0to^33.0.0(#6345) - Bump
@metamask/base-controllerfrom^8.0.1to^8.1.0(#6284) - Bump
@metamask/controller-utilsfrom^11.11.0to^11.12.0(#6303) - Bump accounts related packages (#6309)
- Bump
@metamask/keyring-apifrom^20.0.0to^20.1.0 - Bump
@metamask/keyring-internal-apifrom^8.0.0to^8.1.0
- Bump
- Bump
@metamask/keyring-apifrom^19.0.0to^20.0.0(#6248) - Bump
@metamask/keyring-internal-apifrom^7.0.0to^8.0.0(#6248)
- BREAKING: Bump peer dependency
@metamask/accounts-controllerfrom^31.0.0to^32.0.0(#6171) - Bump
@metamask/keyring-apifrom^18.0.0to^19.0.0(#6146) - Bump
@metamask/keyring-internal-apifrom^6.2.0to^7.0.0(#6146)
- Bump
@metamask/controller-utilsfrom^11.10.0to^11.11.0(#6069) - Bump
@metamask/utilsfrom^11.2.0to^11.4.2(#6054)
- Use
scopesinstead ofaddressto retrieve the network of an account. (#6072)
- BREAKING: Bump peer dependency
@metamask/accounts-controllerto^31.0.0(#5999) - BREAKING: Bump peer dependency
@metamask/network-controllerto^24.0.0(#5999) - Bump
@metamask/controller-utilsto^11.10.0(#5935)
- BREAKING: Bump
@metamask/accounts-controllerpeer dependency to^30.0.0(#5888) - Bump
@metamask/keyring-apidependency from^17.4.0to^18.0.0(#5871) - Bump
@metamask/keyring-internal-apidependency from^6.0.1to^6.2.0(#5871) - Bump
@metamask/controller-utilsto^11.9.0(#5812)
- BREAKING: bump
@metamask/accounts-controllerpeer dependency to^29.0.0(#5802) - Bump
@metamask/controller-utilsto^11.8.0(#5765)
- BREAKING: Bump peer dependency
@metamask/accounts-controllerto^28.0.0(#5763) - Bump
@metamask/base-controllerfrom ^8.0.0 to ^8.0.1 (#5722)
- Updated to restrict
getNetworksWithTransactionActivityByAccountsto EVM networks only while non-EVM network endpoint support is being completed. Full multi-chain support will be restored in the coming weeks (#5677) - Updated network activity API requests to have batching support to handle URL length limitations, allowing the controller to fetch network activity for any number of accounts (#5752)
- Add method
getNetworksWithTransactionActivityByAccountsto fetch active networks for multiple accounts in a single request (#5551) - Add
MultichainNetworkServicefor handling network activity fetching (#5551) - Add types for network activity state and responses (#5551)
- Updated state management for network activity (#5551)
- Add Testnet asset IDs as constants (#5589)
- Add Network specific decimal values and ticker as constants (#5589)
- Add new method
removeNetworkthat acts as a proxy to remove an EVM network from the@metamask/network-controller(#5516)
- The
AVAILABLE_MULTICHAIN_NETWORK_CONFIGURATIONSnow includes non-EVM testnets (#5589) - Bump
@metamask/keyring-api"from^17.2.0to^17.4.0(#5565)
- Fix the condition to update the active network based on the
AccountsController:selectedAccountChangeevent (#5642)
- BREAKING: Bump peer dependency
@metamask/accounts-controllerto^27.0.0(#5507) - BREAKING: Bump peer dependency
@metamask/network-controllerto^23.0.0(#5507)
- BREAKING: Bump
@metamask/accounts-controllerpeer dependency to^26.0.0(#5439) - BREAKING: Bump
@metamask/accounts-controllerpeer dependency to^25.0.0(#5426)
- Bump
@metamask/keyring-api"from^17.0.0to^17.2.0(#5366) - Bump
@metamask/utilsfrom^11.1.0to^11.2.0(#5301)
- Add
MultichainNetworkController:stateChangeto list of subscribableMultichainNetworkControllermessenger events (#5331)
- Initial release (#5215)
- Handle both EVM and non-EVM network and account switching for the associated network.
- Act as a proxy for the
NetworkController(for EVM network changes).