In order to reduce devops, and also to ease deployment/maintenance for OPF, but for others, we need to make out Provider multichain capable, so it does not require multiple deployments, one per network.
Easy path to get that:
Make sure that chainId is available when provider cannot figure it out.
Provider will choose the corresponding web3 object based on chainId
Cool feature:
allow compute jobs when assets are on different chains (ie: algo on mainnet, dataset on polygon)
In order to reduce devops, and also to ease deployment/maintenance for OPF, but for others, we need to make out Provider multichain capable, so it does not require multiple deployments, one per network.
Easy path to get that:
Cool feature: