# How to speed up or cancel a stuck Ethereum transaction in Plain Wallet, and the 25% fee rule behind it

> Plain Wallet resends a pending Ethereum transaction at the same nonce with at least 25% higher fees, or cancels it with a zero-value self-transfer. Tested numbers from the 0.6.1 source.

Published November 15, 2026 on Plain Wallet Notes: https://blog.plainwallet.app/speed-up-cancel-stuck-ethereum-transaction/

When an Ethereum transaction sits pending because its fee is too low, the fix is to send a new transaction with the same nonce and a higher fee, and Plain Wallet now does that for you: open **Transactions** on the home screen, tap **Speed up** to resend the same transaction, or **Cancel transaction** to replace it with a transfer of nothing to yourself. Both ask you to approve exactly what gets signed, and both bump every fee field by at least 25%. That is the whole feature, and it arrived in [Plain Wallet](https://plainwallet.app) 0.5.9 to 0.5.12 on 2 November 2026. The rest of this post is how it works underneath, with the numbers from the code at version 0.6.1 (commit `00b0fd6`, read on 2026-11-15), because "just raise the gas" hides three details that decide whether the replacement is accepted at all.

## Why does a transaction get stuck, and what does "same nonce" mean?

Every account has a counter, the nonce, and the network runs an account's transactions strictly in order: nonce 7 cannot be included before nonce 6. A transaction whose maximum fee per gas is below what blocks currently charge is not rejected, it waits in the pool, and everything behind it from the same account waits too. You cannot delete a waiting transaction. You can only send another one at the same nonce that the network prefers, and whichever of the two is included first counts.

"Prefers" has a precise meaning. A node keeps the waiting transaction unless the new one pays enough more. Plain Wallet's own test comment puts the requirement at at least 10% on each fee field, and the node's refusal when you fall short is the string `replacement transaction underpriced`. Plain Wallet matches that text, and the older `replacement fee too low`, in a function called `feeRefusal` in `lib/chain.ts`.

## What does Plain Wallet do when a node says "replacement transaction underpriced"?

This is where it started, in 0.5.9. You send a transaction while another one from the same account still waits at that nonce, and the node refuses. Now the wallet recognises the refusal, offers the transaction again with 25% higher fees, and asks before signing. It does this both for requests from sites and on the Send screen.

Version 0.5.10 widened the same idea to the other fee refusal, `max fee per gas less than block base fee` (and `transaction underpriced`), which means the network got more expensive between the moment you reviewed the transaction and the moment you approved it. There the retry is not a replacement, so the fee is raised to what the network charges now and never lower than what you already offered. Anything else, such as `nonce too low` or `insufficient funds`, is not a fee problem and is shown as it is.

## How much higher is the new fee? The 25% rule, with numbers

The function that decides is `raise` in `lib/chain.ts`. For a replacement it multiplies every fee field by 125 and divides by 100 in bigint arithmetic, then takes the larger of that and what the network charges now. For a plain retry it skips the 25% and takes the larger of your old value and the current one. I ran the actual function from the 0.6.1 source in Node 22 on 2026-11-15, with a 21,000-gas transfer that was first sent at a max fee of 20 gwei and a priority fee of 1 gwei (a total of 0.00042 ETH at most):

| Situation | New max fee | New priority fee | Most it can cost |
|---|---|---|---|
| Replace, network now charges 18 gwei and 0.5 | 25 gwei | 1.25 gwei | 0.000525 ETH |
| Replace, network now charges 30 gwei and 2 | 30 gwei | 2 gwei | 0.00063 ETH |
| Retry after a fee refusal, network now 24 and 1.5 | 24 gwei | 1.5 gwei | 0.000504 ETH |
| Retry after a fee refusal, network now 15 and 0.5 | 20 gwei | 1 gwei | 0.00042 ETH |

The first row is the case where the market is cheaper than your old fee and the 25% rule still applies: the node will not swap your transaction for one that pays less than 10% more, so the wallet pays 25 gwei even though 18 would clear the market. The second row is the opposite case, where fees jumped past the +25% and the wallet follows the network. The last row shows that a retry never goes below what you offered. The wallet raises the max fee, the priority fee and the legacy gas price together, so no field is left below the bump. (viem fills in `gasPrice` next to the EIP-1559 fields, so a transaction can carry both.)

The "most it can cost" column is the number you see before you approve. The fee is shown again when you open the review, not copied from the first attempt, because the wallet asks the network for current fees when you tap the button.

## How does Cancel work?

Cancel is a replacement whose content is nothing. Plain Wallet takes your pending transaction, keeps its nonce and chain, changes the recipient to your own address, sets the value to zero and removes the call data, and sends that at the higher fee. If the network includes it first, your original transaction can never run, because its nonce is used up. If the original was already about to be included, it wins, and the screen says so up front: *"If it is included first, the original never happens."*

One detail I did not expect to need: the gas limit of the cancel is asked from the node with `estimateGas` for a zero-value transfer to yourself, rather than assumed to be 21,000. Some chains, Arbitrum among them, count more than 21,000 for a plain transfer, and a hard-coded limit would make the cancel fail there.

## Where do the pending transactions come from?

The wallet keeps a list of everything it broadcast, on every network, in the browser's local storage on that device and nowhere else. Each entry is the signed transaction itself plus the network name, the time and the site that asked. The sender, the nonce and the chain are read back out of the signature, so there is no second copy of those that could disagree with what is signed. The last 100 are kept, and older ones are on a block explorer.

To say where each one stands, the list looks for a receipt by hash. Without one, it asks how many transactions the sender has had included. If that count is still at or below the transaction's nonce, the transaction is **Pending**. If the count has moved past the nonce and there is still no receipt, something else took that nonce, and it is shown as **Replaced or dropped**. Once a fate is known it is stored, so the network is not asked again. When you speed up or cancel, the old and new transactions share a nonce, and only the newest of them gets the buttons, which stops you from stacking a third replacement on a second one by accident.

The buttons are hidden for watch-only accounts, because their key lives on another device and there is nothing here to sign with.

## What does "already known" mean?

In 0.5.12 I fixed something that looked like a failure but was not. If you send a transaction, close the wallet, and send the identical one again, the node answers `already known`: it already holds those exact bytes. Signing is deterministic, so the same nonce and the same fees produce the same signature. Before the fix the wallet reported an error. Now it counts the transaction as sent, lists it under Transactions with its hash, and lets you speed it up. The wallet matches three phrasings of that answer: `already known`, `known transaction` and `already imported`.

## What I would tell someone before they tap Speed up

- The new transaction does not stop the old one, it races it. Whichever is included first counts, so a speed-up is safe, and a cancel is a request.
- Check the "most it can cost" figure. A replacement is at least 25% more than the first attempt.
- The list of sent transactions stays on the device and is never synced. A speed-up or cancel goes to the RPC of the network you chose, like any other transaction.

The feature shipped in four small releases in an afternoon, [0.5.9](https://git.borodutch.com/backmeupplz/plainwallet/releases/tag/v0.5.9) to [0.5.12](https://git.borodutch.com/backmeupplz/plainwallet/releases/tag/v0.5.12). Everything is in the open at [github.com/backmeupplz/plainwallet](https://github.com/backmeupplz/plainwallet), and the wallet itself, for Chrome, Firefox, Safari, Android, iPhone and Mac, is at [plainwallet.app](https://plainwallet.app).

## Questions people ask

**Can I cancel an Ethereum transaction?** Only by replacing it: a zero-value transfer to yourself at the same nonce and a higher fee. If the original is included first, it still happens.

**How much higher does the gas fee need to be to replace a transaction?** Nodes need at least 10% more on every fee field. Plain Wallet uses 25%, or the current network fee if that is higher.

**Does Plain Wallet send my transaction list anywhere?** No. It is stored only on the device; only a transaction you approve is sent, to the RPC of the selected network.

