Metamask-extension: How does MetaMask calculate the correct transaction nonce?
How does MetaMask calculate the correct transaction nonce when multiple transactions are being issued?
It's well known that eth_getTransactionCount does not return the correct number of pending transactions, so I was wondering how you guys do it. Could be really beneficial for the community to learn from.
tarekskr
All 4 comments
Put simply: we take the "highest" known confirmed nonce and add the pending transaction count from your local tx history (the transactions you've sent from within metamask). Given that sometimes infura may not know the most update nonce (asking a node a block behind etc.) We do to calculations for confirmed nonces: Derived from local confirmed and eth_getTransactionCount and choose the highest of the two.
you can reference all this code here: nonce-tracker
frankiebee
on 10 Oct 2018
Excellent, thank you so much for the link @frankiebee !
tarekskr
on 10 Oct 2018
Is it possible to suggest a nonce to the metamask extension to be able to cancel a pending transaction or update the gas price?
kaibakker
on 13 Oct 2018
@kaibakker we support speeding up tx already, check out https://github.com/MetaMask/metamask-extension/issues/4022 re: cancelling
bdresser
on 15 Oct 2018
Related issues
whyrusleeping
路
3Comments
beether
路
4Comments
danfinlay
路
3Comments
aecc
路
3Comments
MarkOSullivan94
路
3Comments
Most helpful comment
Put simply: we take the "highest" known confirmed nonce and add the pending transaction count from your local tx history (the transactions you've sent from within metamask). Given that sometimes infura may not know the most update nonce (asking a node a block behind etc.) We do to calculations for confirmed nonces: Derived from local confirmed and eth_getTransactionCount and choose the highest of the two.
you can reference all this code here: nonce-tracker