Skip to content
PenyuOnCore
Menu
  • Home
  • Core Ecosystem Analysis
  • Personal Finance & Investing
  • Make Money Online
  • Bitcoin
  • About Us
Menu
max priority fee per gas higher than max fee per gas: how to fix it – rule: maxFeePerGas must be greater than or equal to maxPriorityFeePerGas

“max priority fee per gas higher than max fee per gas”: What It Means and How to Fix It

Posted on November 17, 2026

You hit Send, or run a deploy script, and the node returns max priority fee per gas higher than max fee per gas. Nothing was broadcast and no gas was spent. The node rejected the transaction because its two EIP-1559 fee fields contradict each other.

Short answer: On EIP-1559 (type 2) transactions, the priority fee (tip) is paid out of the max fee, so maxPriorityFeePerGas can never be larger than maxFeePerGas. Fix it by raising the max fee to at least base fee + tip, or by lowering the tip. If you only set one of the two fields by hand, set both, or leave both to your wallet or library.

Below: what the rule is, where the message comes from, the usual causes in MetaMask, ethers.js, viem, web3.py and Foundry, and the extra twist on networks with a minimum tip, such as Core.

What the error actually means

Since Ethereum’s London upgrade, a type 2 transaction carries two fee numbers instead of one gasPrice (see ethereum.org’s gas guide):

  • maxFeePerGas: the most you will pay per unit of gas in total, covering the burned base fee and the tip.
  • maxPriorityFeePerGas: the most you will tip the block producer per unit of gas.

Because the tip comes out of the total, a tip above the total makes no sense. The EIP-1559 specification enforces this with a hard check, assert transaction.max_fee_per_gas >= transaction.max_priority_fee_per_gas. The tip actually paid is min(maxPriorityFeePerGas, maxFeePerGas − baseFee).

The exact wording comes from go-ethereum (Geth). In core/error.go it is defined as ErrTipAboveFeeCap, described as “a sanity error to ensure no one is able to specify a transaction with a tip higher than the total fee cap.” The transaction pool validation code runs this check before it even recovers the sender from the signature. That is why you get this error rather than a balance or nonce error, even from an empty wallet.

Diagram: maxFeePerGas must cover base fee plus priority fee; a priority fee taller than the max fee is rejected with max priority fee per gas higher than max fee per gas

We reproduced it on four public RPCs

To confirm the behaviour, on 17 November 2026 we signed a type 2 transaction from a brand-new, unfunded test key with maxFeePerGas = 2 gwei and maxPriorityFeePerGas = 3 gwei and sent it with eth_sendRawTransaction. Every endpoint rejected it with the same message:

Network (public RPC)Max fee 2 / tip 3 gweiMax fee 3 / tip 3 gwei
Ethereum mainnet (publicnode)max priority fee per gas higher than max fee per gas (code -32000)Passed this check; failed later on insufficient funds
Ethereum Sepolia (publicnode)Same message (code -32003)Passed this check; failed later on insufficient funds
Base (mainnet.base.org)Same message (code -32003)Passed this check; failed later on insufficient funds
Core (rpc.coredao.org)Same message (code -32000)transaction underpriced: gas tip cap 3000000000, minimum needed 60000000000

Two takeaways. Setting max fee equal to the tip is enough to clear this particular check. And the check is the same across Geth-based chains, but each chain can add its own rules on top (more on Core below).

Common causes, by tool

1. You set one fee field by hand and the tool filled the other

This is the most common trigger in scripts. Libraries fill in whichever field you leave out:

  • ethers.js v6 fills a missing field from getFeeData(). The tip comes from the node’s eth_maxPriorityFeePerGas (falling back to 1 gwei), and the suggested max fee is 2 × base fee + tip (source). If you hard-code maxFeePerGas: parseUnits("1", "gwei") and the node suggests a 1.5 gwei tip, you get this error.
  • web3.py defaults the tip to w3.eth.max_priority_fee and the max fee to tip + 2 × the latest base fee (source). The same mismatch happens if you pin only maxFeePerGas.
  • web3.js / @ethereumjs/tx catches it before sending, with the message maxFeePerGas cannot be less than maxPriorityFeePerGas (The total must be the larger of the two) (source).
  • viem also checks locally and throws TipAboveFeeCapError: “The provided tip (maxPriorityFeePerGas) cannot be higher than the fee cap (maxFeePerGas)” (source).

