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
Us using those two functions unfortunately makes usage of Infura unsafe since they do not expose these two functions.
After talks with them it may be possible to expose the parity_nextNonce function but not the web3.txpool.inspect one for technical reasons.
The good point is that it seems that since we did this geth has fixed their issue and eth_getTransactionCount() works as intended including the pending nonces: ethereum/go-ethereum#2880
Task
Remove the special handling for nonces in geth since they have fixed the issue from their side and eth_getTransactionCount() works as intended.
Once infura exposes the parity function then we can also remove the infura warning
The text was updated successfully, but these errors were encountered:
Problem Definition
We have had some special case handling of nonce both for parity and for geth.
The reason for this can be seen in this issue.
Us using those two functions unfortunately makes usage of Infura unsafe since they do not expose these two functions.
After talks with them it may be possible to expose the
parity_nextNonce
function but not theweb3.txpool.inspect
one for technical reasons.The good point is that it seems that since we did this geth has fixed their issue and
eth_getTransactionCount()
works as intended including the pending nonces: ethereum/go-ethereum#2880Task
eth_getTransactionCount()
works as intended.The text was updated successfully, but these errors were encountered: