How to change gas fees manually on MetaMask? (EIP-1559 Settings)

Understanding EIP-1559 and Its Impact on Gas Management

1. EIP-1559 introduced a new transaction pricing mechanism that replaced the first-price auction model with a base fee and priority fee structure.

2. The base fee is dynamically adjusted per block based on network congestion and is burned, not paid to miners.

3. Users must specify a priority fee (also known as tip) to incentivize validators to include their transactions in the next block.

4. MetaMask implements EIP-1559 by default for Ethereum and compatible EVM chains, allowing granular control over both base fee cap and priority fee.

5. Manual gas adjustments are only possible when the user toggles from “Edit” to “Advanced” mode in the transaction confirmation window.

Accessing Manual Gas Settings in MetaMask

1. Initiate a transaction—such as sending ETH or interacting with a smart contract—through the MetaMask interface.

2. Before confirming, click the “Edit” button located beneath the gas estimation summary.

3. Select “Advanced” to reveal editable fields for “Max base fee (Gwei)” and “Priority fee (Gwei)”.

4. Disable the “Auto” toggle next to each field to enable manual input.

5. Input numeric values carefully: exceeding the current network base fee cap may cause rejection, while setting priority too low risks delayed inclusion.

Interpreting Real-Time Gas Metrics

1. MetaMask displays live base fee data pulled from the latest block header via its connected RPC endpoint.

2. The “Recommended” values shown are derived from recent block history and reflect statistical percentiles of priority fees used in the last few blocks.

3. A green indicator next to the base fee field signals alignment with the current network median; red suggests deviation beyond safe thresholds.

4. The “Max fee per gas” value shown is the sum of the base fee cap and priority fee—this is the absolute upper bound the user agrees to pay.

5. Historical gas charts are not embedded in MetaMask but can be cross-referenced using external explorers like Etherscan or Blockchair for contextual validation.

Risks of Incorrect Manual Gas Configuration

1. Setting the max fee too low relative to the network’s evolving base fee results in immediate transaction failure with “replacement underpriced” or “fee too low” errors.

2. Overestimating the priority fee unnecessarily inflates transaction cost without guaranteeing faster confirmation if the base fee dominates the total.

3. Leaving the base fee cap static during periods of rapid congestion may cause indefinite pending status until the cap is manually raised or the transaction is canceled.

4. Some decentralized applications enforce minimum gas price requirements; violating them triggers revert errors before execution begins.

5. On L2 networks like Arbitrum or Optimism, EIP-1559 parameters behave differently—base fee calculations incorporate sequencer-specific logic and may not align with mainnet expectations.

Frequently Asked Questions

Q: Can I change gas fees after signing a transaction? No. Once signed, the transaction hash and fee parameters are cryptographically bound. You must cancel and resubmit with updated values.

Q: Why does MetaMask show “Base fee increased” warnings? This occurs when the base fee in the latest block exceeds the cap set in your pending transaction. The warning indicates imminent invalidation unless adjusted.

Q: Does increasing only the priority fee speed up confirmation if base fee is insufficient? No. Both components must satisfy network conditions—the priority fee cannot compensate for an inadequate base fee cap.

Q: Are gas fee settings preserved across different dApps? MetaMask retains manual gas preferences per network, not per dApp. Switching between Ethereum and Polygon resets the context, requiring reconfiguration.