MetaMask / MetaMask/metamask-extension

[Bug]: Gas cost in native token shows same value for all fee options despite different max base fees

Open
#39,263 0 comments 0 reactions 0 assignees View on GitHub
Gas potential-ai-ticket Sev3-low team-confirmations type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**Describe the bug**

When editing gas fees on a transaction, the gas cost displayed in the native token (e.g., POL on Polygon) shows the same value for all fee options (Low, Market, Aggressive) even though each option has different max base fee values.

For example, on Polygon:
- Low: 0.023299695 POL
- Market: 0.023299695 POL
- Aggressive: 0.023299695 POL

All show the same native token cost despite having different time estimates and presumably different gas parameters.

https://github.com/user-attachments/assets/c621b2de-6139-40bb-ab18-c665c15e0b4f

**Expected behavior**

Each gas fee option (Low, Market, Aggressive) should display a different native token cost that corresponds to their respective gas parameters. Since the max base fee differs for each option, the displayed cost in the native token should also differ.

**Screenshots/Recordings**

_Screenshots to be attached_

**Steps to reproduce**

1. Open MetaMask extension
2. Select an account on one of the affected networks (Polygon, BNB, Arbitrum, or Optimism)
3. Initiate a send transaction (any amount to any address)
4. On the transaction confirmation screen, click to edit the gas fee
5. Observe that Low, Market, and Aggressive options all show the same native token cost

**Error messages or log output**

_No error messages - this is a display/calculation issue._

**Where was this bug found?**

Live version (from official store)

**Version**

13.14.0

**Browser**

Chrome

**Operating system**

Linux

**Additional context**

**Affected networks:**
- Polygon (POL)
- BNB Chain (BNB)
- Arbitrum (ETH)
- Optimism (ETH)

**Networks NOT affected (working correctly):**
- Ethereum Mainnet
- Linea
- Base

This suggests the bug may be related to how gas costs are calculated or displayed on certain L2/sidechain networks, possibly related to EIP-1559 implementation differences or fee estimation logic specific to these chains.

**Severity**

_To be determined by internal team_

Contributor guide

Open the contributing guide

Research direction

Start in the transaction confirmation flow where gas fee options are edited and native-token costs are displayed. Reproduce the issue on Polygon, BNB Chain, Arbitrum, and Optimism, comparing the displayed costs with each option's max base fee. Done means Low, Market, and Aggressive show costs matching their respective gas parameters while Ethereum, Linea, and Base behavior remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.