Merge branch 'develop' into feat-livepeer-integration-dev

.env.example

@@ -214,12 +214,6 @@ SMALL_ANTHROPIC_MODEL=          # Default: claude-3-haiku-20240307
 MEDIUM_ANTHROPIC_MODEL=         # Default: claude-3-5-sonnet-20241022
 LARGE_ANTHROPIC_MODEL=          # Default: claude-3-5-sonnet-20241022
 
-# VoyageAI Configuration
-VOYAGEAI_API_KEY=
-USE_VOYAGEAI_EMBEDDING=         # Set to TRUE for VoyageAI, leave blank for local
-VOYAGEAI_EMBEDDING_MODEL=       # Default: voyage-3-lite
-VOYAGEAI_EMBEDDING_DIMENSIONS=  # Default: 512
-
 # Heurist Configuration
 HEURIST_API_KEY=                # Get from https://heurist.ai/dev-access
 SMALL_HEURIST_MODEL=            # Default: meta-llama/llama-3-70b-instruct
@@ -514,7 +508,9 @@ GIPHY_API_KEY=
 # OpenWeather
 OPEN_WEATHER_API_KEY=           # OpenWeather API key
 
-
+#GITCOIN Passport
+PASSPORT_API_KEY= #Gitcoin Passport key
+PASSPORT_SCORER= #Scorer number
 
 # EchoChambers Configuration
 ECHOCHAMBERS_API_URL=http://127.0.0.1:3333

agent/package.json

@@ -50,6 +50,7 @@
         "@elizaos/plugin-flow": "workspace:*",
         "@elizaos/plugin-gitbook": "workspace:*",
         "@elizaos/plugin-story": "workspace:*",
+        "@elizaos/plugin-gitcoin-passport": "workspace:*",
         "@elizaos/plugin-goat": "workspace:*",
         "@elizaos/plugin-lensNetwork": "workspace:*",
         "@elizaos/plugin-icp": "workspace:*",

agent/src/index.ts

@@ -32,6 +32,7 @@ import {
     settings,
     stringToUuid,
     validateCharacterConfig,
+    parseBooleanFromText,
 } from "@elizaos/core";
 import { zgPlugin } from "@elizaos/plugin-0g";
 
@@ -70,6 +71,7 @@ import { flowPlugin } from "@elizaos/plugin-flow";
 import { fuelPlugin } from "@elizaos/plugin-fuel";
 import { genLayerPlugin } from "@elizaos/plugin-genlayer";
 import { giphyPlugin } from "@elizaos/plugin-giphy";
+import { gitcoinPassportPlugin } from "@elizaos/plugin-gitcoin-passport";
 import { hyperliquidPlugin } from "@elizaos/plugin-hyperliquid";
 import { imageGenerationPlugin } from "@elizaos/plugin-image-generation";
 import { lensPlugin } from "@elizaos/plugin-lensNetwork";
