MetaMask / MetaMask/metamask-extension
Optimize token data storage in preferences controller
Open
Nobody has claimed this yet.
area-tokens
type-enhancement
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
The way we store token data in the preferences controller has a lot of unnecessary redundancies, and may cause performance issues for users with lots of tokens (hidden or otherwise).
We should review whether we can optimize the storage of tokens in the preferences controller.
Ref: https://github.com/MetaMask/metamask-extension/pull/9320
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the preferences controller and reading the storage approach discussed in PR 9320. Review how token data is represented, including hidden tokens, then define and measure reduced redundancy or improved performance before deciding what completion looks like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100