MetaMask / MetaMask/metamask-extension
Enhancement: Account specific settings/preferences?
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Opening this idea for discussion.
What if I have an account that I want to keep super private, and another account that I want all the usability bells and whistles (token detections, incoming transactions, fiat rates, fast loading token balances, etc)?
Or what if I have an account where I always want all developer specific settings enabled, and another account where I don't want any developer specific settings enabled?
Or what if I have an account that I only ever want to use on polygon, and another that I only ever want to use on goerli?
One way to address this would be to allow the user to configure their settings/preferences per network.
Contributor guide
Research direction
Start by reviewing the issue's proposed per-account and per-network preferences, including privacy, developer settings, token detections, fiat rates, and network restrictions. No files, tests, or entry points are named, so first identify where account and network settings are currently defined. Done would require an agreed scope and implementation plan for account-specific preferences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100