MetaMask / MetaMask/metamask-extension
[Bug]: MetaMask fee estimation fails on non-EIP-1559 networks (missing suggestedMaxPriorityFeePerGas) causing pending txs and broken UI
@jpuri is already working on this.
Since Feb 3, 2026.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Describe the bug
On non-EIP-1559 EVM chains (e.g. Core DAO), MetaMask attempts to read and use EIP-1559 fee fields such as suggestedMaxPriorityFeePerGas. Since these fields are not supported by the network RPC, the value is undefined, which causes MetaMask’s fee estimation logic and UI to break.
Steps to reproduce
Attach screenshot showing error:
Cannot read properties of undefined (reading 'suggestedMaxPriorityFeePerGas')
Error messages or log output
Where was this bug found?
Live version (from official store)
Version
13.4.3
Build type
None
Browser
Chrome
Operating system
MacOS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.