Contributing to External AI Agent Frameworks

Eliza is a simple, fast, and lightweight AI agent framework developed by ai16z DAO. It enables the deployment of autonomous AI agents on various platforms such as Twitter and Discord.

ai16z DAO has gained much notoriety in the web3 ecosystem with now hundreds of contributors and a multi-billion dollar market cap.

The purpose of this post is to gather ideas from the ICP community on how we can contribute more tools to enhance AI agents.

What would you like to see the community build? What functionalities would you like an autonomous AI agent to have on ICP?

For example, the PickPump team recently created a plugin that Eliza to auto-generate a meme token on the PickPump platform. To further accelerate DeAI on ICP, the ecosystem must develop additional tools that expand the capabilities of AI agents, whether it’s for the Eliza framework or elsewhere.

Here are a few ideas for potential plugin ideas for Eliza (also ways that an autonomous agent can interact with ICP):

  • Eliza could deploy to an ICP canister as an option instead of only Twitter, Discord, or Telegram. Would probably require building a new ICP client package on Eliza (CC: @branbuilder)
  • Trading Plugin: When prompted, Eliza (or any other agent) could trade on a DEX (such as @KongSwap, @ICPSwap, @ICPEx, @cakemaker1) on ICP. This is already a common use case for other chains.
  • Chain Fusion Plugin: Eliza can create an ICP canister, generate ECDSA and Schnorr keys, and sign transactions.
  • Verifiable Credentials Plugin: Eliza could request certified credentials for that user from the issuer (could they also issue credentials)?
  • SNS or NNS Plugin: Eliza could handle a SNS or NNS operation such as voting, following neurons, etc.

Please let us know in this thread if you have any other ideas or thoughts; we don’t expect all of the answers; we’re more than happy to help conceptualize or bring the idea to life!

19 Likes

Update on the ability to deploy AI agents built using Eliza on ICP:

@realdanmccoy and Lucid from Cypher Proxy are working on a client to enable ICP deployment, and getting feedback from @lastmjs.

10 Likes

At Seers, we are also working on AI agents. I believe there is room for improvement in HTTP outcalls to better support AI agents. One straightforward improvement is increasing the timeout: HTTP outcalls: HTTP request error. RejectionCode: SysFatal, Error: Timeout expired - #16 by let4be

Additional features to consider:

3 Likes

I’ve DMed youteam. We should get Seers more in the AI conversation, both on ICP and across the web3 ecosystem. Let’s meet and chat.

Thank you for the feedback. The points that you covered a valid and I can understand why you need them for better performance and developer experience.

A few questions:

  1. What is the minimum timeout you are looking for? What APIs are you using and what is the time to get a response from each of them?
  2. Why are you using HTTPS Outcalls to call to different models? What is the main value to developers to call model APIs using HTTPS Outcalls?
2 Likes

IPv4 support and reduction of replication can be addressed by making use of idempotent-proxy

6 Likes

@CodingFu Do you have ideas?

I believe 2 minutes would be sufficient for most of the queries we’re running, but even 1 minute would still be a great improvement over the current 30 seconds.

We aim to verify the entire computation process up to the OpenAI or Anthropic servers. We believe this approach strikes a good balance between fully on-chain and off-chain solutions while remaining economically viable. Initially, we will use it to trade and resolve prediction markets, as well as delegate voting power to AI agents, enabling them to participate in the DAO.

Thanks for sharing! We’re developing our own proxy, but I’m unsure how trustless the enclave approach truly is. In the near term, we plan to give a significant amount of voting power to AI agents, and with around $1M in our treasury, it might be worthwhile to try to eliminate any dependencies outside the IC. I expect many DAOs will pursue similar ideas in the future. Implementing a similar proxy directly inside the IC could be nice.

2 Likes

Regarding the proxy I recommend to reach out to @zensh directly to discuss your needs, unless you are 100% sure that you want and need to build your own solution.

Thanks to @marc0olo for the mention.
It’s unlikely to implement the entire proxy within IC, as the idempotency issue arises from IC’s node consensus. Solving it must happen outside IC, i.e., on a Web2 server.
TEE enclaves can build verifiable proxy, but it requires further development.

1 Like

Yeah, I meant as part of the IC, implemented by DFINITY.

Thanks for developing the proxy—I’ll definitely take a look.

I built this library for swapping token with icswap and kongswap. This lib still need groom a little bit but I used for pacapump frontend to swap directly on Kongswap. It’s great if someone can work with me to put this for plugin

3 Likes

I used it already for production of pacapump. If you have any question please ping me

1 Like

Thank you for the input; I’ll summarize and share the feedback with our team. If anyone has any other feedback on using HTTPS Outcalls to call AI-related APIs, please let us know.

Why is using the APIs on-chain important to you? Also, wouldn’t the responses be different? No worries, if you want to answer via DM.

Having an agent being able swap tokens could be interesting. What do you think are the primary use cases for the end user?

Have you joined the ai16z dao Discord?

Would love to see AI Agents on @Openchat enganging with the Community, answering questions, giving away tokens randomly, sending out tokens to new joined users with a diamond sub. and so one…

It’s hard to find a great community Mod/Manager to keep the channel active 24/7

1 Like

An OpenChat agent - would @branbuilder be able to help?

@wpb though your team hasn’t built an agent but you are familiar with the OpenChat APIs through TallyBot, have you guys considered building agents?

1 Like

I think I can support add some plug in like swap on kong and icpswap. The easy use cases here is other develop can build some thing called intent based architecture with AI. I just deep dive to intent this last two weeks.

I didn’t join the ai16z discord.

Where we can read about open chat API?

I recommend taking a look at the OpenChat architecture to understand the canister architecture.

FYI:

AI Agent Demo Days (hosted by Nader Dabit - the Head of Developer Relations at Eigenlayer and has a reach of over 150k) is a regularly occurring livestream that allows teams from any ecosystem to rapid-fire demo and talk about the AI agent that they are building. An example here.

I encourage you to apply if your team is building an AI agent to showcase your work:

1 Like