Best practices on loading RPCs from a single source

[PaulRBerg]

Problem

When using Envio, there are two use cases for specifying RPCs:

1. Fallback RPCs
2. Loading data from other contracts (e.g. ERC20 token metadata such as symbol) using a Viem client

In the 2nd use case, is there any way to load the RPC from the YAML config, so that the RPCs don't have to be defined/maintained in multiple places?

Solution: getConfigByChainId?

I suppose the getConfigByChainId utility could be used for this. Could you confirm? Will this method return the networks object for the chain ID?

And a related question: can HyperSync be used in the Viem client?

[DZakh]

No, getConfigByChainId won't probably work, and we have plans to deprecate it in v3. What about using env vars and reading them both from code and config.yaml. I know that it's not the best solution, but we want to polish effect API cache first, before introducing a built-in RPC client on top of it.

[PaulRBerg]

That works. Thanks for confirming. I was planning to use getConfigByChainId before your answer.

[DZakh]

And a related question: can HyperSync be used in the Viem client?

No