[Bug]: CCIP Read ENS resolution fails
Describe the bug
Originally reported in https://github.com/MetaMask/eth-json-rpc-middleware/issues/335:
ENS resolution sometimes uses CCIP read (eip-3668) to resolve an address. That relies on a reverted execution being interpreted as a redirect. When the provider used to perform such a read is managed by this middleware, the read operation fails. My guess is that the reverted execution is somehow wrapped such that the error is no longer interpretable.
Expected behavior
ENS resolution should succeed, including addresses that use CCIP read.
Screenshots/Recordings
No response
Steps to reproduce
- Checkout the
test-apprepository locally to theens-resolutionbranch (see https://github.com/MetaMask/test-dapp/pull/362) - Start the test dapp using
yarn start - Install the MetaMask extension (any type of build)
- Ensure that the current selected chain is Ethereum Mainnet
- Navigate to the locally-hosted test dapp and connect at least one account
- Scroll to the bottom, enter
jwt.rointo the "ENS Resolution" field, then click Submit
This should resolve to an address, but it currently resolves to null instead.
Error messages or log output
No response
Detection stage
In production (default)
Version
12.1.1
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
@Gudahtt We'll need https://github.com/MetaMask/metamask-extension/pull/22875
Blocked by: https://github.com/MetaMask/core/pull/4773 https://github.com/MetaMask/metamask-extension/pull/24496 https://github.com/MetaMask/metamask-extension/pull/27700
plz fiz this, PizzaDAO needs you. We'll buy pizza for whoever does it!
- https://github.com/MetaMask/metamask-extension/pull/22875
Also related:
- https://github.com/MetaMask/core/pull/4769
- https://github.com/MetaMask/eth-json-rpc-infura/pull/114
- https://github.com/MetaMask/providers/pull/380
looks like #22875 fixed it
This issue has been fixed. Are we waiting for a release to close it?
cc @mikesposito @Gudahtt
@mirceanis Nope we are all good. Just missed closing the issue! It was included in 12.6.0