feat(more-actions): Lit Protocol plugin #2912
Conversation
|
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 ESLint
agent/src/index.tsOops! Something went wrong! :( ESLint: 9.19.0 ESLint couldn't find an eslint.config.(js|mjs|cjs) file. From ESLint v9.0.0, the default configuration file is now eslint.config.js. https://eslint.org/docs/latest/use/configure/migration-guide If you still have problems after following the migration guide, please stop by packages/plugin-lit/src/actions/helloLit/helloLit.tsOops! Something went wrong! :( ESLint: 9.19.0 ESLint couldn't find an eslint.config.(js|mjs|cjs) file. From ESLint v9.0.0, the default configuration file is now eslint.config.js. https://eslint.org/docs/latest/use/configure/migration-guide If you still have problems after following the migration guide, please stop by packages/plugin-lit/src/actions/tools/ecdsaSign/lit-actions/policy.tsOops! Something went wrong! :( ESLint: 9.19.0 ESLint couldn't find an eslint.config.(js|mjs|cjs) file. From ESLint v9.0.0, the default configuration file is now eslint.config.js. https://eslint.org/docs/latest/use/configure/migration-guide If you still have problems after following the migration guide, please stop by
WalkthroughThis pull request introduces comprehensive enhancements to the Lit Protocol plugin, adding multiple blockchain-related actions and utilities. The changes include new functionalities for ERC20 token transfers, Uniswap swaps, ECDSA signing, and a hello world action. The plugin now supports more complex blockchain interactions, with detailed policy management, transaction handling, and robust error checking across different network environments. Changes
Sequence DiagramsequenceDiagram
participant User
participant LitPlugin
participant LitNetwork
participant Blockchain
User->>LitPlugin: Request Action
LitPlugin->>LitNetwork: Authenticate
LitNetwork-->>LitPlugin: Session Signatures
LitPlugin->>Blockchain: Execute Transaction
Blockchain-->>LitPlugin: Transaction Result
LitPlugin->>User: Return Result
Possibly related PRs
Suggested Labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (44)
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
There was a problem hiding this comment.
Hi @madschristensen99! Welcome to the elizaOS community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now an elizaOS contributor!
|
@madschristensen99 can you resolve conflicts? |
The conflicts mentioned in the auto check have seemingly nothing to do with my code. There are a bunch of package.json files for plugins that I am not changing. The error message for the check mentions a plugin I am not changing. In addition, I see other PR's are having similar issues with the integration test. |
|
issue in you package.json syntax |
|
@coderabbitai summary |
✅ Actions performedSummary regeneration triggered. |
Relates to
Adding Lit Protocol functionality, including Lit Agent Wallet integration. This enables key management solutions including delegation for specific tasks and policies for agents.
Risks
Low risk, simply adds a plugin
Background
Full Lit Protocol plugin addition
What kind of change is this?
Feature improvement
Current key storage for Eliza agents is done locally, and there are security concerns with agent key management Lit Protocol is addressing
Lit Protocol Agent Wallet is a new way to enable controlled policies for agents.
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
I git cloned my fork, and ran the standard startup sequence. I then modified the agent/index.ts file to use plugin-lit, and it worked as intended.
Where should a reviewer start?
Looking inside of the plugin-lit package
Detailed testing steps
Discord username
@remsee
Summary by CodeRabbit
Based on the comprehensive summary, here are the release notes:
New Features
Documentation
Dependencies
These release notes provide a high-level overview of the significant changes in the Lit Protocol plugin, highlighting the new features and improvements without delving into technical implementation details.