Reduce queries to ENS to get the resolver contract

[sebastinez]

Hi folks,

I'm working currently on the Radicle Webclient (https://app.radicle.network) and we have plenty of lookupAddress and resolveName calls for our UI.
Now for every call ethers.js requests the ENS resolver contract, which is usually stays the same for a defined identity.
To reduce queries and make our UI more "snappy" we would like to provide the resolver as a optional argument to lookupAddress and resolveName.

Would that be something you are interested in?
We could provide a PR to implement it.

I could imagine for example for lookupAddress:

-    async lookupAddress(address: string | Promise<string>): Promise<string> {
+    async lookupAddress(address: string | Promise<string>, resolverAddress?: string): Promise<string> {
        address = await address;
        address = this.formatter.address(address);

        const reverseName = address.substring(2).toLowerCase() + ".addr.reverse";

-       const resolverAddress = await this._getResolver(reverseName);
+       resolverAddress = resolverAddress ?? await this._getResolver(reverseName);
        if (!resolverAddress) { return null; }

Please let me know what you think!
Best regards!

[ricmoo]

For that purpose, you might be interested in using the provider.getResolver(name).

I don’t think the library should maintain a cache, as there are cases where the resolver changes and then a lot of functionality needs to be added around setting cache expiry policies and a way to flush the cache.

It would be a fairly simple extension to add as a sub-class of provider though. :)

[sebastinez]

Hey @ricmoo, thanks for your response!

Yeah I was already using provider.getResolver(name) but I would like to provide the obtained resolver as optional input to functions like lookupAddress to avoid one unnecessary query.
But yeah I guess that I could write my own lookupAddress function, where I can have the getResolver fn call as optional to optimize the loading times.