Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Metamask simulation TX return error "maxFeePerGas must be non-zero" #2517

Closed
zzzckck opened this issue Jun 19, 2024 · 0 comments
Closed
Assignees

Comments

@zzzckck
Copy link
Collaborator

zzzckck commented Jun 19, 2024

System information

Geth version: v1.4.8
OS & Version: Windows/Linux/OSX
Commit hash : f5ba30e

Expected behaviour

Metamask should not show warning on their page.

Actual behaviour

there is a warning in Metamask for BSC.
image

Steps to reproduce the behaviour

Step#1.connect metamask to pancake or other DApp with BSC network
https://pancakeswap.finance/swap?chain=bsc
Step#2.try swap
image

Step#3.after confirm, there would be warning shown in Metamask by this tool: https://www.blockaid.io/
image

Backtrace

No backtrace, but some error log printed in chromium console:

Error: simulation: fallback: (code: -32603, message: , data: Some(Object {"cause": Null, "code": Number(-32000), "message": String("maxFeePerGas must be non-zero")}))

Seems like there is some issue with maxFeePerGas and maxPriorityFeePerGas, both are 0, but actually BSC accept zero gas price right now.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant