MetaMask / MetaMask/metamask-extension

Adding Native Token and ERC-20 Token logos on metamask

Open
#27,901 5 comments 0 reactions 0 assignees View on GitHub
external-contributor
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

**As a user** adding chains and tokens to metamask
**I want** to see logos of the tokens
**So that I** feel more secure about what tokens I have and I can easily differentiate them.

- Could we add the logos of Chiliz so that when someone adds The Chiliz Chain to metamask it has a logo for CHZ the native token.

Chain ID: 88888
Currency: CHZ
Logo: https://assets-staking.chiliz.com/images/assets/Chiliz.png

- Could we add a logo for the Community Token PEPPER so that when imported in metamask it has a nice looking logo.
Contract Address: 0x60F397acBCfB8f4e3234C659A3E10867e6fA6b67
Logo: https://assets-staking.chiliz.com/images/assets/pepper.webp

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [X] Other (please specify)

### References

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the extension’s existing native-token and ERC-20 logo handling, then check how chain ID 88888 and the supplied PEPPER contract address are represented; done means both supplied logos appear in the relevant token views.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.