Description
What to do?
We decided that the multichain service will store the list of chains that are necessary for a particular multichain client. For example, the interop cluster could have the following URL base: https://multichain.blockscout.com/interop and will return data only for chains from interop cluster
The list of chains for .../interop... will be set on the backend and can be regulated for a particular client
The URL base will be set as a variable during a specific multichain client launch
This approach helps to use the same read-only Multichain DB for different subsets of chains (different multichain clients)
IN ADDITION TO THIS:
Multichain service should also return the rest of variables for the config for a single chain explorer as the client also renders views for a single chain info, e.g. token info per chain, etc