Feat: cashtags #200
Closed
Feat: cashtags #200
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
|
This is a cool PR but a lot has drifted, still relevant? |
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.
Background
Goal - Eliza should be able to verify and use "real" tokens when trading or conversing with users.
What does this PR do?
What kind of change is this?
Features - add Cashtag action with Dexscreener API
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
Converse with Eliza and ask for a Contract address for $ai16z and get the real one.
Where should a reviewer start?
Detailed testing steps