Skip to content
PenyuOnCore
Menu
  • Home
  • Core Ecosystem Analysis
  • Personal Finance & Investing
  • Make Money Online
  • Bitcoin
  • About Us
Menu
Transaction underpriced on Core: fix the 60 gwei minimum gas price

“Transaction Underpriced” on Core: Fix the 60 Gwei Minimum

Posted on November 16, 2026

Quick answer: On Core, “transaction underpriced” means your gas price (or, for EIP-1559 transactions, your priority fee) is below the minimum the RPC node will accept. In live tests on November 17, 2026, the official endpoint rpc.coredao.org rejected anything under 60 gwei with transaction underpriced: gas tip cap …, minimum needed 60000000000. Fix it by letting your wallet use the network’s suggested gas price, or by setting the gas price (or max priority fee) to at least 60 gwei.

This guide explains where the 60 gwei floor comes from, how to fix the error in MetaMask and in scripts, and how it differs from the similar-sounding “replacement transaction underpriced” error.

What the error actually says

Core runs a Geth-based client (the public RPC reported Geth/v1.0.27 when we checked). Geth nodes have a setting called --txpool.pricelimit, described in the Geth command-line docs as the “minimum gas price tip to enforce for acceptance into the pool.” Geth’s default is just 1 wei, so each node operator picks the real value. A transaction priced below it is refused straight away. It never enters the mempool, so it can’t get stuck. It just doesn’t exist on-chain.

The full message from Core’s public RPC looks like this:

{"code":-32000,"message":"transaction underpriced: gas tip cap 1000000000, minimum needed 60000000000"}

The values are in wei. 1000000000 is 1 gwei (what was offered), and 60000000000 is 60 gwei (the floor). Older wallets, including MetaMask, sometimes show only the short form: [ethjs-query] while formatting outputs from RPC … "transaction underpriced". MetaMask’s error guide says it simply means the gas price was set too low.

What we measured on Core (November 17, 2026)

We signed test transactions from a brand-new, empty wallet and sent them to public Core RPC endpoints. An empty wallet means nothing could actually be spent. The useful signal is which check fails first. If the node complains about the price, the fee is too low. If it moves on to “insufficient funds,” the price passed.

Gas setting sentrpc.coredao.org (official)core.drpc.org
Legacy gas price 0 gweitransaction underpricedtransaction underpriced
Legacy gas price 1 gweitransaction underpricedtransaction underpriced
Legacy gas price 59 gweitransaction underpricedtransaction underpriced
Legacy gas price 60 gweiPrice accepted (failed later on balance)Price accepted (failed later on balance)
EIP-1559: max fee 100, priority fee 1 gweitransaction underpricedtransaction underpriced
EIP-1559: max fee 100, priority fee 60 gweiPrice accepted (failed later on balance)Price accepted (failed later on balance)

Other readings from the same session:

  • eth_gasPrice and eth_maxPriorityFeePerGas both returned 60 gwei, and recent blocks reported a baseFeePerGas of 0.
  • In a sample of 300 recent blocks, every transaction with a non-zero gas price paid at least 60 gwei. The only zero-price transactions were validator system transactions sent by the block producer to the system contract 0x…1000. Ordinary users can’t send those.
  • At 60 gwei, a plain 21,000-gas transfer costs 0.00126 CORE in gas. That figure comes from the node’s own “tx cost” in its error response.

Diagram: Core RPC checks the gas tip against the 60 gwei minimum before checking the balance; below 60 gwei returns transaction underpriced

Because the base fee is 0, the “tip” the node checks is effectively your whole gas price. For a legacy transaction it’s the gas price itself. For an EIP-1559 transaction it’s the max priority fee, and a high max fee doesn’t help if the priority fee is low. That’s why a common Ethereum default like a 1–2 gwei priority fee fails on Core even with a generous max fee. (EIP-1559 explains how the two fields work.)

How to fix it in MetaMask or another wallet

  1. Check that nothing is already pending. MetaMask’s guide recommends checking the block explorer first so you don’t build up a queue. Paste your address into Core Scan. If an older transaction is stuck, deal with it first (see our guide to Core transactions pending in MetaMask).
  2. Go back to the wallet’s suggested fee. If you edited gas by hand or chose a “Low” preset, switch back to the market or default setting. The node’s suggested price was 60 gwei when we checked.
  3. If you set fees manually, use at least 60 gwei for the gas price. If you see separate fields, set the max priority fee to at least 60 gwei and the max fee at or above it.
  4. Check your network settings. Core mainnet is chain ID 1116 (0x45c), and the official RPC is https://rpc.coredao.org, per the Core network configuration docs. Our Add Core to MetaMask guide walks through it.
  5. Make sure you hold enough CORE. Once the price is fixed, the next check is your balance. If that fails, see how to get CORE for gas fees.

