Add support for Movement Network #1621
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hi @Rahat-ch! Welcome to the ai16z community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now a ai16z contributor!
|
looks movish to me |
|
can newbies enter sir? |
|
Gmove Gmove, |
shakkernerd
approved these changes
Jan 8, 2025
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.
Relates to:
Risks
Low - non-breaking changes made to the Aptos Plugin
Background
What does this PR do?
Adds support for transacting on Movement Network Testnet and Mainnet
What kind of change is this?
New Plugin created for Movement based on existing Aptos Plugin with differences to account for Movements slight differences and future compiler differences
Why are we doing this? Any context or related work?
Allow developers in the Movement Ecosystem to start experimenting with using eliza for agents
Documentation changes needed?
Added basic instructions in readme
Testing
Updated tests for Wallet and added some tests for transfer action triggers
Where should a reviewer start?
All changes are in the packages/plugin-movement
functionally it is almost exactly like the aptos plugin with changes to ensure compatibility with movement
Detailed testing steps