You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem are you trying to solve?
Users often submit multiple transactions in a row and are confused / frustrated when they don't confirm, especially if they submit a transaction with high gas while something else is already pending. Many folks don't realize tx need to be processed in nonce order. See #5113 and MetaMask/Design#25 (comment)
Describe the solution you'd like
When a user has several pending tx and is about to confirm another tx, we could show a dismiss-able warning that says something like.
You have X pending transactions that must be confirmed before this transaction will confirm. If you'd like to speed up those transactions, click here.
Open to discussion whether we should show this warning if the user has as few as 1 pending tx, or if we should only show it if the user has several (>3) backed up.
The text was updated successfully, but these errors were encountered:
The warning can look like the cancel modal (but with only title, text and buttons; not the highlighted eth amount):
Clicking the yes option should take the user to the main screen with the speed up sidebar opened as is done here:
This should be opened for the blocking transaction. That transaction should be highlighted in some way so that the user can know which transaction they are speeding up.
What problem are you trying to solve?
Users often submit multiple transactions in a row and are confused / frustrated when they don't confirm, especially if they submit a transaction with high gas while something else is already pending. Many folks don't realize tx need to be processed in nonce order. See #5113 and MetaMask/Design#25 (comment)
Describe the solution you'd like
When a user has several pending tx and is about to confirm another tx, we could show a dismiss-able warning that says something like.
The text was updated successfully, but these errors were encountered: