"Version of JSON-RPC protocol is not supported." error

[siobh9]

Check existing issues

• I checked there isn't already an issue for the bug I encountered.

Viem Version

2.41.2

Current Behavior

We are seeing this weird error from a couple users, it's only started recently, and we can't really seem to figure out a common denominator for what's triggering it, so wanted to make an issue here to see if y'all could provide more context on what this error means, if it's expected behavior from viem, and what can be done to hedge against it.

Tickets for when this error has occurred are here for context: jk-labs-inc/confetti#5001, jk-labs-inc/confetti#5002, jk-labs-inc/confetti#4988

Thank you!

Expected Behavior

To not see this error, or at least to know what it means and what we can tell users to do to resolve it.

Steps To Reproduce

It is annoyingly unreproducible.

Link to Minimal Reproducible Example

https://jokerace.io

Anything else?

Browser and wallet info are included in the linked tickets where this error has been reported.

[jxom]

Likely behavior of your RPC provider or wallet if it just started happening. What RPC provider/wallet are you using?

[jxom]

Likely a MetaMask issue...

[siobh9]

Likely behavior of your RPC provider or wallet if it just started happening. What RPC provider/wallet are you using?

We're using Quicknode for our RPC provider on all chains - and the wallet being used is user-dependent but in each case of the above 3 tickets where we've seen it the wallet has been Metamask.

[siobh9]

Likely a MetaMask issue...

Ah oh makes sense - we'll recommend people try a different wallet or to update MM then. I couldn't find it in the docs but if there's any other context about what this error means that'd be helpful as well to explain to folks what's going on.

Thanks for the response here even though we aren't able to repro - appreciate it!

[jxom]

Closing as this isn't really a Viem issue. But if you manage to reproduce, or find the payload which produces this, we can add a workaround for MetaMask if it makes sense.

[siobh9]

Closing as this isn't really a Viem issue. But if you manage to reproduce, or find the payload which produces this, we can add a workaround for MetaMask if it makes sense.

Okay perfect, thanks so much!

[siobh9]

just noting here but we figured out how to reproduce in figured out how to reproduce in jk-labs-inc/confetti#5044 (comment). essentially this error happens if a user has our production RPC endpoint (that is allowlisted so only jokerace.io can access it, so when MM tries to hit it directly for the stuff it needs it gets this error) saved as the default one in MM.