MetaMask / MetaMask/metamask-extension
Speedup/Cancel transaction UX improvements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
**Describe the usability problem**
- [ ] Currently in the extension we don't give the user any UI feedback when we broadcast a speedup or cancel transaction. We should probably tell the user the cancel/speedup transaction has been submitted (including a disclaimer that it may or may not beat the original transaction).
Video of current speedup UX:
https://user-images.githubusercontent.com/34557516/131925686-2a848a0e-1b78-4638-b9fc-5b5c7eac36a0.mov
- [ ] When speedup/cancel transaction is unsuccessful (the original transaction is confirmed by the network) we show the user two contradictory and confusing messages:
The error "nonce too low" should be translated to something like `Unfortunately your speedup/cancel transaction didn't successfully replace your original transaction`. And then we ought to show an indication of this failed speedup/cancellation in their activity log.
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 tracing the extension's speedup and cancel transaction flow, including how the activity log handles transaction outcomes. Done means users receive submission feedback with the replacement disclaimer and see a clear failed replacement message and activity-log indication when the original transaction is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100