You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the user add GOAT Network into their metamask, but Metamask can not get the correct gas for their transaction.
Design
No response
Technical Details
We dived into the issue and found that https://gas.api.cx.metamask.io/networks/2345/suggestedGasFees doesn't work. and from this comment (#25655 (comment)), it says suggestedGasFees doesn't use the chain's eth_estimateGas.
We need to use our own eth_estimateGas because GOAT Network is a Bitcoin L2, and the gas token is wrapped BTC.
GOAT Network:
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
Security
Legal
Marketing
Management (please specify)
Other (please specify)
References
No response
The text was updated successfully, but these errors were encountered:
What is this about?
When we use
"https://gas.api.cx.metamask.io/networks/2345/suggestedGasFees"
for GOAT Network to get the estimated gas, it responds:We have listed GOAT on chainlist at https://chainlist.org/chain/2345.
Scenario
When the user add GOAT Network into their metamask, but Metamask can not get the correct gas for their transaction.
Design
No response
Technical Details
We dived into the issue and found that
https://gas.api.cx.metamask.io/networks/2345/suggestedGasFees
doesn't work. and from this comment (#25655 (comment)), it sayssuggestedGasFees
doesn't use the chain'seth_estimateGas
.We need to use our own
eth_estimateGas
because GOAT Network is a Bitcoin L2, and the gas token is wrapped BTC.GOAT Network:
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: