getTransactionCount('pending') vs. parity_nextNonce

Hello, we’re using getTransactionCount with “pending” to get the nonce, which is not always correct. Should we be using parity_nextNonce instead?

Seems like there’s an issue documented here already: Wrong nonce number in eth_getTransactionCount

I also see this in the docs:

NOTE: this method is only supported on the kovan network through our HTTPS and WebSocket endpoints.

Are there plans for this to be in the mainnet release?

Hi @tpae, and welcome to the Infura community! I see you also commented on the other community thread, so I will let Jee answer you there to keep everything in one thread :slight_smile:

1 Like

Hi Leiya, just following up, I haven’t received any replies yet on the other thread.