You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This bug showed up after the upgrade from v13 to v14 of this lib in the MetaMask extension.
The environment to reproduce it has ethers@6.x as a dependency, and a simple test to reproduce would go along the lines of:
constprovider=newBrowserProvider(setup.provider);// provider managed by this middlewareconstsampleDomain='jwt.ro';// resolving a linked DNS domain uses CCIP readconstensResolver=awaitprovider.getResolver(sampleDomain);constethAddress=awaitensResolver?.getAddress();expect(ethAddress).toBe('0xd08E08a0551575eE6bcE6d56180148EB68Bca061');
The text was updated successfully, but these errors were encountered:
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.
This bug showed up after the upgrade from v13 to v14 of this lib in the MetaMask extension.
The environment to reproduce it has
ethers@6.x
as a dependency, and a simple test to reproduce would go along the lines of:The text was updated successfully, but these errors were encountered: