feat: ws specific rpc urls

[NikolasHaimerl]

We want to be able to control which indexer is using what RPC URLs, this is both because Websockets are not equally well supported by all RPC providers and we want to know the Websocket specific RPC usage, which means we have to separate the keys being used by the Websocket and poll based indexer.
Related to https://github.com/UMAprotocol/zion/pull/1153

[amateima]

Is there a way to keep using RPC_PROVIDER_URLS_ as a fallback? It would be ideal to not redeclare the RPC URL if the existing one used for polling works as expected for ws as well. Basically use WS_RPC_PROVIDER_URLS_ as a override only if declared and needed 🤔

[NikolasHaimerl]

Hm is there a way to know whether an RPC URL works for a websocket before seeing if the websocket looses it's connection?

[NikolasHaimerl]

I could do something like this:

const rpcProviders = parseEnv.parseProvidersUrls("RPC_PROVIDER_URLS_");
const wsProviders = parseEnv.parseProvidersUrls("WS_RPC_PROVIDER_URLS_");
// Merge providers, allowing WS providers to override RPC providers if defined for a chain
const allProviders = new Map([...rpcProviders, ...wsProviders]);

Does this address what you had in mind?

[amateima]

Hm is there a way to know whether an RPC URL works for a websocket before seeing if the websocket looses it's connection?

I don't think so.

[amateima]

I could do something like this:

const rpcProviders = parseEnv.parseProvidersUrls("RPC_PROVIDER_URLS_");
const wsProviders = parseEnv.parseProvidersUrls("WS_RPC_PROVIDER_URLS_");
// Merge providers, allowing WS providers to override RPC providers if defined for a chain
const allProviders = new Map([...rpcProviders, ...wsProviders]);

Does this address what you had in mind?

Something like this, yes.

 const allProviders = new Map([...rpcProviders, ...wsProviders]);

Here order matters, right? Basically wsProviders is overriding rpcProviders because it comes after

[NikolasHaimerl]

Yes that was the intention, wsProviders overwrites rpcProviders.

[NikolasHaimerl]

Addressed in

f80faa2#diff-28d5ba14aff9c78a4bbd7e0584eddc36d00a3a92b598cc44df269702404a275fR193

[amateima]

🚀