We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Geth version: v1.4.8 OS & Version: Windows/Linux/OSX Commit hash : f5ba30e
Metamask should not show warning on their page.
there is a warning in Metamask for BSC.
Step#1.connect metamask to pancake or other DApp with BSC network https://pancakeswap.finance/swap?chain=bsc Step#2.try swap
Step#3.after confirm, there would be warning shown in Metamask by this tool: https://www.blockaid.io/
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.
maxFeePerGas
maxPriorityFeePerGas
The text was updated successfully, but these errors were encountered:
zzzckck
No branches or pull requests
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.
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
Step#3.after confirm, there would be warning shown in Metamask by this tool: https://www.blockaid.io/
Backtrace
No backtrace, but some error log printed in chromium console:
Seems like there is some issue with
maxFeePerGas
andmaxPriorityFeePerGas
, both are 0, but actually BSC accept zero gas price right now.The text was updated successfully, but these errors were encountered: