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
Describe the bug
Custom nonce feature doesn't work for the first transaction of account (nonce zero)
To Reproduce (REQUIRED)
Steps to reproduce the behavior
Try to use a new account which hasn't any transaction on network, so it's first transaction will have nonce value zero.
Connect metamask to mainnet or any testnet which doesn't do transaction immediately
Do a transaction in network and set low gas limit for it in order to have enough time for next transactions
Cancel the first transaction (this step may not be required, but I needed for my test)
Create another transaction with high gas value and set its nonce value manually to zero
Expected behavior
The second transaction should be mined by network and the first one should be failed! But metamask doesn't care about the custom nonce zero and eventually both transactions will be mined. First transaction will have nonce value 0 and the second one will have nonce 1
Screenshots
Browser details (please complete the following information):
OS: macOS Catalina
Browser Chrome Version 83.0.4103.116 (Official Build) (64-bit)
MetaMask Version 7.7.9
The text was updated successfully, but these errors were encountered:
Describe the bug
Custom nonce feature doesn't work for the first transaction of account (nonce zero)
To Reproduce (REQUIRED)
Steps to reproduce the behavior
Expected behavior
The second transaction should be mined by network and the first one should be failed! But metamask doesn't care about the custom nonce zero and eventually both transactions will be mined. First transaction will have nonce value 0 and the second one will have nonce 1
Screenshots
![image](https://user-images.githubusercontent.com/5684607/86327459-a2a3a900-bc58-11ea-9643-106f4ddd9333.png)
Browser details (please complete the following information):
The text was updated successfully, but these errors were encountered: