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
Warn when sending a token to its own address #9437
Comments
@cjeria I heard you may already have some designs on this? |
I didn't find this specific warning message but I did mock up an additional error message for this use case. Here's the Figma file where these can be found. cc @rachelcope |
Christian's update designs are here: https://www.figma.com/file/KNLr0RnAk5p4duCywOqIhR/Send-Flow-QR-Compatibility?node-id=0%3A1 |
Related: #9673 |
Is there any way to bump the priority of this issue? I don't have definitive proof, but I believe that metamask is the wallet used in many of the losses found on the TokenOops twitter bot, and those losses are commonly over $10,000/day |
Designs ready. View designs in Figma This error message is should follow the patterns set out in the error/notification system |
If this is error is implemented before the new transaction confirmation, then the banner should be shown at the top of the current transaction confirmation design. |
Amazing, awesome! |
Any idea what happened to this feature? Metamask does not warn any more and users are losing significant funds again. https://etherscan.io/tx/0x4ac70627fa303cf8dd6bb26b5dc63eab653bac88736c642394a952489cac7231 |
For example
This is a common way to lose funds. I honestly thought we already prevented this, but it seems not.
Acceptance criteria:
Maybe even:
I am sure I want to probably lose these tokens
before theConfirm
button is enabled.The text was updated successfully, but these errors were encountered: