MetaMask & Wallets

Rant: So it looks like Met*mask is using default rpc instead of the rpc configured in wagmi when fetching gas estimation, which then throws 429 often for base mainnet and then users flood our support channels since there's no way to handle this well. Shouldn't wallet infer rpc url or at least not throw on estimation the error if custom gasFee values are passed?

CTO & Full Stack Developer at @rmrk. Building modular NFTs with truly on-chain composability JS maxi, tea, advaita vedanta, psychonaut
https://x.com/Yuripetusko

suggested by the dapp (wagmi transport config). But even if Metamask want to use default rpc for gas estimation (to display best gas settings) it should not throw an error when trying to send a transaction especially if explicitly passing gas fee price values manually

Is the custom RPC configured as the desired RPC inside MetaMask or is it suggested by the dapp?

yeah, i've been debugging it for the whole week, trying to set higher gasFees and limit etc etc. Finally decided to check dev console of extension window! to discover that it's not using supplied rpc when 429 happens

created a bug here

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

yeah, i've been debugging it for the whole week, trying to set higher gasFees and limit etc etc. Finally decided to check dev console of extension window! to discover that it's not using supplied rpc when 429 happens

created a bug here

https://github.com/MetaMask/metamask-extension/issues/27099

ahh, good to know. Ok in this case the bug is that they throw the error for something that I didn't ask them to do (fetch gas fee prices with default rpc that may fail with 429). Would be good to either opt-out, or handle it gracefully. Will update the issue, ty