fix(providers): unifying Solana chain_id #486
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chris13524
approved these changes
Jan 22, 2024
Omnia is using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We have two chain IDs for the Solana mainnet:
We should unify the Solana mainnet chain IDs into the single standardized
solana:4sgjmw1sunhzsxgspuhpqldx6wiyjntz.This PR adds the
solana-mainnetalias for thesolana:4sgjmw1sunhzsxgspuhpqldx6wiyjntto support clients that already using thesolana-mainnet, but moving forward with the unifiedsolana:4sgjmw1sunhzsxgspuhpqldx6wiyjntfor all providers.This will solve the load balancing for the Solana chain as well.
Slack thread context.
How Has This Been Tested?
Integration test for the Solana chain.
Due Diligence