Test Multichain Provider

[LoznianuAnamaria]

from @alexcos20 let's test this:

• create docker image - image "oceanprotocol/provider-py:multichain" available
• @md00ux - create CNAMEs https://v4-2.provider.NETWORK.oceanprotocol.com that points to https://v4.provider.NETWORK.oceanprotocol.com/ (for the NETWORKs: mumbai, goerli, polygon)
• create market PR that uses new CNAMES for provider URI
• publish assets (datasets & algorithms), using all known storage types: url, graphql, ipfs, smartcontract, etc
• make sure consumption works for all previous created assets
• @md00ux - deploy multichain provider to https://v4.provider.oceanprotocol.com, using private keys from existing providers (this can be done anytime, there is no deps or blocker)
• once previous steps are done, @md00ux changes all v4-2 CNAMES to point towards multichain provider (IE: https://v4-2.provider.mainnet.oceanprotocol.com/ points to https://v4.provider.oceanprotocol.com
• make sure consumption works for all previous created assets
• update market PR to use https://v4.provider.oceanprotocol.com as provider URI for all networks
• publish another set of assets (datasets & algorithms), using all known storage types: url, graphql, ipfs, smartcontract, etc
• make sure consumption works for all previous created assets

[calina-c]

@AnaLoznianu can we consider this closed? The new multichain provider is released and integrated into Barge, as well as the new Aquarius version that accurately "communicates" with the new provider. The deployed multichain provider endpoints are active and have been tested, as far as I know. Should we still keep this ticket?