Fix: set both fields together, or neither. A safe manual pattern is to read the latest block’s baseFeePerGas, choose a tip, and set maxFeePerGas = 2 × baseFee + tip. You never pay more than base fee + tip, so the headroom costs nothing if fees stay flat.

2. Foundry flags pointing the wrong way

In forge script and cast send, --with-gas-price / --gas-price sets the max fee on EIP-1559 transactions, and --priority-gas-price sets the tip (forge script reference, cast send reference). A low gas price combined with a default or environment-supplied tip (ETH_PRIORITY_GAS_PRICE) produces this error. On a widely cited Ethereum Stack Exchange question, the accepted answer is simply to pass a small --priority-gas-price. Alternatively, raise --with-gas-price so it is at least the tip. Use --legacy only on chains without EIP-1559.

3. Hand-edited fees in a wallet

MetaMask’s Advanced gas screen calls the max fee “Max base fee”, which is misleading, because it is the ceiling for base fee plus tip. MetaMask’s own interface strings include the warnings “Max base fee must be greater than priority fee” and “Priority fee must be less than max base fee” (MetaMask extension locale file). If you see those, raise Max base fee or lower Priority fee. If you saved custom values as the default for a network, clear them so the wallet goes back to its market estimate.

4. Geth’s own variant: “maxFeePerGas (X) < maxPriorityFeePerGas (Y)”

If you call eth_sendTransaction, eth_call or eth_estimateGas with both fee fields, Geth checks them while building the call and returns maxFeePerGas (X) < maxPriorityFeePerGas (Y) (transaction_args.go). It is the same mistake with the same fix.

The extra trap on chains with a minimum tip (Core)

Some networks enforce a minimum gas price or tip at the RPC. Our test above shows Core’s public RPC rejecting a 3 gwei tip with “minimum needed 60000000000” (60 gwei). If you raise only the tip to 60 gwei and leave a low max fee, you swap one error for the other. On Core, set both maxPriorityFeePerGas and maxFeePerGas to at least 60 gwei, or send a legacy transaction with a 60 gwei gasPrice. Our guide to “transaction underpriced” on Core covers that minimum in detail.

Quick checklist

  1. Print the exact maxFeePerGas and maxPriorityFeePerGas your code or wallet is sending, and check that both are in the same unit (wei vs gwei mix-ups are common).
  2. Make sure max fee ≥ tip. Then make sure max fee ≥ current base fee + tip, or you will hit “max fee per gas less than block base fee” next.
  3. Check the chain’s minimum tip, if it has one.
  4. Check that your balance covers gas limit × max fee + value. Nodes check against the max fee, not the fee you end up paying (see insufficient funds for gas).
  5. If you are replacing a stuck transaction, raise both fields. Geth’s replacement rule applies to each one (see replacement transaction underpriced).

FAQ

Did I lose gas when I got this error?

No. The node rejects the transaction before it enters the mempool, so nothing is mined and no fee is charged. Our test wallet had a zero balance and received the same response.

Is it safe to set the max fee much higher than I expect to pay?

In terms of cost, yes. Under EIP-1559 you pay the block’s base fee plus your tip (capped by the max fee), and the difference is never charged. The catch is that your balance must cover gas limit × max fee up front.

Can I set the priority fee to zero?

The protocol allows a zero tip, and it passes this check. Block producers have little reason to prioritise it, though, and some, like Core’s public RPC, reject tips below their minimum.

Why does setting both fields equal work?

The rule is “greater than or equal”. With max fee = tip, the effective tip becomes max fee − base fee. That is valid, but you tip less than you asked for whenever the base fee is above zero.

Disclaimer: This article is for general educational purposes only and is not financial or investment advice. Always double-check fee settings and network details before signing a transaction.

Recent Posts

  • “Nonce Too High” Error: What It Means and How to Fix It (MetaMask, Hardhat, Foundry)
  • Udemy Instructor Payout Schedule: When You Actually Get Paid
  • How to Deploy a Smart Contract on Core with Foundry (forge create & forge script)
  • Inheriting a Spouse’s ISA Allowance: How the Additional Permitted Subscription (APS) Works
  • “max priority fee per gas higher than max fee per gas”: What It Means and How to Fix It
Subscription form is not available at the moment
  • Altcoin News
  • Bitcoin
  • Core Ecosystem Analysis
  • DeFi
  • Free Crypto Signals
  • Make Money Online
  • Personal Finance & Investing
  • Token Analysis
  • About Us
  • Contact
  • Privacy Policy
  • Disclaimer
©2026 PenyuOnCore | Design: Newspaperly WordPress Theme