MetaMask / MetaMask/metamask-extension

Remember added custom token details across accounts

Open
#7,125 0 comments 0 reactions 0 assignees View on GitHub
area-tokens T08-featureRequest type-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**What problem are you trying to solve?**
When I add a token to one of my accounts (addresses in my den) that MM doesn't support out-of-the-box, I need to mine the data from Etherscan. I need to do this again whenever I switch to a new account and want to use the same token.

**Describe the solution you'd like**
Once a custom token is added to an account, store its details locally and treat it as an out-of-the-box supported token for all other accounts. If this is not possible, at least make it addable through searching for the symbol.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the custom-token add flow and the local data used when switching accounts; confirm that one account's token details are available to the others, with symbol search as the fallback. Done means the same custom token no longer requires repeated Etherscan lookup.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.