feat: chainbase plugin for focEliza #3
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 @lxcong! 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!
lxcong
changed the title
|
LGTM |
cpppppp7
pushed a commit
that referenced
this pull request
Jan 13, 2025
feat: rename plugin from EVM to Arthera and update README feat: remove bridge and swap actions from Arthera plugin feat: update transfer examples and templates to use AA instead of ETH feat: update viem dependency to version 2.21.58 and adjust pnpm-lock.yaml feat: remove unused LiFi dependencies and clean up type definitions in Arthera plugin feat: remove bridge actions and templates from Arthera plugin feat: remove swap actions and templates from Arthera plugin feat: update EVM naming to Arthera feat: update README and types for Arthera mainnet integration feat: update plugin to use Arthera instead of mainnet fix: add required devDependencies fix: remove switchChain fix: update _options type to Record<string, unknown> in transferAction fix: correct log message format in transfer action to include wallet client address test: enhance transfer tests with additional wallet provider and address validation Plugin arthera merge (#3) * feat: added arthera to default character and agent * feat: renamed EVM_PRIVATE_KEY by ARTHERA_PRIVATE_KEY * fix: roll back core package * fix: workspace: version --------- Co-authored-by: Arthera Node <[email protected]> fix: run transfer test only if private key provided fix: add missing newline at end of package.json and tsconfig.json files
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
Eliza AI agents, blockchain data analytics, Chainbase
Risks
Low. This is a new feature that adds functionality without disrupting existing systems.
Background
What does this PR do?
This PR introduces a new Chainbase plugin for Eliza that enables AI agents to access and analyze blockchain data across multiple networks using natural language queries. The plugin leverages Chainbase's comprehensive data infrastructure to provide real-time insights.
What kind of change is this?
Features (non-breaking change which adds functionality)
Why are we doing this? Any context or related work?
Eliza AI agents currently lack the ability to easily access and analyze on-chain data, especially across multiple blockchain networks. This plugin bridges that gap by allowing users to query blockchain data using natural language without requiring deep technical blockchain knowledge. It unlocks powerful new analytics and insight generation capabilities for Eliza.
This work builds upon Chainbase's existing multi-chain data infrastructure and Eliza's natural language processing capabilities. It is part of the broader initiative to make blockchain data more accessible and actionable for end users.
Documentation changes needed?
My changes require a change to the project documentation.
I have updated the documentation to include:
Testing
Where should a reviewer start?
npm run testDetailed testing steps
Deployment instructions
Let me know if you need any other information to include in the PR description! I aimed to be thorough while following the provided template.
Screenshot