Speeding up EIP-1559 transactions always results in failure

[beaugunderson]

Describe the bug

I always get this error when speeding up an EIP-1559 transaction, and no replacement transaction is sent:

Steps to reproduce (REQUIRED)

• Try to speed up an EIP-1559 transaction

Expected behavior

• Transaction is sent

Screenshots

See above

Browser details (please complete the following information):

• OS: current macOS
• Hardware Wallet: none
• Browser: latest Chrome
• MetaMask Version: 10.0.3

Additional context (Error Messages, etc.)

What would be helpful?

[kevinghim]

I'm not able to reproduce the error after trying speed up transactions several times. I'm on Chrome, MetaMask version 10.0.3. What network are you trying this on? Can you include a screenshot of your console error?

[Zaphod101010]

I'm getting this error when I try to speed up txns too. There is no error in console. There is just an error that appears in the OS notification, and there is no way to read the full error.

I've tried sending a new txn manually with the same nonce as my stuck txn, but that fails too. Is there another wallet I can use to import my private key and unstick my transactions?

I got it to unstick by just setting my gas price crazy high on the new txn to 2000 gwei and 100 priority fee. I think if the replacement txn being submitted has too low of a gas fee metamask throws unexpected errors.

[kevinghim]

@Zaphod101010 is this happening when you're performing a swap?

[Zaphod101010]

It wasn't a swap. The stuck txn was the mint function on one of the loot derivatives.

[danjm]

@Zaphod101010 @beaugunderson What version of MetaMask are you using?

[danjm]

Oh, I see @beaugunderson is on 10.0.3

[danjm]

@beaugunderson @Zaphod101010 @BlackDots If you are willing, it would be helpful if you could grab your state logs and securely submit them to us via our customer support channel.s

1. Go to the home screen
2. open the developer tools
3. enter logState(true) in the developer console, this will copy json text to your clipboard
4. paste into a text file and save
5. submit the file via the form found here: https://metamask.zendesk.com/hc/en-us/requests/new

[Zaphod101010]

v10.0.3

[beaugunderson]

Two friends just reported that speedups failed on transactions as well; here's one example where a speedup failed:

https://etherscan.io/tx/0x202eb0c9929db5a5ed1400308d8a25219e5ae405c48f3666a8fac11ba57dea55

[beaugunderson]

still happening, though this time I can grab the logState 👍 will submit momentarily

[beaugunderson]

hmm, logState contains way more than I want to share; @danjm can you share a jq query for the specific information you need from the logState object? (or just a dotted path or paths and I can grab manually)

[beaugunderson]

I submitted the state log for the specific transaction in question; if you need more let me know 👍

[beaugunderson]

this is the full error, btw:

        "err": {
          "message": "Error: [ethjs-query] while formatting outputs from RPC '{\"value\":{\"code\":-32000,\"message\":\"replacement transaction underpriced\"}}'",
          "stack": "Error: [ethjs-query] while formatting outputs from RPC '{\"value\":{\"code\":-32000,\"message\":\"replacement transaction underpriced\"}}'\n  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-1.js:1:77293"
        }

[GeekLad]

I'm having the same problem. I managed to submit one speed-up, but it doesn't show up in Etherscan. When I try to submit another, I get the RPC error.

[susuper]

I've got the same issue, Metamask 10.1.0 for Firefox

[HoorayJorge]

Same issue in firefox. Speed up doesn't work and no new transaction appears.

[Validatus]

@kevinghim Still, years later @MetaMaskSupport offers no solution. We would love to spin up to reproduce this issue.

[IgoresVer]

This annoying and disgusting bug still exists. 10.5.2 Please, do something!

[hukkin]

This happens to me consistently too. Not when using the built-in "Speed up" feature though. But each and every time when I create a new fresh transaction and manually set it to the same nonce as the previous one.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in 60 days. Thank you for your contributions.

[github-actions[bot]]

This issue was closed because there has been no follow activity in 90 days. If you feel this was closed in error please provide evidence on the current production app in a new issue or comment in the existing issue to a maintainer. Thank you for your contributions.