defaultProvider spams Etherscan API for queryFilter

[DennisKo]

I want to get the event history (for event "Transfer") for a contract. At the moment I do the following:

const contract = new ethers.Contract(
  address,
  abi,
  getDefaultProvider()
);

const filter = contract?.filters?.Transfer;
const events = await contract?.queryFilter(filter, 0, 'latest');

And that kind of works but while doing it, ethers is somehow generating A LOT of calls to https://api.etherscan.io/api?module=proxy&action=eth_getBlockByNumber.... I guess one call per Event? In my case that can be 1000s of events...

Is that a valid way to get a lot of events from history? Can I somehow suppress those extra calls (or throttle?) ?

UPDATE: This seems to be fixed by using const provider = new ethers.providers.Web3Provider(window.ethereum);. I dont know why that is though. Whats happening in the default provider thats causing those calls?

[DennisKo]

Ok I am beginning to think thats a problem/bug with the way the defaultProvider/FallbackProvider resolves queryFilter for EtherscanProvider. It fires single API calls to Etherscan for every block in the query and those are not "canceled" even though another provider already returned the result. So for example if you have a block range of 1000 blocks it will "start" all 1000 requests and these slowly resolve (probably with some timeouts in between)