Description

This PR removes the RatesController to reduce redundant CryptoCompare API calls in the multichain architecture.

Reason for the change

The RatesController was introduced for fetching cryptocurrency conversion rates (primarily for BTC and SOL) to support non-EVM chains. However, this resulted in duplicate API calls to CryptoCompare since we already have MultichainAssetsRatesController and TokenRatesController handling rate fetching functionality. This redundancy increased API usage unnecessarily.

Improvement/solution

• Removed RatesController initialization and configuration from the Engine
• Deleted RatesController messenger setup and related controller initialization files
• Removed multichain selectors that depended on RatesController state (selectMultichainConversionRate, selectMultichainCoinRates)
• Cleaned up type definitions and state management to remove RatesController references
• Updated test snapshots and initial background state

The existing MultichainAssetsRatesController and TokenRatesController will continue to handle all rate-fetching needs without the additional overhead of RatesController.

Changelog

CHANGELOG entry: Removed redundant RatesController to optimize API usage

Related issues

Fixes:

Manual testing steps

Feature: Multichain rate fetching

  Scenario: User views portfolio balance with non-EVM accounts
    Given user has Bitcoin and Solana accounts configured
    And user is viewing their portfolio

    When the app fetches cryptocurrency rates
    Then rates should be fetched only through MultichainAssetsRatesController
    And no redundant API calls should be made to CryptoCompare
    And account balances should display with correct fiat conversions

  Scenario: User switches between EVM and non-EVM accounts
    Given user has both EVM and non-EVM accounts
    And user is viewing their wallet

    When user switches between different account types
    Then appropriate conversion rates should display for each account
    And rate updates should continue to work correctly

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.