A note on third-party RPCs

Different RPC providers can run different price limits. In our test, Ankr’s public Core endpoint (rpc.ankr.com/core) didn’t return “transaction underpriced” for sub-60 gwei transactions. It skipped straight to the balance check, and it even returned a transaction hash for a zero-fee transaction. A few minutes later, none of the three endpoints we queried could find that transaction, and it had no receipt. The lesson: a node accepting your transaction doesn’t guarantee it will be mined. If a low-fee transaction “sent” but never confirms, the price floor is a likely reason.

How to fix it in scripts (ethers, viem, Hardhat)

Most developer cases come from hard-coded fees copied from Ethereum configs. Two safe patterns:

  • Ask the node instead of hard-coding. With ethers v6.17.0 against rpc.coredao.org, provider.getFeeData() returned gasPrice = 60 gwei and left the EIP-1559 fields as null. In the ethers source, those fields are only filled when the latest block has a non-zero base fee. A wallet.populateTransaction() call then produced a legacy (type 0) transaction at 60 gwei, which passes.
  • If you must set fees, set a floor. Use max(eth_gasPrice, 60 gwei) for legacy transactions, or the same value for maxPriorityFeePerGas on type-2 transactions. Avoid Ethereum-style priority fees like 1–2 gwei.
// ethers v6
const fee = await provider.getFeeData();          // gasPrice: 60 gwei on Core (Nov 2026)
const floor = ethers.parseUnits("60", "gwei");
const gasPrice = fee.gasPrice > floor ? fee.gasPrice : floor;
await wallet.sendTransaction({ to, value, gasPrice });

In Hardhat, check whether your core_mainnet network entry has an old fixed gasPrice. Some older public configs pinned 30 gwei for Core mainnet, which is below the floor we measured. Remove it or raise it.

“Transaction underpriced” vs. “replacement transaction underpriced”

These look alike but have different causes:

  • Transaction underpriced: your fee is below the node’s minimum (60 gwei on Core’s official RPC in our test). It applies to any new transaction.
  • Replacement transaction underpriced: you’re reusing the nonce of a pending transaction (speed-up or cancel) without raising the fee enough. Geth’s default --txpool.pricebump is 10%. Our separate guide covers replacement transaction underpriced.

A third related message, max fee per gas less than block base fee, is about the base fee rather than the tip. That’s rare on Core while the base fee reads 0.

FAQ

Is 60 gwei an official Core protocol rule?

Not that we could find. It isn’t hard-coded in the core-chain client source, where the pool default is 1 wei. It’s the minimum the official and dRPC endpoints enforced when we tested. Node operators can change it, so let your wallet read the current suggested price rather than memorizing a number.

Did I lose CORE when I got this error?

No. A rejected transaction never reaches the mempool, so no gas is charged and nothing moves. You can safely send it again with a higher fee.

Why does a high max fee still fail?

Because the node checks the priority fee (tip) against the minimum. On Core, with the base fee at 0, a 1 gwei tip is “underpriced” no matter how high the max fee is.

Will a higher gas price make my transaction faster?

Not much. Recent Core blocks were using a tiny fraction of their 50,000,000 gas limit, so 60 gwei was enough to be included. Paying more mainly costs more.

Disclaimer: This article is for general educational purposes only and is not financial, investment, or technical advice. Network settings and RPC policies change; always verify current values before sending transactions.

Sources: Core network configurations, Core RPC list, Geth command-line options, MetaMask error codes, EIP-1559, live JSON-RPC tests against rpc.coredao.org, core.drpc.org and rpc.ankr.com/core on November 17, 2026.

Recent Posts

  • “tx fee exceeds the configured cap” on Core: Fix the 1 CORE RPC Limit
  • Zazzle Payout Schedule: When Do Zazzle Creators Get Paid? (2026)
  • “Transaction Underpriced” on Core: Fix the 60 Gwei Minimum
  • What Happens to EE Bonds After 30 Years? Payout, Paper Bonds and Taxes
  • USDT and USDC on Core: Contract Addresses and How to Add Them to MetaMask
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