Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: handle multicall revert in
TokenBalancesController
(#5083)
## Explanation When fetching erc20 token balances via the multicall3 contract, there's a case where the call can revert. Even though we pass `requireSuccess=false` to `tryAggregate`, this does not catch all errors. Specifically, trying to execute code on a target address that is not a smart contract. There were some cases where users had tokens added with address `0x0000000000000000000000000000000000000000` which caused such a revert, preventing balances fetches from other tokens. In addition to migrating out of state tokens we can detect as invalid, the fix here is to fallback to parallel `balanceOf` calls if the multicall request reverts. ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/assets-controllers` - **FIXED**: `TokenBalancesController` was fixed to fetch erc20 token balances even if there's an invalid token in state whose address does not point to a smart contract. ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
- Loading branch information