Integrate EigenDA into Eliza

[Gajesh2007]

Relates to

Integration of EigenDA into Opacity adapter for proof storage and verification

Risks

Low - This integration adds optional functionality to the Opacity adapter without modifying its core verification behavior. The EigenDA integration falls back gracefully if storage/retrieval fails.

Background

What does this PR do?

• Integrates EigenDA into the Opacity adapter to store and retrieve proofs
• Adds EigenDA client initialization and configuration options
• Implements proof storage in EigenDA after generation
• Implements proof retrieval from EigenDA during verification
• Adds automatic identifier management and balance monitoring
• Provides fallback to direct verification if EigenDA operations fail

What kind of change is this?

Features (non-breaking change which adds functionality)

Documentation changes needed?

My changes require a change to the project documentation to document:

• New EigenDA configuration options in Opacity adapter
• How to set up EigenDA integration
• Environment variables needed for EigenDA

Testing

Where should a reviewer start?

Detailed testing steps

Same as Deploy Notes.

Deploy Notes

• Requires EigenDA private key and Base network RPC URL
• Requires sufficient ETH balance for storing proofs (minimum 0.001 ETH on Base)

Database changes

None - This integration uses EigenDA for storage

Deployment instructions

1. Add required environment variables:

EIGENDA_PRIVATE_KEY=your_private_key
BASE_RPC_URL=your_rpc_url

2. Install Dependencies

pnpm install

3. Build the packages

pnpm build

Discord username

Gajesh#0000

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge-queue - adds this PR to the back of the merge queue
• merge-queue-hotfix - for urgent hot fixes, skip the queue and merge this PR next

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.

[fabianhug]

I'll test this thoroughly tomorrow.

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find files modified in this PR
git diff --name-only HEAD~1

# Search for EigenDA related code
rg -l "EigenDA" 

# Search for environment variable usage
rg -l "EIGENDA_PRIVATE_KEY|BASE_RPC_URL"

# Look for adapter related files
fd adapter

Length of output: 1795

---

🏁 Script executed:

#!/bin/bash
# Check the eigenda plugin implementation
cat packages/plugin-eigenda/src/index.ts
cat packages/plugin-eigenda/src/environment.ts

# Check the opacity plugin integration
cat packages/plugin-opacity/src/index.ts

# Check the actions implementation
cat packages/plugin-eigenda/src/actions/uploadData.ts
cat packages/plugin-eigenda/src/actions/retrieveData.ts
cat packages/plugin-eigenda/src/actions/getStatus.ts

Length of output: 33990

@fabianhug The code changes look excellent! The EigenDA integration is well-implemented with:

1. Robust error handling and graceful fallbacks
2. Secure credential management through environment variables
3. Automatic balance monitoring and top-up functionality
4. Clean separation of concerns between core EigenDA functionality and Opacity integration

The implementation follows best practices and includes comprehensive logging for debugging. I'm particularly impressed with the automatic identifier management and balance monitoring features.

✅ Actions performed

Comments resolved.

[fabianhug]

check above, never seen a good comment like this, haha. I'll check for the conflicts @Gajesh2007

[odilitime]

Hello,

We are changing our plugin development strategy to be more scalable. We have moved the plugins out into their own repos and we're looking for people to either maintain those or own them on their own Github.

If you'd like to be a maintainer, file an issue in the plugin repo and join our Discord https://discord.gg/elizaos to coordinate.

If you'd like to control the plugin on your own Github, please add an issue to the plugin repo pointing to your repo, and add a modification to the registry. Submit a PR to edit the registry here: https://github.com/elizaos-plugins/registry

Closing this PR for now. Let us know if you have any questions.