@@ -830,7 +832,7 @@ export async function createAgent(
             getSecret(character, "ABSTRACT_PRIVATE_KEY")
                 ? abstractPlugin
                 : null,
-            getSecret(character, "B2_PRIVATE_KEY") ? b2Plugin: null,
+            getSecret(character, "B2_PRIVATE_KEY") ? b2Plugin : null,
             getSecret(character, "BINANCE_API_KEY") &&
             getSecret(character, "BINANCE_SECRET_KEY")
                 ? binancePlugin
@@ -873,6 +875,9 @@ export async function createAgent(
             getSecret(character, "LETZAI_API_KEY") ? letzAIPlugin : null,
             getSecret(character, "STARGAZE_ENDPOINT") ? stargazePlugin : null,
             getSecret(character, "GIPHY_API_KEY") ? giphyPlugin : null,
+            getSecret(character, "PASSPORT_API_KEY")
+                ? gitcoinPassportPlugin
+                : null,
             getSecret(character, "GENLAYER_PRIVATE_KEY")
                 ? genLayerPlugin
                 : null,
@@ -1114,3 +1119,16 @@ startAgents().catch((error) => {
     elizaLogger.error("Unhandled error in startAgents:", error);
     process.exit(1);
 });
+
+// Prevent unhandled exceptions from crashing the process if desired
+if (process.env.PREVENT_UNHANDLED_EXIT && parseBooleanFromText(process.env.PREVENT_UNHANDLED_EXIT)) {
+    // Handle uncaught exceptions to prevent the process from crashing
+    process.on('uncaughtException', function(err) {
+        console.error("uncaughtException", err);
+    });
+
+    // Handle unhandled rejections to prevent the process from crashing
+    process.on('unhandledRejection', function(err) {
+        console.error("unhandledRejection", err);
+    });
+}

client/src/components/chat.tsx

@@ -61,10 +61,13 @@ export default function Page({ agentId }: { agentId: UUID }) {
 
     const handleKeyDown = (e: React.KeyboardEvent<HTMLTextAreaElement>) => {
         if (e.key === "Enter" && !e.shiftKey) {
+            e.preventDefault();
+            if (e.nativeEvent.isComposing) return;
             handleSendMessage(e as unknown as React.FormEvent<HTMLFormElement>);
         }
     };
 
+
     const handleSendMessage = (e: React.FormEvent<HTMLFormElement>) => {
         e.preventDefault();
         if (!input) return;

docs/community/Contributors/weekly-contributor-meeting/2024-12-10.md

@@ -0,0 +1,69 @@
+---
+title: "Weekly Contributor Meeting Notes"
+date: 2024-12-10
+description: "Notes from the first ai16z Eliza contributor meeting, addressing key challenges in stability, plugins, and codebase organization, with proposed solutions for improvement."
+---
+
+# Weekly Contributor Meeting Notes
+
+(December 10, 2024 4:00 PM PST)
+
+**Taming the Beast, The Quest for AI Agent Stability**
+
+
+## Summary
+
+This first weekly meeting of maintainers and contributors for the ai16z Eliza repo, organized by Odilitime. The discussion revolved around improving the stability, maintainability, and organization of the rapidly growing project.
+
+**Key Issues and Concerns:**
+
+*   **Instability and Breakages:** Frequent crashes and bugs were reported, especially after merging new code. Main was breaking repeatedly despite fixes.
+*   **Plugin Management:** There was a hold on merging new plugins due to concerns about quality, maintainability, and the need for a more robust process.
+*   **Code Quality and Modularity:** Concerns were raised about the overall quality and modularity of the codebase, particularly regarding how plugins were integrated. The lack of clear separation between core logic and plugins was causing issues.
+*   **Testing:** The absence of comprehensive testing, especially for plugins and adapters, was identified as a major problem contributing to instability.
+*   **Documentation:** The documentation was incomplete and outdated, making it difficult for new contributors to understand the project and how to use plugins.
+*   **Organization and Planning:** The need for better organization, planning, and communication was highlighted, particularly for coordinating contributions and defining a clear roadmap.
+*   **Contributor Incentives:** The discussion touched on how to properly incentivize and reward contributors, with considerations for retroactive rewards and avoiding a "mercenary" culture.
+
+**Proposed Solutions and Action Items:**
+
+*   **Branching Strategy:** Enforce pushing new features to the `develop` branch instead of `main` to prevent constant breakages. Close PRs targeting `main` that are not bug fixes.
+*   **Plugin V2 API:** Consider creating a new V2 API for plugins that better distinguishes between clients and adapters, allowing for a cleaner separation of concerns.
+*   **Monorepo Tools:** Explore using monorepo tools like Turbo or NX to better manage dependencies and potentially break down the project into smaller, more manageable modules.
+*   **Testing Framework:** Develop a testing framework to make it easier to write tests for plugins, adapters, and other components. Implement end-to-end tests to ensure basic functionality.
+*   **Plugin Requirements:** Draft new requirements for plugins, including contact information for maintainers and possibly a migration path to a V2 API.
+*   **JSON Configuration:** Allow specifying plugins in the character JSON configuration file to enable easier multi-tenant agent setup.
+*   **Documentation Improvement:** Prioritize improving the documentation, potentially with the help of an AI agent to keep it up-to-date.
+*   **Organization and Communication:** Use GitHub issues more effectively for tracking tasks and discussions. Consider using tools like Gorse to visualize code contributions.
+*   **Contributor Roles:** Clarify roles and responsibilities, particularly regarding release engineering, architecture, and DevOps.
+*   **Contributor Rewards:** Develop a system for rewarding contributors, potentially using quadratic funding and considering retroactive rewards.
+*   **Regular Meetings:** Establish regular meetings (weekly, as suggested) to improve communication and coordination among maintainers and contributors.
+*   **AI Agents:** Utilize AI agents to assist with documentation, onboarding, and other tasks.
+
+**Participants:**
+
+The meeting involved several key participants, including Odilitime (the organizer), Jin, 0x8664,and several others who actively contributed to the discussion.
+
+**Overall Tone:**
+
+The tone of the meeting was constructive and collaborative, with participants expressing a shared desire to improve the Eliza Repo and address the challenges of its rapid growth. There was a sense of urgency to implement solutions and establish better processes to ensure the project's long-term success.
+
+
+## Quotables
+
+1. **"We kind of put a hold on merging new plugins and I started going through the repo last night and actually flagging which PRs are just straight up new plugins." (00:01:55)**
+    *   This is a hot take because it signals a significant shift in the project's approach to handling new plugins. It implies that the previous process was not sustainable, and the decision to halt new plugin merges could be controversial among contributors eager to add their work. It raises questions about the criteria for accepting plugins and the long-term vision for plugin integration.
+
+2. **"Yeah, what I would love if we can manage- it is to get people pushing to develop and not main because main keeps like- we fix main and then it re breaks and this is the same." (00:02:19)**
+    *   This highlights a major pain point in the development process and suggests a stricter control over the `main` branch. This could be controversial as it restricts contributors' ability to directly merge into `main` and might be perceived as a slowdown in development, even though the intention is to increase stability.
+
+3. **"So one thing we were kind of thinking about is, you know, how we could potentially segment the repository because there's functionally like the core of this repository is agent folder, right?" (00:08:05)**
+    *   This is a hot take as it proposes a fundamental change to the structure of the repository. Segmenting the repository could be a significant undertaking and might face resistance or debate about the best way to implement modularity. It suggests a potential shift from a monolithic architecture to a more modular one, which has implications for development and maintenance.
+
+4. **"I think we could use some kind of organization, I know Rudolph and other folks are doing, and then the ability to execute against it. I'm not sure if there's any kind of, you know, documents we have any, you know, Google Sheets, you know, any sort of structure so that we can kind of not lose things in the discord." (00:16:55)**
+    *   This take openly criticizes the current state of organization and communication within the project. The call for a more structured approach, moving beyond Discord chats, implies that the current methods are insufficient and potentially hindering progress. This could spark debate about the best tools and processes for project management.
+
+5. **"If you're doing things that are adding value, I do want to do some stuff with quadratic funding in the future. Because right now, it's just very deterministic, based on objective data." (00:39:45)**
+    *   The introduction of quadratic funding is a hot take, especially within an open-source context. It's a relatively novel approach to funding that can be complex to implement and may be met with skepticism or misunderstanding. The discussion around contributor rewards and avoiding a "mercenary" culture adds another layer of complexity and potential controversy to this topic. It's unclear how this would work, given that quadratic funding typically requires tokens, and they stated they are not creating a token.
+
+These takes represent key areas of change, potential conflict, and important decisions that will shape the future of the ai16z Eliza project. They often challenge the status quo, propose significant changes, and touch on sensitive topics like code quality, project organization, and contributor compensation.

docs/community/Contributors/weekly-contributor-meeting/2024-12-31.md

@@ -0,0 +1,66 @@
+---
+title: "Weekly Contributor Meeting Notes"
+date: 2024-12-31
+description: "Meeting notes covering ElizaOS's contributor discussions on improving developer onboarding, CI/CD pipelines, funding models, and technical improvements to the core platform."
+---
+
+# Weekly Contributor Meeting Notes
+
+(December 31, 2024 4:00 PM PST)
+
+**Streamlining Contributor Experience and Funding Models**
+
+
+## Summary
+
+This was a weekly contributor meeting for ElizaOS, an open-source project by ai16z building an AI agent framework.
+
+**1. Discussion on Improving the Onboarding Experience:**
+
+*   A contributor raised concerns about the default use of local Llama as an inference provider, which caused issues for users without GPUs or sufficient hardware.
+*   They proposed offering alternative free API providers (like Together, Google AI Studio, and others) with clear documentation to make the initial setup smoother for beginners.
+*   The idea was to have a dedicated "inference" channel on Discord to list free inference options and pin them for easy access.
+*   They also discussed the possibility of a user-friendly Electron app for launching agents in the future.
+
+**2. Priorities and Challenges in the Codebase:**
+
+*   **CI/CD Pipeline:** The current CI/CD process was identified as a major bottleneck. Merging PRs was slow and complex, requiring multiple maintainers to focus on a single PR at a time. They needed a way to run tests without pulling the entire repo for every commit and to ensure that passing tests wouldn't break the `develop` branch.
+*   **Developer Experience (DevEx) vs. New Features:** There was a discussion about the need to prioritize DevEx improvements and bug fixes over adding new features. Many contributors were focused on building new plugins rather than improving the core codebase.
+*   **Incentivizing Contributions:** The group discussed the need for better incentives to encourage contributions to DevEx and core improvements. Ideas included bounties, micro-bounties, and clearer communication about priorities through issue tagging.
+*   **Financials and Funding:** The lack of a clear process for allocating funds and paying contributors was a significant blocker. They needed a system for tracking contributions and distributing rewards, possibly through a retroactive public goods funding (RetroPGF) model.
+
+**3. Deep Dive into Funding and RetroPGF:**
+
+*   The main obstacle to implementing RetroPGF was the lack of a system to map Discord users to wallet addresses and GitHub accounts.
+*   A contributor volunteered to work on this issue full-time, as it was crucial for both rewarding past contributions and establishing a framework for future funding.
+*   They discussed using account abstraction (smart accounts) to create wallets based on social logins (GitHub or Google), potentially simplifying the process.
+*   The tip bot was also considered as a possible solution for distributing rewards.
+
+**4. Technical Discussion on Embeddings and RAG:**
+
+*   A contributor asked about improving the RAG (Retrieval-Augmented Generation) pipeline, inspired by the performance of AIXBT on Twitter.
+*   They discussed the location of embedding-related code in the Eliza codebase (searching for `get_remote_embeddings`) and the issue of zero vectors being used in place of actual data.
+*   There was a brief discussion about how to feed external data (PDFs, Markdown files) into Eliza for context, with a mention of the `knowledge` field in character files and the limitations of the current room-based scoping of knowledge.
+
+**5. Action Items and Next Steps:**
+
+*   **Prioritize Issues:** Create and categorize issues into DevEx, product stability, and feature requests to guide contributions.
+*   **Improve CI/CD:** Investigate ways to streamline the CI/CD pipeline and automate testing.
+*   **Funding and Wallet Mapping:** Work on mapping Discord/GitHub accounts to wallets to enable RetroPGF and other funding mechanisms.
+*   **Badges:** Explore the possibility of creating custom GitHub badges to incentivize contributions.
+*   **Investigate Embeddings:** Research and address the zero vector issue and improve the RAG pipeline.
+*   **Shaw's Conversation on X:** Gather information about Shaw's conversation on X regarding bot monetization and platform guidelines.
+
+**6. Concerns about Bot Behavior and Monetization:**
+
+*   The group discussed Shaw's concerns about agents being used as "reply guys" on Twitter and the need to be good stewards of the platform.
+*   They acknowledged that the current Twitter client implementation might violate Twitter's terms of service and discussed the importance of educating users about the risks.
+*   There was a consensus that monetizing bots could negatively impact the X platform and that this should be avoided.
+
+**7. Closing Remarks:**
+
+*   Participants emphasized the value of these meetings for new developers and the importance of clear communication and documentation.
+*   They reiterated the need to focus on core improvements and DevEx, in addition to building new features.
+*   The meeting concluded with a sense of optimism and a commitment to addressing the identified challenges.
+
+In essence, the meeting was a productive discussion about the challenges and opportunities facing the ElizaOS project. The participants identified key areas for improvement, including the onboarding experience, CI/CD pipeline, funding mechanisms, and the need to balance new feature development with core improvements. They also discussed the ethical implications of AI agents on social media platforms and the importance of responsible development.