feat: axelar local dev cosmos #92
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
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.
Add Local CallContract Example for Cosmos
This pull request introduces an enhancement to the Axelar Local Dev Cosmos, focusing on supporting Wasm contract deployment and facilitating the testing of cross-chain message transmission from Wasm contracts to EVM chains. For a comprehensive setup guide and further details, please refer to the documentation available here.
Key Points in This PR
CallContract Method Support: This PR currently supports only the CallContract method. We plan to extend this support to additional methods in future updates.
IBC Memo Message Specification: When sending an IBC memo message from the Cosmos to the EVM chain, it's essential to specify "Ethereum" as the destination chain. This is a critical requirement for successful message delivery, as other chain names are not supported in the current implementation.
Tests