fix: Standardize Chain Names and Clean Up Bridge Definitions #362
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.
Hi team,
I went ahead and tackled the
TODO: FIX need to control chain naming here
in the bridge network definitions.Here's what I did:
chains
,destinationChain
,chainMapping
keys/values). This resolves the inconsistency we had.chainMapping
objects, removing mappings that were no longer needed after standardizing (likeavalanche: "avax"
). Only the essential mappings remain.chains
arrays.This should make the configuration much more consistent and reliable to work with.