Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add multichain provider in addition to existing providers #348

Closed
wants to merge 7 commits into from

Conversation

alexcos20
Copy link
Member

In current main, we can run 2 providers.

This PR adds an additional provider (ip: 172.15.0.104), running the multichain version, but sharing the same private key with provider1.

This will help us to test the backwards compatibility by doing a test:

  • publish assets using 172.15.0.4 (provider1) as serviceEndpoint
  • update metadata, and change serviceEndpoint to point to 172.15.0.104 (multichain provider)
  • test consume

@trentmc
Copy link
Member

trentmc commented May 11, 2023

@alexcos20 I think this PR is now obsolete because Provider is always multichain. Right? If yes, then we can close the PR and delete the branch (dual_provider_version)

@mihaisc mihaisc closed this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants