lookupAddress() makes redundant requests to infura?

[evvvritt]

Ethers Version

5.7.2

Search Terms

lookupAddress

Describe the Problem

I'm trying to reduce my API calls to Infura and noticed that lookupAddress() makes 13 POST requests for one lookup.
7 of these requests return the same result. Is that correct?

redundant result value

{
    "jsonrpc": "2.0",
    "id": 44,
    "result": "0x1"
}

It appears to be looking up the chain ID redundantly?

(Thanks for developing this great library!! ❤️ )

Code Snippet

const INFURA_KEY = 'XXX';
const ADDRESS = 'XXX';
const provider = ethers.getDefaultProvider(`https://mainnet.infura.io/v3/${INFURA_KEY}`);
provider.lookupAddress(ADDRESS).then(ens => console.log(ens));

Contract ABI

No response

Errors

No response

Environment

Ethereum (mainnet/ropsten/rinkeby/goerli)

Environment (Other)

No response

[ricmoo]

If you use the InfuraProvider or use the StaticJsonRpcProvider (which InfuraProvider inherits) it won’t do that.

I’ve considered adding a short-lived cache to the JsonRpcProvider for chainId, but it does add some extra complexity. I prolly won’t make that change to v5, but v6 already has plenty of configuration available to the JsonApiProvider, so I could consider adding that.

For now though, using a StaticJsonRpcProvider will resolve your issues. ;)