Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Metamask account suddenly gone! Can i still recover my funds? #17864

Closed
vlindersteen opened this issue Feb 22, 2023 · 2 comments
Closed
Labels
CS handover Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. stale issues and PRs marked as stale type-bug

Comments

@vlindersteen
Copy link

vlindersteen commented Feb 22, 2023

Describe the bug

I transferred funds within my MetaMask from Account A → Account B. I’ve seen the funds (0.017 ETH + 1 NFT + $SDL tokens) arrive in Account B.

The next day when i opened my MetaMask, Account B is totally gone and nowhere to be found. (0x12c951e8D4838420e01EB8a0E6eC2bDc44A83249 is the address)

I figured it might have to do something with these issues i found on Github: #6012 and #10875. The address is probably connected to my Ledger.

I also wrote about it on Metamask support forum: https://community.metamask.io/t/metamask-account-suddenly-gone-can-i-still-recover-my-funds/24484/1

I still don't have solution yet after searching for two days, hope anyone can help me out!

Steps to reproduce

I don't know?

Error messages or log output

No response

Version

10.25.0

Build type

None

Browser

Chrome

Operating system

Windows

Hardware wallet

Ledger

Additional context

No response

@danjm danjm added CS handover Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. labels Mar 1, 2023
@github-actions github-actions bot added the stale issues and PRs marked as stale label Jul 20, 2023
@pedronfigueiredo pedronfigueiredo removed the stale issues and PRs marked as stale label Jul 20, 2023
@MetaMask MetaMask deleted a comment from github-actions bot Jul 20, 2023
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Oct 18, 2023
Copy link
Contributor

github-actions bot commented Dec 2, 2023

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 2, 2023
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CS handover Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. stale issues and PRs marked as stale type-bug
Projects
None yet
Development

No branches or pull requests

5 participants
@danjm @pedronfigueiredo @vlindersteen and others