MetaMask / MetaMask/metamask-extension

Seed phrase backup reminder - for light users

Open
#6,600 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-seedPhrase 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?
"Very light" MetaMask users forget there is a seed phrase associated with MetaMask, forget where they saved it, save it locally on their PC, or never write it down/save in the first place. The longer they do not use MetaMask, the risk of loss of funds may increase if they are not well educated about the importance of their seed phrase.

Describe the solution you'd like
For those users that use MetaMask less often, provide them a reminder notification the next time they use MetaMask, if there is a 30+ days between the time they last used MetaMask or maybe the next time MetaMask is updated (maybe display an indication number or image by the MetaMask extension icon in the browser's toolbar).

Additional context
The message could be a friendly reminder, "MetaMask Tip, ensure you have your seed phrase saved somewhere secure, in order to prevent permanent loss of funds. Ways you could permanently lose funds without backing up your seed phrase include: computer crashing, changing computers (from an old to new, or switching jobs), loss, theft, data corrupting, issues with OS, Browser or MetaMask auto-updates, etc.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the extension's notification and seed-phrase backup flows, then clarify the trigger, reminder presentation, and required behavior before implementation; done should include a defined reminder for users inactive for 30 or more days.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.