Sentry Error: [ethjs-query] while formatting outputs from RPC '{..."execution reverted" ...} Last 30 days: 1.9K

[sentry-io]

Sentry Issue: METAMASK-J9ST

Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"message":"Internal JSON-RPC error.","data":{"code":-32000,"message":"execution reverted"},"stack":"{\n  \"code\": -32603,\n  \"message\": \"Internal JSON-RPC error.\",\n  \"dat...
  at Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"message":"Internal JSON-RPC error.","data":{"code":-32000,"message":"execution reverted"},"stack":"{\n  \"code\": -32603,\n  \"message\": \"Internal JSON-RPC error.\",\n  \... (metamask/common-1.js:27:365128)\\n    at a ()

[seaona]

Problem: this error is thrown everytime Metamask tries to resolve certain ENS domains. I'm not sure why only affects to some. One of the affected is offchainexample.eth. I'm doing further investigations

Steps to reproduce:

1. Unlock Metamask
2. Click Send ETH
3. Introduce ENS address offchainexample.eth
4. Check background console

Update: it affects all ENS domains which have set the resolver to the OffchainResolver address 0x379E5BfDf9a94b18937df48664260fD3d32F47a7. The ones using the PublicResolver address do not throw the error.

In case you also want to register an ENS domain that triggers the error, you can do the following:

1. Go to app.ens.domains
2. Type any non-existing ENS domain (examplexyz.eth)
3. Register it (you can do it on Rinkeby network)
4. Change Resolver (from 0xf6305c19e814d2a75429Fd637d01F7ee0E77d615, to 0x379E5BfDf9a94b18937df48664260fD3d32F47a7
5. Now, go to Metamask and do the Steps to reproduce the error, looking for this ENS name