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
By default, ethers allows CCIP reads during ENS lookups. In Otterscan, we observed that CCIP reads were also followed during calls to provider.lookupAddress, which resolves the ENS name associated with an address. This presents a privacy issue for our application, since ENS names are looked up by default as users browse with Otterscan. Is there a way to enable CCIP reads for ENS lookups (via provider.resolveName) but disable them for provider.lookupAddress? I see that lookupAddress actually calls an ENS reverse resolver under the hood.
Alternatively - and this might be the more robust route - it would be great if there were a way for us to catch attempted CCIP read attempts which failed because CCIP reads have been disabled. This would let us conditionally allow the read after getting the user's approval. Currently, ethers discards call exceptions during ENS lookup:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
By default, ethers allows CCIP reads during ENS lookups. In Otterscan, we observed that CCIP reads were also followed during calls to
provider.lookupAddress
, which resolves the ENS name associated with an address. This presents a privacy issue for our application, since ENS names are looked up by default as users browse with Otterscan. Is there a way to enable CCIP reads for ENS lookups (viaprovider.resolveName
) but disable them forprovider.lookupAddress
? I see thatlookupAddress
actually calls an ENS reverse resolver under the hood.Alternatively - and this might be the more robust route - it would be great if there were a way for us to catch attempted CCIP read attempts which failed because CCIP reads have been disabled. This would let us conditionally allow the read after getting the user's approval. Currently, ethers discards call exceptions during ENS lookup:
ethers.js/src.ts/providers/ens-resolver.ts
Line 253 in 9fd9d41
If you're interested, I list a few addresses and pages which trigger CCIP reads from reverse lookups: otterscan/otterscan#3330
Beta Was this translation helpful? Give feedback.
All reactions