SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Web3 New Added 26 September 2026

Web3: transaction underpriced

The node rejected the transaction before it entered the pool because the fee offered is below the minimum it will accept, which is local policy rather than a consensus rule. It differs from the replacement case: nothing is pending for that nonce, the fee is simply under this node’s floor or under the current base fee.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
// Let the provider price it rather than hard coding gwei
const fee = await provider.getFeeData();
const tx = await wallet.sendTransaction({
  to,
  value,
  maxFeePerGas: fee.maxFeePerGas,
  maxPriorityFeePerGas: fee.maxPriorityFeePerGas,
});

// Many nodes enforce a minimum tip, and 1 gwei is a common floor
// maxPriorityFeePerGas: ethers.parseUnits('1', 'gwei')

# What the node itself suggests, right now
# cast gas-price --rpc-url $RPC
# cast rpc eth_maxPriorityFeePerGas --rpc-url $RPC

// Replacing a stuck transaction needs a real bump, not a nudge: at least
// 10 per cent above both fee fields of the pending one, same nonce
const pending = await provider.getTransaction(hash);

// Legacy chains still want gasPrice, and mixing the two styles is rejected outright

How to diagnose Web3 errors

Web3 errors are unusually terse because the EVM reports failure without explanation by default. execution reverted means a require or revert triggered. The reason string is present in the return data but most libraries discard it. Nonce errors reflect the strict sequential ordering of transactions per account, so a stuck transaction blocks every one behind it.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Simulate before sending: eth_call against the same block returns the revert reason string that a submitted transaction hides.
  2. Use a transaction tracer (Tenderly, Foundry's cast run, or a node's debug_traceTransaction) to see the exact opcode and contract where execution reverted.
  3. For nonce errors, query the account's pending nonce (eth_getTransactionCount with the pending tag) rather than tracking it locally.
  4. To replace a stuck transaction, resend with the same nonce and a materially higher gas price: most nodes require at least a 10% increase.
  5. Check the chain ID matches the network you intend. Signing for the wrong chain produces confusing rejection messages.

Tools worth reaching for

  • cast (Foundry)
  • eth_call simulation
  • Tenderly / block explorer tracer
  • debug_traceTransaction

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

ethereum.org docs.ethers.org

Related Web3 errors

See all 17 Web3 errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.