[Bug]: 429 error on Base. Extension not using supplied rpc api

[Yuripetusko]

Describe the bug

When using wagmi with configured private rpc api url and metamask connector, metamask still uses default rpc (perhaps for quering gasFee estimation or doing eth_call simulation), which often leads to 429 error. Shouldn't Metamask use the supplied rpc api here somehow to avoid that?

Expected behavior

Metamask to use supplied rpc api for fee estimation, or handle 429 errors better

Screenshots/Recordings

Steps to reproduce

Hard to have consistent reproduction as it is dependant on public base (mainner.base.org) rpc requests load.

• set up wagmi config and supply custom rpc in transports object
• send a transaction with writeContract and then open dev console of the metamask extension
• observe that the rpc used by metamask is a default rpc (mainner.base.org), instead of the configured rpc

Error messages or log output

Error: Non-200 status code: '429'

Detection stage

In production (default)

Version

12.1.3

Build type

None

Browser

Brave, Other (please elaborate in the "Additional Context" section)

Operating system

MacOS

Hardware wallet

No response

Additional context

Both Brave and Arc browsers (both latest chromium)

Severity

• Quite critical as during busy hours, users can't submit a transaction and blame us, and we have no way to handle it

[Yuripetusko]

Alternatively, maybe if the dapp provided custom fee values, estimation shouldn't throw the error and prevent user from submitting the transaction?

[DanielTech21]

Hi @Yuripetusko

Thank you for bringing this to our attention.

Our product team will look into this and provide comments.

[Yuripetusko]

Updating with some context: As i've been told now, it is normal that wallets don't use the rpc configured by the dapp. So in this case the issue here is that Metamask throws an error for something I didn't ask for and have no control over (gas fee price estimations) and this fails the whole transaction. The 429 should either be handled more gracefully or Metamask should provide a way to opt out of gas fee fetching if I provide it myself

[tingui96]

i have the error in edge and my friend in chrome, Both in windows. I think that can be general error

[Yuripetusko]

Some context.

[Yuripetusko]

Still puzzeled that there are not many reports besides mine since we are getting ~100 sentry error instances per day with this error

[bschorchit]

Base team has adjusted rate limits on their side to minimize this issue. Did it improve the issue on your side, @Yuripetusko ?