[Bug]: Base chain tokensChainsCache not refreshing, stale token data persists with no manual refresh trigger

[web3iocore]

Describe the bug

On Base mainnet (chainId: 8453 / 0x2105), MetaMask Extension appears to cache token data in tokensChainsCache very aggressively.

In practice, the cached token data can remain stale for a long time (e.g. data from yesterday), even though the upstream token list has already been updated.

There does not seem to be a clear way to manually or programmatically trigger a refresh of tokensChainsCache.

Expected behavior

• tokensChainsCache should refresh in a reasonable time window
• Or MetaMask should expose:
  • a manual refresh mechanism, or
  • a clear cache invalidation strategy (TTL), or
  • a documented way to force refresh of tokensChainsCache

Screenshots/Recordings

No response

Steps to reproduce

1. Switch MetaMask Extension to Base mainnet
2. Ensure a token list update happens upstream (e.g. new token added or metadata updated)
3. Observe token list / token metadata in MetaMask
4. Even after a long time (hours or a full day), the token data still reflects old values from tokensChainsCache

Error messages or log output

Where was this bug found?

Live version (from official store)

Version

13.14.2 and 13.15.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

This issue impacts:

• newly added tokens
• token metadata updates
• dapps relying on up-to-date token information

Clarification on the following would be helpful:

• cache TTL policy for tokensChainsCache
• whether this behavior is expected
• whether this is specific to Base network integration

Severity

No response

[ruhil6789]

@chloeYue i want to work on this issue. Can you please assign this issue to me.