-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add Mayan SDK tool #241
Conversation
enables cross-chain swaps SVM <-> EVM
* main: chore: pkg + docs priority fees added feat: Adds Allora Network price inference tool
Hey @zoli please can you make it so that both token symbols and token addresses can be accepted in the prompt. e.g |
Sure, I was a bit afraid that it might happen a mistake in recognizing the token. |
Yes, currently there is no way to break a prompt into multiple steps but having it be an option of either of the 2 would be nice. The developer using the kit could then choose whether they want to use token addresses or token names, and the end user if they're using the kit as is and parsing the actions to their agent could choose to use symbols as they're more memorable and a better user experience. |
* main: chore: remove unused import Update README.md: change 15+ actions to 60+ actions do not log kp fix: spot position balance signs fix: spot position balance type and signs fix: overall drift account usd balance fix: spot position balance type fix: perp position precision fix: drift user account balances and position amounts
@michaelessiet I've implemented using token symbol instead of contract address but one thing to note is most of the times the ai (in my case gpt4-4o-mini) before passing the symbol to the agent action replaces the symbol with contract address and mostly the address is wrong. I mostly specified in my prompts to not replace token symbols and then it worked fine. Other than the above I think this is ready to get merged. |
Sweet. Please can you remove anything EVM related as this will bloat the SDK with unnecessary dependencies. Solana Agent Kit only wants to support Solana on-chain actions so there is no need to implement EVM -> Solana bridging, only Solana -> EVM or Solana -> Solana are necessary |
Done. |
897f310
to
e846b10
Compare
hey @zoli, had to reverse the previous commit, we want the evm to svm bridging as discussed internally. on times where the ai mis-interprets it's mostly due to the tool description |
* main: fix: convert position mint to pub key chore: orca actions added
Done all requested changes. |
Pull Request Description
enables cross-chain swaps SVM <-> EVM through Mayan SDK
Related Issue
Changes Made
This PR adds the following changes:
ETHEREUM_PRIVATE_KEY
to config object for EVM to SVM swapsImplementation Details
Using Mayan SDK now the agent can swap cross-chain SVM to SVM or SVM to EVM and vice versa.
Transaction executed by agent
Example transaction:
Multiple transactions (you can see all of them in Mayan Explorer)
Prompt Used
Additional Notes
Checklist