With more chains, the number of tokens with similar names will increase.
Meanwhile, we are also embracing more user-centric naming, like via [[address display fallback logic]].
We have a need to revisit how we show tokens, and highlight to a user why it is called a given name.
From our own list
From our [[[[CodeFi]] Improved [[token detection]] v2]]
From [[token lists]]
From [[EIP-747: wallet_watchAsset]]
From user-added via the custom token form
Possible acceptance criteria
- Recognized tokens should show the source of their auto-detection
- Was this an auto-detected [[proposed name]]?
- Was this drawn from one or more [[token lists]]?
- Was this added from a particular domain via [[EIP-747: wallet_watchAsset]]?
- Was this added manually? When?
- Tokens with names that are similar to other known tokens should be indicated as such.
- Particularly if the new token name is similar to a token the user already has/trusts.
- What if the token resembles a token in our auto-detection system that the user has never encountered? Do we need to bother the user about that? Possibly not!
- [[eth-contract-metadata]] should be able to have multiple tokens with the same symbol (but maybe not the same name)
- Maybe we add fields to distinguish them
- Official website
- Support email (as [[MyCrypto]] does)
- When tokens are shown, we should show their `name` field (not just the symbol, which is meant to be shorter).
- Possible: When a token is added/detected, allow the user to either [[pet name]] the token or at least add a personal note to that token, which should then be visible any time that token is interacted with. ("Not the real DAI, just my test token.")
- Anywhere long token names are shown, it should be possible for the user to see the full name (even if cut off in preview).
Background
Possible acceptance criteria