bug: no way to update public transaction after submitting transaction with gas below intrinsic limit

[annamcallister]

What happened?

I submitted a public transaction with a gas limit below the intrinsic limit, which was rejected by the chain. This meant the nonce was not used and all subsequent transactions from that signing key with higher nonces became stuck in the mem pool.

What did you expect to happen?

To have a way to continue submit transactions. I think what that means is being able to update the transaction to increase the gas limit, or to nullify the transaction.

We could potentially guard against this issue by estimating the intrinsic gas, but this would an additional rpc call to the node and since it's an estimate the issue could still occur, so this is probably an enhancement if we want it, and less important than the ability to update a transaction.

How can we reproduce it (as minimally and precisely as possible)?

Submit a public transaction with a very low gas limit

Anything else we need to know?

No response

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here