I got a little greedy a few days ago and tried to execute a 2.5m gas transaction at 9 gwei, which was poor timing given the state of crypto markets. I have quite a bit of crypto experience and have had plenty of stuck transactions historically that I could get unstuck through the commonly sourced methods, but I’ve never had an issue like this before.
- I funded a Rocket Pool minipool ~4 days ago at 9 gwei, which was too low and it’s been pending for four days (Ethereum Transaction Hash (Txhash) Details | Etherscan)
- I tried all the common methods speeding it up by clicking speed up in MetaMask, replacing the transaction with a zero ETH transfer reusing the 106 nonce from the stuck transaction, I’ve updated my ledger Ethereum app. No success. Every transaction I sign to speed up the stuck transaction or send w/ custom nonce reusing nonce 106, fails immediately and the transaction is not visible on Etherscan as far as I can tell. It produces the below screenshot every time.
- The other interesting piece of information that I’m not sure how to interpret is when I click transaction data in MetaMask for the stuck transaction, it takes about a minute to load and says the user aborted a request.
One final caveat in advance:
Every person I’ve sought help from looked at my account and noted that I did the custom nonce transaction incorrectly. Just to save time before it gets raised by responders, this isn’t the case. The other pending transaction in my Etherscan intentionally used nonce 107 instead of 106. This was just me messing around on day ~3 to see how it’d look in the block explorer as I’d never had two pending transactions before. Just a curiosity on my end and not related to this issue. All the transactions I sign to replace the real stuck transaction (the one where I fund a Rocket Pool minipool for 16ETH) do not show up in Etherscan at all so you can’t verify that I’ve tried to do this as far as I can tell.
Appreciate any thoughts or help here as I have no idea what’s going on at this point …
Hello @martykebke, welcome to MetaMask community!
So just to make sure, have you increased the max fee and max priority fee by 30% before sending the transaction with the same nonce and 0 ETH value, in order to cancel the one you got stuck?
Ahh that did it. It was a weird quirk with priority fee, which admittedly I’m not sure I understand why it exists? I thought my initial transaction had a standard 1 gwei priority fee and 9 gwei max fee, but apparently it was actually a 9 gwei priority fee AND 9 gwei max fee, so I needed a 10 gwei priority fee to push it through but the most I tried before was 3 gwei think it was 3x my initial priority fee.
Out of curiosity, why would there be a % increase threshold on priority fees to replace a transaction instead of just the max fee? Seems weird to prevent me from replacing my initial transaction with a higher max fee given I somehow fat-fingered the prior priority fee calculation and that was fee was already ~9x the normal market rate. How would that work on a transaction initially excluding priority fees? I presume this is a MetaMask thing and not an Ethereum thing?
No worries if you don’t know the answer to any of my questions above, you already helped me solve my problem and I learned something new, but would be curious on knowing more if this is known information.
In short, it’s at least by that amount (30%) because it takes into consideration that a transaction with more gas fee offered, but with the same nonce and no value added, will be processed by the nodes, in our case now with the move from PoW to PoS, much faster and thus cancelling your stuck one. The staked node gets the fees and you get unstuck and free to transact further. If the gas fee is not high enough, you will only increase the number of transactions pending and it will get messier.
So, it isn’t a MetaMask thing, it’s a blockchain thing and MetaMask offers you the tools to solve your issue.
Sorry, just to clarify, I totally understand the max fee increase parameter, but don’t understand the point of a priority fee increase threshold and I presume that’s a MetaMask thing and not an Ethereum thing, but I could totally be wrong on that.
Meaning it seems weird to me that the transaction was prevented because I initially had the max priority fee equivalent to the max fee, when in reality that max priority fee was never going to be even close to paid. Just my thoughts. Thanks again for the help.
I believe these articles could explain the difference. Basicly the priority fee is the miner’s tip and what i said above as general information applies to the different types of fees, especially for the miner’s tip to rush and get your transaction processed.
Let me know if these help.
Thank you, all set here! Appreciate it.