[proposal] eth_getLogs unreliable on L2 providers, stops validation.

[RobertoSnap]

Is your feature request related to a problem? Please describe.
Im always frustrated when suddenly VPs are treated as invalid.

We are checking validity through

 async validVP(jwt: string) {
    try {
      await this.agent.handleMessage({
        raw: jwt,
      });
      return true;
    } catch (error) {
      console.log('VP not valid => ', error);
      return false;
    }
  }

This then returns

JWT not valid =>  Error: Unsupported message type

Going abit deeper:

The reason

The cause

https://status.alchemy.com/

Describe the solution you'd like

1. Better error messages for what goes wrong when validating a VP.
2. Could there be a backup method for resolving did:ethr if eth_getLogs are failing?

Describe alternatives you've considered
Switching to L2 node providers while they are haveing trouble. Like Infura, but conspiring if they also have same issues. Though i dont have a good way of detecting it.

[mirceanis]

Excellent bug report!

We're already working on better error handling #588 and better verification api #375

In the meantime, perhaps we can leverage FallbackProvider/defaultProvider from ethersjs https://docs.ethers.io/v5/api/providers/#providers-getDefaultProvider when L2 providers fail. But I suppose this requires eth_getLogs to signal failure; I'm not sure if it actually happens.

I'll try to come back with some configuration example with these fallbacks

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.