fix(providers): Near chain ID to be CAIP-2 compatible
#547
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
geekbrother
changed the title
Near chain ID to be CAIP-2 compatible
geekbrother
force-pushed
the
fix/change_near_to_near_mainnet
branch
from
e664002
to
a37a275
Compare
geekbrother
force-pushed
the
fix/change_near_to_near_mainnet
branch
from
a37a275
to
0177f20
Compare
chris13524
approved these changes
Mar 1, 2024
There was a problem hiding this comment.
Technically there should be a CAIP-2 entry in ChainAgnostic/namespaces but I see an abandoned PR which matches what you've done here so approving 👍
Opening this issue for standardizing this: ChainAgnostic/namespaces#106
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
This PR changes the chain Id for the
Nearto be CAIP-2 compatible and becomesnear:mainnetinstead ofnear.According to the Grafana chain Ids requests, at the moment we don't have any Near traffic yet (we've added it recently), so we can switch it without migration.
How Has This Been Tested?
Integration tests.
Due Diligence