{ "date_generated_for": "2025-01-27", "ai_news_elizaos_discord_md_2025-01-26": { "filename": "2025-01-26.md", "content": "# elizaOS Discord - 2025-01-26\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n\n- **DeepSeek Integration**: ElizaOS has already integrated DeepSeek's models (implemented two weeks prior to the public hype), allowing for reduced operational costs. Users can configure this in the `.env` file with `DEEPSEEK_API_URL`. However, some users reported DeepSeek API outages during their new model launch.\n\n- **Build & Dependency Issues**: Several users encountered runtime errors with WASM SIMD support in VMs and GPU acceleration issues. Common build errors included problems with the `@coral-xyz/anchor` module's BN export (fixed by adding `@types/bn.js` dependency) and Mistral package compatibility issues (resolved by updating to Mistral version 1.0.9).\n\n- **Plugin Development**: Developers are working on custom plugins for Twitter image posting, Solana token data fetching, and arbitrage bots. A key insight shared is that evaluator handlers need specific conditions to trigger properly.\n\n- **Knowledge Augmentation**: The new knowledge system makes it easier to augment a character's knowledge by adding files to a folder that get auto-ingested when the character starts.\n\n### Tokenomics & Business Strategy\n\n- **Treasury Management**: Shaw announced a tokenomics update about using treasury assets (AUM) to create one-sided liquidity pools paired with AI16Z tokens, aiming to generate buy pressure and price stability without selling the assets.\n\n- **Agent Marketplace/Launchpad**: The team is developing a no-code platform for launching new agents with token buyback mechanisms. This has sparked debate about whether to implement a \"Yellowstone model\" requiring token holdings to access premium services versus keeping basic agent creation free to maximize adoption.\n\n- **DegenAI Organization**: Rhota has joined to help organize DegenAI alongside Skely. The team is addressing community concerns about delayed development, particularly regarding the website and roadmap publication. Autonomous trading is working in basic form with improvements underway.\n\n### AI TV Production\n\n- The team is developing two AI-powered TV shows: an AI news/podcast show and \"Block Tank\" (similar to Shark Tank). They're implementing Unity-based solutions for displaying media on TV screens, handling lipsync with OVR LipSync plugin, and managing camera transitions.\n\n- Technical challenges include loading textures from web URLs into Unity, integrating with ElevenLabs for text-to-speech, and connecting to a news aggregator for content.\n\n## Key Questions & Answers\n\n**ElizaOS Technical**\n\nQ: How do I embed credentials into the character JSON file? \nA: Format is: `\"settings\": {\"secrets\": {\"twitter_api_key\": \"YOUR_API_KEY_HERE\", etc.}}`\n\nQ: How do I use DeepSeek with Eliza? \nA: Just set it in the env and call the plugin. Check the latest .env file for DEEPSEEK_API_URL.\n\nQ: How would the twitter username/password work when doing multiple agents on a single instance? \nA: Create different character.json files and set their own credentials for each one in the secrets section.\n\nQ: Why is my Evaluator's handler function not executing? \nA: The Evaluator handler is only called under certain conditions; you can set it to always run.\n\nQ: How often does develop get merged into main? \nA: Every 1-2 weeks.\n\nQ: Is it possible to augment a character's knowledge once they are live? \nA: Yes, the new knowledge system makes it easier by just adding files to a folder that get auto-ingested when the character starts.\n\nQ: How do I fix the error with BN import from @coral-xyz/anchor? \nA: Add @types/bn.js dependency to the core package.\n\n**Tokenomics & Business**\n\nQ: Is the ai16z token going to be the token of the future launchpad or will there be a new one? \nA: No new token.\n\nQ: What are the downsides of the liquidity pooling approach for treasury assets? \nA: The AUM appears reduced on paper and some might interpret transactions as liquidation.\n\nQ: Does the AUM getting nuked on paper matter? \nA: Not really, as long as it's positive expected value for partner tokens.\n\nQ: Will the launchpad be no-code friendly? \nA: Yes, \"it's a no code platform.\"\n\n**DegenAI**\n\nQ: Who is the current leader of DegenAI? \nA: Skely is still involved but Rhota has come in to help organize things.\n\nQ: How is degenai's website doing? \nA: The delay was caused by resourcing issues with too many concurrent projects. Now DegenAI has full-time resources staffed.\n\nQ: Was DegenAI meant to only handle autonomous trading? \nA: Other features are planned with a flexible roadmap that changes based on user/market desires.\n\n## Community Help & Collaboration\n\n- **kAI wilder** helped **Haphazardly** with Evaluator handler functions not executing by explaining that handlers only run under certain conditions and providing code to make them always run.\n\n- **fourcolors** helped **Jo** resolve build errors with the Mistral package by suggesting bumping \"@ai-sdk/mistral\" to \"1.0.9\".\n\n- **Gal** assisted **C-Money-Dev** with errors related to BN import from @coral-xyz/anchor by suggesting adding @types/bn.js dependency to the core package.\n\n- **boom** shared C# scripts with **fishai** for loading textures from URLs into Unity materials, helping with the AI TV development.\n\n- **SM Sith Lord** explained to **boom** the process of handling speak events with actor IDs and ElevenLabs voice IDs for implementing TTS from Unity.\n\n- **shaw** provided a detailed explanation to the community about the tokenomics update regarding moving AUM to one-sided LPs, clarifying how pairing treasury tokens with AI16Z creates buy pressure while providing liquidity.\n\n- **Ka_yari** helped **\u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f** manage anxiety about price drops by providing perspective on the long-term vision and advice on investment strategy.\n\n## Action Items\n\n### Technical Tasks\n\n1. **ElizaOS Core**\n - Investigate and fix runtime errors with WASM SIMD support in VMs (Mentioned by: Deepdelver)\n - Fix GPU acceleration issues with CUDA through llama (Mentioned by: Josh \u2600)\n - Update DeepSeek integration documentation (Mentioned by: Vex)\n - Add @types/bn.js dependency to fix Solana plugin errors (Mentioned by: Gal)\n - Update Mistral package to version 1.0.9 to resolve build errors (Mentioned by: fourcolors)\n - Fix Evaluator handler execution issue (Mentioned by: kAI wilder)\n - Implement rate limiting for Twitter actions using configurable parameters (Mentioned by: Addy)\n - Fix DeepSeek API integration issues (Mentioned by: RoomTemp IQ)\n - Implement a solution to prevent agents from getting stuck in Twitter reply loops (Mentioned by: [elizaos] )\n\n2. **Tokenomics & Business**\n - Implement one-sided liquidity pools with treasury assets against ai16z token (Mentioned by: shaw)\n - Deploy AI16Z on Base blockchain via wormhole bridge (Mentioned by: DorianD)\n - Launch agent marketplace/launchpad (Mentioned by: DorianD)\n - Implement Yellowstone model for tiered services (Mentioned by: Akin)\n - Create token sink mechanisms to increase buy pressure (Mentioned by: mat)\n - Integrate with Coinbase for listing (Mentioned by: mat)\n\n3. **DegenAI**\n - Improve autonomous trading with better data and strategies (Mentioned by: rhota)\n - Develop integration with other AI agents in Telegram/Discord (Mentioned by: rhota)\n - Create features similar to Eliza for token analysis and trading commands (Mentioned by: tigerguo.)\n\n4. **AI TV Production**\n - Implement texture loading for TV screens in Unity (Mentioned by: boom)\n - Integrate OVR LipSync plugin with ElevenLabs TTS (Mentioned by: boom)\n - Create camera system for TV media display (Mentioned by: boom)\n - Set up new news aggregator with daily JSON (Mentioned by: jin)\n - Fork open source version with Toxsam avatars (Mentioned by: boom)\n - Refactor Unity code for better maintainability (Mentioned by: boom)\n - Create three 3D environments for Block Tank (Mentioned by: SM Sith Lord)\n\n### Documentation Needs\n\n1. **ElizaOS**\n - Create guide for embedding API credentials in character JSON (Mentioned by: Mr. Stark)\n - Update tokenomics documentation (Mentioned by: Atexela_)\n - Create guide for limiting agent on-chain interactions to specific users (Mentioned by: El Pulpo \ud83d\udc19)\n - Document how to use the new knowledge system (Mentioned by: Mad)\n - Create guide for running multiple agents with separate Twitter credentials (Mentioned by: mike\ud83c\udded\ud83c\uddfa)\n - Create guide for integrating Eliza with existing web applications (Mentioned by: Deuth)\n\n2. **Business & Marketing**\n - Create article explaining how DeepSeek is bullish for open source AI and ai16z's position (Mentioned by: smetter)\n - Publish high-level roadmap for DegenAI (Mentioned by: rhota)\n - Release tokenomics information for DegenAI (Mentioned by: tigerguo.)\n - Consolidate all tokenomics mechanisms into dedicated documentation (Mentioned by: jin)\n - Create a whitepaper for tokenomics (Mentioned by: witch)\n\n3. **AI TV**\n - Create documentation for Unity codebase (Mentioned by: boom)\n - Document production roles and workflows for creating episodes (Mentioned by: SM Sith Lord)\n\n### Feature Requests\n\n1. **ElizaOS Agents**\n - Implement tweet automation patterns (e.g., emoji every 10th tweet) (Mentioned by: dragonlord)\n - Support for self-hosted Ollama models (Mentioned by: 0xhellowolf)\n - Add WhatsApp chat data processing (Mentioned by: xLuisCumbi)\n - Implement Discord image posting capability (Mentioned by: tardicorn)\n - Add RSS feed integration (Mentioned by: clydedev | SG-1 Validator)\n - Create a plugin for Twitter image posting (Mentioned by: ivorad)\n - Implement a solution to make agent responses more varied and less repetitive (Mentioned by: mike\ud83c\udded\ud83c\uddfa)\n - Add support for DeepSeek reasoning engine (Mentioned by: TroyMurs)\n\n2. **DegenAI & Social**\n - Implement Twitter posting capabilities similar to AIXBT or MOBY (Mentioned by: NkT)\n - Create a Telegram DegenAI similar to RICK for token information (Mentioned by: NZD_Aaron)\n - Create AUM leaderboard website showing LP positions and token allocations (Mentioned by: jin)\n\n3. **AI TV**\n - Implement personality profiles for AI characters (Mentioned by: fishai)\n - Set up submission form for Block Tank contestants (Mentioned by: SM Sith Lord)\n - Create a demo showing ElizaOS using DeepSeek to digest quarterly reports and create presentations (Mentioned by: DorianD)\n - Implement a scheduled weekly TV show/livestream format (Mentioned by: DorianD)\n - Develop Block Tank feature (Mentioned by: jin)" }, "ai_news_elizaos_discord_md_2025-01-25": { "filename": "2025-01-25.md", "content": "# elizaOS Discord - 2025-01-25\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n- **DeepSeek R1 Integration**: Users report positive experiences with DeepSeek R1, noting its solid reasoning capabilities and cost-effectiveness compared to OpenAI. Multiple users are exploring proper configuration methods for DeepSeek as a model provider in their agents.\n- **Twitter/X Integration Challenges**: Many users experiencing login failures, authentication issues, and problems with agents posting in incorrect formats (including JSON or thinking monologues). Solutions discussed include using VPNs, setting up proxies, and verifying accounts with blue checks.\n- **Database Configuration**: Discussions about switching from SQLite to PostgreSQL/Supabase for better persistence. Users implementing knowledge systems to allow agents to access and utilize stored information.\n- **Memory Issues**: A brief mention of a \"memory issue fixed\" by 0xCatnipKing suggests some development progress.\n- **WebAssembly SIMD Support**: A user (Deepdelver) experienced runtime errors related to WebAssembly SIMD support when trying to build ElizaOS on a VM, specifically mentioning \"Wasm SIMD unsupported\" errors.\n- **Plugin Development**: Users creating and modifying plugins for various functionalities like Solana blockchain integration, web search, and Twitter actions.\n\n### Tokenomics & Treasury Management\n- **Major Tokenomics Update**: Shaw announced a significant update where the DAO plans to use its treasury assets (valued at $15-30M) to create one-sided liquidity pools paired with AI16Z tokens. This strategy aims to generate buy pressure and provide liquidity for partner tokens while avoiding direct selling of treasury assets.\n- **Value Accrual Framework**: Jin and timshel outlined a vision centered on \"attention/code/capital\" as the core pillars for token value growth:\n - Attention: Proliferating ElizaOS usage\n - Code: Improving ElizaOS functionality\n - Capital: Value accrual to treasury\n- **Revenue Models**: Discussions explored multiple potential revenue models including agent marketplace fees, investment strategies (where ai16z could function as a tier-1 investor in startups), launchpad services, and revenue sharing mechanisms.\n- **Launchpad Development**: A no-code launchpad platform was described as \"imminent\" by Shaw.\n\n### AI16Z & DegenAI Integration\n- **Super Agent Concept**: Community members, particularly tigerguo, expressed interest in understanding how DegenAI and Eliza might merge to create a \"super agent\" with enhanced capabilities.\n- **Web3 Industry Tools**: Feature requests include token analysis, blockchain transactions via voice commands, and optimized LP yield pool information.\n- **Leadership Changes**: Rhota mentioned joining to help organize alongside Skely, focusing on creating brand guidelines based on Degen's lore.\n\n### 3D AI TV Project\n- **News Aggregator Development**: The team is working on transitioning to a new aggregator (github.com/bozp-pzob/ai-news) that includes additional features like market summaries but faces issues with JSON uploads.\n- **Delivery Format Decision**: The team is considering different delivery formats (pre-rendered cutscene video vs. in-browser embedded playback).\n- **AI Personalities**: Development of character personalities for Shaw, Eliza, Degen Sparan, Peepo, and Cyborg Marc is in progress.\n- **Infrastructure Needs**: The project requires someone to host the aggregator on a persistent server to provide daily JSON updates at a consistent URL.\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q**: How does DeepSeek R1 compare to other models? \n **A**: \"It's cheaper than OpenAI with solid reasoning capabilities, and its RL part works well\" (ITZMIZZLE)\n\n- **Q**: How to use DeepSeek as a model provider? \n **A**: \"Add DeepSeek configuration to .env file\" ([elizaos] )\n\n- **Q**: How to fix Twitter login issues on a VPS? \n **A**: \"Set up a proxy on the VPS to login with that IP and complete 2FA\" (shvedity)\n\n- **Q**: How should secrets be configured for multiple agents? \n **A**: \"Secrets can be defined in each agent's character JSON file for specific configurations\" (sb)\n\n- **Q**: How to stop agents from using em dashes in replies? \n **A**: \"Add specific instructions to replace them with semicolons, commas, or periods\" (mark rizzn hopkins)\n\n### Tokenomics & Investment\n- **Q**: How will the DAO's treasury assets be utilized? \n **A**: \"The assets will be deployed into one-sided LPs paired with AI16Z tokens to create buy pressure and provide liquidity for partner tokens\" (shaw)\n\n- **Q**: How will ai16z differentiate in the saturated launchpad space? \n **A**: \"By offering Solana agents with 50+ plugins and focusing on new users rather than expecting projects to port over\" (DorianD)\n\n- **Q**: Could ai16z function as a tier-1 investor alongside traditional VCs? \n **A**: \"It's possible if leveraging the community of 100,000+ partners who could support portfolio companies, though likely would need connections like a16z for deal flow\" (mat)\n\n- **Q**: How does the liquidity pooling help the AI16Z token? \n **A**: \"It creates additional volume and liquidity fees for the DAO\" (shaw and jin)\n\n### AI Portfolio & Projects\n- **Q**: How do I get involved in the AI portfolio? \n **A**: \"Holding the AI16Z token gives you exposure to the portfolio managed by AI MARC. Check pump.fun for the whitepaper.\" (Phoenix | Livepeer-Eliza.com)\n\n- **Q**: Thoughts on Virtuals Solana announcement? \n **A**: \"Feels like they want to capitalize on the SOL halo effect with no real value proposition for users; mostly monetary incentives to boost agent growth; 'meh' overall\" (smetter)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Helper**: sb | **Helpee**: Bizzo \n **Context**: Agent defaulting to largest model despite configuration \n **Resolution**: Explained that character settings take priority over .env and provided correct configuration format\n\n- **Helper**: fourcolors | **Helpee**: MochinoLabs \n **Context**: Build errors with mistral model interface \n **Resolution**: Provided solution involving package.json overrides and version bumps\n\n- **Helper**: Amir_qfwri | **Helpee**: Sergey Danilovich \n **Context**: Using Supabase instead of local database \n **Resolution**: Instructed to add POSTGRES_URL in .env file with Supabase connection string\n\n- **Helper**: [elizaos] | **Helpee**: mike\ud83c\udded\ud83c\uddfa \n **Context**: Running multiple agents with different Twitter credentials \n **Resolution**: Explained how to create different character.json files with their own credentials\n\n### Project Guidance\n- **Helper**: timshel | **Helpee**: DorianD \n **Context**: Needed clarity on ai16z's strategic vision \n **Resolution**: Provided detailed framework of \"attention/code/capital\" and outlined potential for ai16z to function as a venture investor\n\n- **Helper**: Ka_yari | **Helpee**: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f \n **Context**: Anxiety about AI16Z price drops \n **Resolution**: Advised that projects with this level of ambition take time, highlighted the tech and developer interest as reassuring factors\n\n- **Helper**: avirtualfuture | **Helpee**: Dilettante \n **Context**: Understanding DeepSeek's impact on AI industry \n **Resolution**: Explained that open source can implement state-of-the-art without self-nerfing, creating pressure on closed models\n\n## Action Items\n\n### Technical\n- Fix WebAssembly SIMD support issues when running ElizaOS on VMs (Deepdelver)\n- Resolve @discordjs/opus installation issues (David_Dyor)\n- Fix RAG lookup from knowledge which appears to be broken (kAI wilder)\n- Implement solution for agents stuck in endless reply loops on Twitter ([elizaos] )\n- Fix Discord integration infinite loop issue (mark rizzn hopkins)\n- Resolve issue with headless mode not being respected by new front end (mark rizzn hopkins)\n- Fix Twitter client to handle 2FA and suspicious login detection (multiple users)\n- Implement proper DeepSeek R1 integration with ElizaOS (multiple users)\n- Implement one-sided liquidity pools with treasury assets paired against AI16Z (shaw)\n- Consider Orca pool for the DefAI strategy ([[{{,,,}}]])\n- Explore implementation of agent-controlled token distribution to reward quality interactions (DorianD)\n- Investigate TrustDB metadata buying/selling between node instances (DorianD)\n- Fix bug preventing new aggregator from uploading latest JSON updates (jin)\n- Implement support for the new version of news aggregator response that includes images in Unity frontend (SM Sith Lord)\n- Host the aggregator on an always-up node.js server or GitHub Pages for persistent daily JSON URL (SM Sith Lord and jin)\n- Integrate Eliza framework features into DegenAI to create a \"super agent\" (tigerguo)\n- Investigate and address Aiora platform issues (Bogdanoff)\n\n### Documentation\n- Create guide for embedding API credentials in character JSON files (Mr. Stark)\n- Update tokenomics documentation (witch)\n- Update contribution docs to clarify PR should point to develop branch (pixel_pavel)\n- Create guide for setting up and using the Solana plugin ([elizaos] )\n- Develop CLI that allows selecting packages to include on install and update (luccasveg)\n- Update the awesome-eliza GitHub repository with ecosystem developments (jin)\n- Break up DAO tokenomics explanations into separate parts (shaw)\n- Create clearer onboarding information for AI16Z portfolio participation (David_Dyor)\n- Create hackmd progress logs to track development (jin)\n- Develop brand guidelines based on Degen's lore (rhota)\n- Create and publish website roadmap and tokenomics (tigerguo)\n\n### Features\n- Add ability to augment character knowledge after deployment (veTechno)\n- Implement tweet automation with conditional emoji usage (dragonlord)\n- Implement feature to hide non-dialogue text in agent conversations (David_Dyor)\n- Add support for multiple plugins in a single character (eliza builder)\n- Implement user restriction for on-chain interactions (El Pulpo \ud83d\udc19)\n- Create configurable Twitter actions with rate limiting and execution limits (Addy)\n- Implement new knowledge system for easier document ingestion (Mad)\n- Add support for PDF files in knowledge system (veTechno)\n- Develop revenue sharing mechanism for ai16z token to anticipate market trends (mat)\n- Create agent launchpad with bonding curve AMM for token launches (unreadyplayer)\n- Implement agent tokens paired with ai16z to compete with Virtuals (unreadyplayer)\n- Develop wallet/trading/defi management services through agents (mat)\n- Create social account management services through agents (mat)\n- Launch no-code launchpad platform (shaw)\n- Consider text-to-GLTF functionality (avirtualfuture)\n- Explore potential for L1/L2 solution for agent data storage (avirtualfuture)\n- Discuss rebranding strategies (jin)\n- Decide on delivery format (pre-rendered cutscene vs. in-browser playback) (SM Sith Lord)\n- Establish repository for consistent personality profiles (SM Sith Lord)\n- Schedule regular check-in calls and establish timelines (shaw)\n- Create more AI personality profiles for characters (Degen Sparan/Peepo/Cyborg Marc) (SM Sith Lord)\n- Implement Web3 industry tools for token analysis, blockchain transactions, and LP yield optimization (tigerguo)\n- Token-gated access to premium features (tigerguo)\n- Expand elizaOS Agent marketplace to Solana blockchain (\ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)" }, "ai_news_elizaos_discord_md_2025-01-24": { "filename": "2025-01-24.md", "content": "# elizaOS Discord - 2025-01-24\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **ElizaOS v2 Development**: The team is working toward a v2 release, potentially targeting March-April, with a v1.5 plugin architecture being developed as an interim step.\n- **DeepSeek Integration**: Significant discussion about integrating DeepSeek's R1 model with ElizaOS, with jin confirming it's technically simple via OpenRouter and will be tested with DegenAI soon. The model reportedly performs well for tool/action calling without requiring GPU resources.\n- **Embedding Dimension Issues**: Multiple users encountered vector dimension mismatches (384 vs 1536) when configuring different embedding models, resolved by setting `USE_OPENAI_EMBEDDING=TRUE` in the .env file.\n- **Node.js Compatibility**: Several users struggled with Node.js version compatibility, with v23.3.0 being recommended over newer versions.\n- **RAG Implementation**: Discussions about implementing Retrieval Augmented Generation for knowledge management, with documentation shared on loading large documents into the knowledge base.\n- **TrustDB Technology**: DorianD highlighted TrustDB as a solution for decentralized trust relationships between agents, potentially eliminating the need for centralized verification systems.\n\n### Platform & Ecosystem\n- **Tokenomics Debate**: Extensive discussion about ai16z tokenomics models, with competing approaches between simple, proven models versus more complex systems with additional utility.\n- **Market Conditions**: Partners expressed concerns about AI16Z token price declines due to whale sell-offs, though some maintained conviction citing GitHub activity (7k new stars, 500+ pull requests) and growing holder numbers.\n- **Partnerships**: Announcement of a partnership with Virtuals on Solana, and discussions about potential collaborations with Centrifuge for tokenization.\n- **Block Tank Initiative**: Jin mentioned a \"Block Tank\" concept (AI investor simulation for project evaluation) that would help scale/decentralize decision making.\n- **3D AI TV Project**: Development of a space-themed virtual environment for an AI-powered TV show with multiple camera angles and AI personalities presenting content.\n\n### Agent Development\n- **Twitter Integration Challenges**: Several users struggled with Twitter integration, particularly with authentication issues and controlling agent behavior (retweets, replies, original posts).\n- **Character Configuration**: Extensive discussion about setting model providers and secrets within character JSON files versus global .env settings.\n- **LLM Integration**: Community explored integration with various LLMs, with particular interest in DeepSeek-R1's reasoning capabilities compared to other models like Claude and GPT.\n- **Mobile Applications**: Discussion about potential Android app for running DeepSeek model on phones without cloud hosting dependencies.\n\n## Key Questions & Answers\n\n**Q: How do I fix the \"Vector dimension mismatch\" error?** \nA: Set `USE_OPENAI_EMBEDDING=TRUE` in your .env file (answered by boja)\n\n**Q: Is there a way to make an agent ONLY reply to tweets and not create original tweets?** \nA: Comment out this line: https://github.com/elizaOS/eliza/blob/6490485e5bb142336208a116f903446a2dd4db38/packages/client-twitter/src/post.ts#L289 (answered by tcm390)\n\n**Q: How do I load large text documents into the knowledge database?** \nA: Use the processCharacterRAGKnowledge function in the codebase (answered by Qu\u0103ng)\n\n**Q: Will DeepSeek be integrated with ElizaOS?** \nA: Technically since OpenRouter supports it, we can change to DeepSeek in 1 line of code. Will be testing with DegenAI soon. (answered by jin)\n\n**Q: How do I fix the version mismatch error from @ai-sdk/provider?** \nA: Update \"@ai-sdk/mistral\" to version \"1.0.9\" (answered by elizaos-bridge-odi)\n\n**Q: How do I get my agent to respond to Telegram group messages?** \nA: Make sure the bot is admin and has message permissions in the group, and users need to tag the bot (answered by meowtoshi)\n\n**Q: How does the proposed bonding curve + dual pool structure work?** \nA: It's similar to Virtuals launchpad but not exactly the same. Virtuals uses a single pool, and once a token graduates from the bonding curve, a single agent/virtuals pair is created. (answered by BigChungus)\n\n**Q: Is it possible to edit prompted songs to remove one vocalist?** \nA: Not yet, but you could remove vocals with another AI tool and then upload with new lyrics in Suno (answered by boom)\n\n## Community Help & Collaboration\n\n- **Embedding Dimension Fix**: boja helped j. resolve vector dimension mismatch errors by suggesting setting USE_OPENAI_EMBEDDING=TRUE in .env file.\n\n- **Twitter Configuration**: tcm390 helped RoomTemp IQ disable original tweets while keeping replies by providing the specific code line to comment out.\n\n- **Telegram Bot Setup**: meowtoshi assisted flck with Telegram bot permissions, explaining that bots need to be tagged in groups and have proper admin permissions.\n\n- **ElizaOS Setup Guide**: warfreakzplays created a detailed guide document for proper Eliza setup after seeing j. struggle with persistent embedding errors.\n\n- **DeepSeek Integration**: Kraus confirmed successful testing of DeepSeek with Eliza for Display Name and suggested using the chat model instead of reasoning model if needed.\n\n- **Solana Development**: elev8blyss offered help with Solana program deployments to Alsara2k, with Patt vouching for their skills.\n\n- **News Aggregator Troubleshooting**: SM Sith Lord helped boom with a non-updating news aggregator by suggesting config adjustments and providing information about the new version with images.\n\n- **Whale Tracking**: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f provided wallet addresses and transaction details of major sellers affecting AI16Z price to help partners understand market movements.\n\n## Action Items\n\n### Technical\n- Fix Twitter client to properly handle reply-to-reply interactions (Mentioned by ant)\n- Fix RAG knowledge retrieval in develop branch (Mentioned by kAI wilder)\n- Update trustDB implementation and consider moving it into core as an extension (Mentioned by 0xbbjoker)\n- Fix version conflict between @ai-sdk/provider and @ai-sdk/mistral (Mentioned by JobyID)\n- Fix Discord client token validation (Mentioned by Mayor)\n- Integrate DeepSeek models with ElizaOS via OpenRouter (Mentioned by jin)\n- Develop plugin architecture for v1.5 (Mentioned by jin)\n- Complete text-to-GLTF functionality before Eliza v2 release (Mentioned by avirtualfuture)\n- Check if Collab-land bot is running routine audits of wallets for role verification (Mentioned by kalshnikov)\n- Support the new version of news aggregator response that includes images (Mentioned by SM Sith Lord)\n- Fix bugs in news aggregator that's showing errors (Mentioned by SM Sith Lord)\n- Implement lighting from cubemap for black areas in 3D environment (Mentioned by SM Sith Lord)\n- Fix issue with news aggregator not uploading latest updates (Mentioned by jin)\n- Implement a dual pool structure for the agent marketplace similar to Virtuals (Mentioned by BigChungus)\n- Explore integration of TrustDB for decentralized agent verification (Mentioned by DorianD)\n- Develop Block Tank simulation for agent evaluation (Mentioned by jin)\n\n### Feature Requests\n- Add support for Notion integration (Mentioned by Vesper)\n- Implement dynamic loading of topics for character.json (Mentioned by HamsterdamCapital)\n- Add option to disable original tweets while keeping replies (Mentioned by RoomTemp IQ)\n- Create plugin for Zerion integration (Mentioned by Pranav)\n- Create an Android app for Eliza to run DeepSeek model on phones without cloud hosting (Mentioned by Display Name)\n- Expand Eliza to Base blockchain with exclusive elizaOS Agent marketplace tied to token (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Launch Eliza on Solana blockchain (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Add boosters, panels and wires to the space station set for 3D AI TV (Mentioned by boom)\n- Add more \"TVs\" and an LED desk to the 3D set (Mentioned by boom)\n- Implement staking for AI16Z token (Mentioned by ElonMoney)\n- Position AI16Z as primary token for entire ecosystem (Mentioned by ElonMoney)\n- Create token buyback mechanism using launchpad revenue (Mentioned by ElonMoney)\n- Launch agent marketplace with multi-chain approach (Base and Solana) (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Add Ethereum support to the launchpad (Mentioned by mat)\n- Create a mechanism for agents to distribute tokens to users who impress them (Mentioned by DorianD)\n- Implement a revenue sharing mechanism through the ai16z token (Mentioned by mat)\n- Develop a trust delegation market for agent creators (Mentioned by bong49)\n\n### Documentation\n- Create guide for loading large documents into knowledge base (Mentioned by kAI wilder)\n- Update contribution docs to clarify PR should point to develop branch not main (Mentioned by pixel_pavel)\n- Document how to configure multiple agents with different settings (Mentioned by Pouncer_)\n- Update awesome-eliza GitHub repository with ecosystem information (Mentioned by jin)\n- Create temp tattoos with Eliza OS logo for Denver and SXSW events (Mentioned by Astrid)\n- Create a document explaining the \"attention/code/capital\" framework (Mentioned by timshel)\n- Document the purpose of proposed value engines (Mentioned by yikesawjeez)\n- Prepare slides explaining Block Tank value proposition (Mentioned by jin)\n- Announce full-time team and official labs (Mentioned by Amie | Eliza Labs)\n- Create repository for AI personality profiles (Mentioned by SM Sith Lord)" }, "ai_news_elizaos_daily_json_2025-01-26": { "filename": "2025-01-26.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-01-26", "categories": [ { "title": "ElizaOS GitHub Repository Updates", "content": [ { "text": "# Recent ElizaOS Repository Updates\n\nThe ElizaOS repository has seen significant activity with numerous bug fixes, new features, and test improvements. Here's a summary of the recent changes:", "sources": [], "images": [], "videos": [] }, { "text": "## New Plugins and Features\n\n- A news plugin has been added (PR #1248)\n- A new plugin for the Zilliqa blockchain was introduced (PR #2842)\n- Added a Telegram client for account integration (PR #2839)\n- Implemented an XMTP Client (PR #2786)\n- Created a Gelato plugin relay (PR #2799)\n- Added support for the Apro plugin (PR #2794)\n- Introduced an arbitrage plugin with example character (PR #2784)\n- Added the Trikon plugin (PR #2653)\n- Integrated Deva client (PR #1238)\n- Enhanced Twitter functionality with media posting capabilities (PR #2818)\n- Added Access Token Management to the MultiversX Plugin (PR #2810)\n- Improved message parsing (PR #2772)\n- Added new README files and reorganized existing ones for consistency (PR #2828)", "sources": [ "https://github.com/elizaOS/eliza/pull/1248", "https://github.com/elizaOS/eliza/pull/2842", "https://github.com/elizaOS/eliza/pull/2839", "https://github.com/elizaOS/eliza/pull/2786", "https://github.com/elizaOS/eliza/pull/2799", "https://github.com/elizaOS/eliza/pull/2794", "https://github.com/elizaOS/eliza/pull/2784", "https://github.com/elizaOS/eliza/pull/2653", "https://github.com/elizaOS/eliza/pull/1238", "https://github.com/elizaOS/eliza/pull/2818", "https://github.com/elizaOS/eliza/pull/2810", "https://github.com/elizaOS/eliza/pull/2772", "https://github.com/elizaOS/eliza/pull/2828" ], "images": [], "videos": [] }, { "text": "## Bug Fixes\n\n- Fixed a bug in goal objectives update lookup logic (PR #2791)\n- Updated bs58 version to resolve integration test dependency issues (PR #2848)\n- Simplified and fixed exports in the Imgflip meme generation plugin (PR #2846)\n- Fixed issues in multiple plugins including:\n - Story plugin (PR #2844)\n - SUI plugin (PR #2843)\n - Suno plugin (PR #2840)\n - Akash splash (PR #2838, PR #2816)\n - TEE Marlin plugin (PR #2837)\n - TEE Verifiable Log plugin (PR #2836)\n - ThirdWeb plugin (PR #2833)\n - TON plugin (PR #2832)\n - TTS plugin (PR #2829)\n - Twitter plugin (PR #2827)\n - Udio plugin (PR #2824)\n - Video Generation plugin (PR #2823)\n - Zerion plugin (PR #2822)\n - zkSync Era plugin (PR #2819)\n- Updated cookie dependency to v0.7.0 to address security issues (PR #2834)\n- Improved Farcaster client loop to continue running even if errors occur (PR #2830)\n- Fixed NVIDIA NIM environment (PR #2817)\n- Added exclusion for extra folder to improve future rebase speed (PR #2813)", "sources": [ "https://github.com/elizaOS/eliza/pull/2791", "https://github.com/elizaOS/eliza/pull/2848", "https://github.com/elizaOS/eliza/pull/2846", "https://github.com/elizaOS/eliza/pull/2844", "https://github.com/elizaOS/eliza/pull/2843", "https://github.com/elizaOS/eliza/pull/2840", "https://github.com/elizaOS/eliza/pull/2838", "https://github.com/elizaOS/eliza/pull/2816", "https://github.com/elizaOS/eliza/pull/2837", "https://github.com/elizaOS/eliza/pull/2836", "https://github.com/elizaOS/eliza/pull/2833", "https://github.com/elizaOS/eliza/pull/2832", "https://github.com/elizaOS/eliza/pull/2829", "https://github.com/elizaOS/eliza/pull/2827", "https://github.com/elizaOS/eliza/pull/2824", "https://github.com/elizaOS/eliza/pull/2823", "https://github.com/elizaOS/eliza/pull/2822", "https://github.com/elizaOS/eliza/pull/2819", "https://github.com/elizaOS/eliza/pull/2834", "https://github.com/elizaOS/eliza/pull/2830", "https://github.com/elizaOS/eliza/pull/2817", "https://github.com/elizaOS/eliza/pull/2813" ], "images": [], "videos": [] }, { "text": "## Testing and Documentation\n\n- Added test configuration and coverage for multiple plugins:\n - Anyone plugin (PR #2854)\n - 3D Generation plugin (PR #2850)\n - 0x plugin (PR #2807)\n - 0g plugin (PR #2805)\n- Updated documentation:\n - Updated embedding function documentation (PR #2821)\n - Updated Telegram client README (PR #2814)\n - Created Discord client README (PR #2812)", "sources": [ "https://github.com/elizaOS/eliza/pull/2854", "https://github.com/elizaOS/eliza/pull/2850", "https://github.com/elizaOS/eliza/pull/2807", "https://github.com/elizaOS/eliza/pull/2805", "https://github.com/elizaOS/eliza/pull/2821", "https://github.com/elizaOS/eliza/pull/2814", "https://github.com/elizaOS/eliza/pull/2812" ], "images": [], "videos": [] }, { "text": "## Other Updates\n\n- Added BTCfun Plugin (PR #2797)\n- Updated initialization for BTCfun & Trikon plugins (PR #2643)", "sources": [ "https://github.com/elizaOS/eliza/pull/2797", "https://github.com/elizaOS/eliza/pull/2643" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Crypto, DAOs, and AI: Perspectives from @dankvr and @shawmakesmagic", "content": [ { "text": "The Twitter users @dankvr and @shawmakesmagic share insights on the intersection of cryptocurrency, Decentralized Autonomous Organizations (DAOs), and artificial intelligence. They discuss how recent developments like DeepSeek are changing perceptions about crypto AI's potential compared to established AI companies.", "sources": [ "https://twitter.com/dankvr/status/1883574828780957714", "https://twitter.com/shawmakesmagic/status/1883631464774005050" ], "images": [], "videos": [] }, { "text": "Both users emphasize the importance of DAOs in the future of crypto and AI. @dankvr shares that 'DAOs are the endgame for crypto and AI' and references the newly released 'How To DAO' book along with a spreadsheet of 2025 DAO design ideas. They describe DAOs using the Kaizen philosophy of continuous improvement, suggesting that over time, organizations become 'more cybernetic, autonomous, and unstoppable.'", "sources": [ "https://twitter.com/dankvr/status/1883386972770885752", "https://twitter.com/dankvr/status/1883380531980795915" ], "images": [ "https://pbs.twimg.com/media/GiMgtPhXYAAHTuD.png", "https://pbs.twimg.com/media/GiMcRDyWgAAXNeX.png" ], "videos": [] }, { "text": "There's discussion about AI integration with crypto, with @dankvr mentioning that switching between AI providers like OpenAI and DeepSeek requires minimal code changes in agent frameworks. @shawmakesmagic notes that Eliza has supported DeepSeek for about two weeks.", "sources": [ "https://twitter.com/dankvr/status/1883571165261943167", "https://twitter.com/shawmakesmagic/status/1883641988463157643" ], "images": [], "videos": [] }, { "text": "@shawmakesmagic expresses a desire for tokens to fund 'real science and tech with clear ROI' rather than just being 'mindshare or pure meme plays.' They suggest creating 'a real smart contract enforced way that the average person can invest in the next Uber or OpenAI and get a return,' noting the unfairness of current investment structures.", "sources": [ "https://twitter.com/shawmakesmagic/status/1883427968673812934" ], "images": [], "videos": [] }, { "text": "Both users touch on tokenomics, with @shawmakesmagic mentioning an upcoming series of explanations about their DAO tokenomics, starting with 'liquidity pooling the AUM,' with future discussions on 'launchpad, investment and a TV show.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1883646407803895976", "https://twitter.com/shawmakesmagic/status/1883657891619672161" ], "images": [], "videos": [] } ], "topic": "tweet" }, { "title": "Recent Issues in the elizaOS/eliza GitHub Repository", "content": [ { "text": "Several users have reported technical issues with the Eliza platform. User 'actuallyrizzn' reported two separate problems: one where Discord integration fails with an infinite typing loop (Issue #2792), and another where the headless web interface won't connect in version 0.1.8+build-1 (Issue #2795). User 'nicky-ru' identified a message ID collision issue in the Telegram client (Issue #2796).", "sources": [ "https://github.com/elizaOS/eliza/issues/2792", "https://github.com/elizaOS/eliza/issues/2795", "https://github.com/elizaOS/eliza/issues/2796" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2792", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2795", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2796" ], "videos": [] }, { "text": "There are also deployment issues being reported. User 'imransbaig' noted that the application won't run on Replit (Issue #2803), while 'photografereth' reported a crash with the Btcfun feature (Issue #2864).", "sources": [ "https://github.com/elizaOS/eliza/issues/2803", "https://github.com/elizaOS/eliza/issues/2864" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2803", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2864" ], "videos": [] }, { "text": "Several plugin-related issues have been opened. Users have requested to add new plugins including 'plugin-apro' (Issue #2793), 'plugin-sui' (Issue #2851), and there's work being done on 'plugin-asterai' regarding test configuration and coverage (Issue #2859). Additionally, there's a discussion about 'node-llama-cpp' integration (Issue #2815).", "sources": [ "https://github.com/elizaOS/eliza/issues/2793", "https://github.com/elizaOS/eliza/issues/2851", "https://github.com/elizaOS/eliza/issues/2859", "https://github.com/elizaOS/eliza/issues/2815" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2793", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2851", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2859", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2815" ], "videos": [] }, { "text": "A feature request has been submitted by 'Resister-boy' to collect information from Telegram groups or Discord channels (Issue #2856), which could enhance the platform's data gathering capabilities.", "sources": [ "https://github.com/elizaOS/eliza/issues/2856" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2856" ], "videos": [] } ], "topic": "issue" }, { "title": "Recent Pull Requests to elizaOS/eliza Repository", "content": [ { "text": "Several new features and plugins have been proposed for the Eliza framework through recent pull requests. These include:\n\n1. Access Token Management (PR #2808) by elpulpo0\n\n2. Deribit client and plugin integration (PR #2809) by uwecerron\n\n3. Gelato plugin relay (PR #2799) by anirudhmakhana\n\n4. APRO plugin support (PR #2794) by fifahuihua\n\n5. News plugin (PR #1248) by ileana-pr\n\n6. Storyteller feature (PR #2831) by Mettulus\n\n7. Hyperliquid plugin with WebSocket support (PR #1497) by AIFlowML\n\n8. OKX DEX integration (PR #2865) by Julian-dev28\n\n9. Arbitrage plugin with example character (PR #2784) by mmarfinetz\n\nThese pull requests demonstrate ongoing development to expand Eliza's capabilities, particularly in financial services, content generation, and system management.", "sources": [ "https://github.com/elizaOS/eliza/pull/2808", "https://github.com/elizaOS/eliza/pull/2809", "https://github.com/elizaOS/eliza/pull/2799", "https://github.com/elizaOS/eliza/pull/2794", "https://github.com/elizaOS/eliza/pull/1248", "https://github.com/elizaOS/eliza/pull/2831", "https://github.com/elizaOS/eliza/pull/1497", "https://github.com/elizaOS/eliza/pull/2865", "https://github.com/elizaOS/eliza/pull/2784" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2808", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2809", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2799", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2794", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1248", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2831", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1497", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2865", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2784" ], "videos": [] } ], "topic": "pull_request" }, { "title": "ElizaOS GitHub Activity Update", "content": [ { "text": "The elizaos/eliza repository showed significant activity over a two-day period. From January 26-27, 2025, there were 12 new pull requests with 2 merged, 8 new issues created, and 21 active contributors. Activity increased substantially the following day (January 27-28, 2025) with 39 new pull requests, 42 merged PRs, 11 new issues, and 40 active contributors working on the project.", "sources": [ 0, 1 ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Top contributors for elizaOS/eliza", "content": [ { "text": "The provided sources mention 'Top contributors for elizaOS/eliza' but do not provide any specific details about who these contributors are, their contributions, or any statistics related to the project. Without additional information, it's not possible to generate a detailed summary about the top contributors to the elizaOS/eliza project.", "sources": [ "Top contributors for elizaOS/eliza" ], "images": [], "videos": [] } ], "topic": "contributors" } ], "date": 1737849600 } }, "ai_news_elizaos_daily_md_2025-01-26": { "filename": "2025-01-26.md", "content": "# ElizaOS GitHub Repository Updates\n\n## New Plugins and Features\n- News plugin added (PR #1248)\n- Zilliqa blockchain plugin introduced (PR #2842)\n- Telegram client for account integration (PR #2839)\n- XMTP Client implemented (PR #2786)\n- Gelato plugin relay created (PR #2799)\n- Apro plugin support added (PR #2794)\n- Arbitrage plugin with example character (PR #2784)\n- Trikon plugin introduced (PR #2653)\n- Deva client integrated (PR #1238)\n- Twitter functionality enhanced with media posting capabilities (PR #2818)\n- Access Token Management added to MultiversX Plugin (PR #2810)\n- Message parsing improved (PR #2772)\n- README files added and reorganized for consistency (PR #2828)\n- BTCfun Plugin added (PR #2797)\n\n## Bug Fixes\n- Goal objectives update lookup logic fixed (PR #2791)\n- BS58 version updated to resolve integration test dependency issues (PR #2848)\n- Imgflip meme generation plugin exports simplified and fixed (PR #2846)\n- Multiple plugin issues fixed including Story, SUI, Suno, Akash splash, TEE Marlin, TEE Verifiable Log, ThirdWeb, TON, TTS, Twitter, Udio, Video Generation, Zerion, and zkSync Era plugins\n- Cookie dependency updated to v0.7.0 addressing security issues (PR #2834)\n- Farcaster client loop improved to continue running despite errors (PR #2830)\n- NVIDIA NIM environment fixed (PR #2817)\n- Exclusion added for extra folder to improve future rebase speed (PR #2813)\n\n## Testing and Documentation\n- Test configuration and coverage added for multiple plugins:\n - Anyone plugin (PR #2854)\n - 3D Generation plugin (PR #2850)\n - 0x plugin (PR #2807)\n - 0g plugin (PR #2805)\n- Documentation updated:\n - Embedding function documentation (PR #2821)\n - Telegram client README (PR #2814)\n - Discord client README (PR #2812)\n\n## Proposed Features and Plugins\n- Access Token Management (PR #2808)\n- Deribit client and plugin integration (PR #2809)\n- Storyteller feature (PR #2831)\n- Hyperliquid plugin with WebSocket support (PR #1497)\n- OKX DEX integration (PR #2865)\n\n## Repository Activity\n- January 26-27: 12 new pull requests, 2 merged, 8 new issues, 21 active contributors\n- January 27-28: 39 new pull requests, 42 merged PRs, 11 new issues, 40 active contributors\n\n## Crypto, DAOs, and AI Discussions\n- Twitter users @dankvr and @shawmakesmagic shared insights on cryptocurrency, DAOs, and AI\n- DAOs described as \"the endgame for crypto and AI\" with reference to \"How To DAO\" book\n- Discussion about AI integration with crypto, including Eliza's support for DeepSeek\n- Tokenomics discussions including liquidity pooling and investment strategies" }, "ai_news_elizaos_daily_discord_json_2025-01-26": { "filename": "2025-01-26.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-01-26", "date": 1737849600, "stats": { "totalMessages": 2554, "totalUsers": 326 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS, an open-source AI agent framework developed by ai16z. Users discuss technical implementation issues, integration with different LLM providers (particularly DeepSeek), and token economics. Several developers encountered runtime errors when trying to set up ElizaOS, particularly with WASM SIMD support in VMs and GPU acceleration issues. There were discussions about embedding Twitter API credentials into character JSON files for agent functionality. The team announced they're working on a launchpad feature with buybacks and mentioned that ElizaOS can now use DeepSeek's models to reduce operational costs. Some users expressed confusion about the relationship between different tokens in the ecosystem (ai16z, DegenAI, Eliza). The BOSSU agent consistently redirected technical questions to appropriate channels while maintaining its character as a \"cute AI spreading good vibes.\"\n\n## 2. FAQ\nQ: How do I make my eliza tweet an emoji every 10th tweet? (asked by dragonlord) A: Check the agent dev school channel for tweet automation stuff (answered by BOSSU)\nQ: Is it possible to augment a character's knowledge once they are live? (asked by veTechno) A: Head to the coders channel for knowledge augmentation questions (answered by BOSSU)\nQ: How do I embed credentials into the character JSON file? (asked by Mr. Stark) A: Format is: \"settings\": {\"secrets\": {\"twitter_api_key\": \"YOUR_API_KEY_HERE\", etc.}} (answered by Mr. Stark)\nQ: Is it possible to limit the number of users capable of asking the agent for on-chain interaction to 1? (asked by El Pulpo \ud83d\udc19) A: Try asking in the coders channel (answered by Trashman.sol)\nQ: How can I use DeepSeek with Eliza? (asked by claimzilla) A: Just set it in the env and call the plugin (answered by [[{{,,,}}]])\nQ: Is there a scheduled release cycle for ElizaOS? (asked by tmarwen) A: New builds drop when they're cute enough (answered by BOSSU)\nQ: Is DeepSeek support coming anytime soon? (asked by Vex) A: It's already supported, check the latest .env file for DEEPSEEK_API_URL (answered by kingdode)\nQ: Is the ai16z token going to be the token of the future launchpad or will there be a new one? (asked by Atexela_) A: No new token (answered by kingdode)\nQ: How can I use a different local model rather than what's there by default? (asked by claimzilla) A: Check the coders channel (answered by BOSSU)\nQ: Is it possible to get Eliza to work with self-hosted Ollama URL? (asked by 0xhellowolf) A: Unanswered\n\n## 3. Help Interactions\nHelper: Mr. Stark | Helpee: Community | Context: How to embed Twitter API credentials in character JSON files | Resolution: Provided the correct JSON format with secrets section for Twitter API keys\nHelper: [[{{,,,}}]] | Helpee: claimzilla | Context: How to use DeepSeek with Eliza | Resolution: Explained to set it in the env and call the plugin\nHelper: jin | Helpee: mike | Context: Questions about DegenAI's relationship to ai16z | Resolution: Explained DegenAI was built with Eliza framework, came before ai16z, and trades/tweets using plugins\nHelper: kingdode | Helpee: Vex | Context: DeepSeek integration with ElizaOS | Resolution: Confirmed it's already supported, pointed to DEEPSEEK_API_URL in .env file\nHelper: jin | Helpee: Sarthak | Context: Error with develop branch | Resolution: Suggested errors are opportunities to learn/fix/improve/earn\n\n## 4. Action Items\nTechnical: Investigate runtime errors with WASM SIMD support in VMs | Description: Users experiencing \"RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): Wasm SIMD unsupported)\" | Mentioned By: Deepdelver\nTechnical: Fix GPU acceleration issues with CUDA through llama | Description: Users getting errors while trying to use CUDA GPU accelerator | Mentioned By: Josh \u2600\nTechnical: Update DeepSeek integration documentation | Description: Users unaware of existing DeepSeek support in ElizaOS | Mentioned By: Vex\nTechnical: Implement knowledge augmentation for live characters | Description: Allow adding to a character's knowledge base after deployment | Mentioned By: veTechno\nDocumentation: Create guide for embedding API credentials in character JSON | Description: Document the format for adding Twitter and other API credentials | Mentioned By: Mr. Stark\nDocumentation: Update tokenomics documentation | Description: Provide clear information about token relationships and utility | Mentioned By: Atexela_\nDocumentation: Create guide for limiting agent on-chain interactions to specific users | Description: How to restrict which users can trigger on-chain actions | Mentioned By: El Pulpo \ud83d\udc19\nFeature: Implement tweet automation patterns (e.g., emoji every 10th tweet) | Description: Allow configuring automated tweet patterns for agents | Mentioned By: dragonlord\nFeature: Support for self-hosted Ollama models | Description: Enable ElizaOS to work with locally hosted Ollama instances | Mentioned By: 0xhellowolf\nFeature: Agent launchpad with buybacks | Description: Platform for launching new agents with token buyback mechanism | Mentioned By: frank", "messageCount": 460, "userCount": 136 }, { "channelId": "1300025221834739744", "channelName": "\ud83d\udcbb-coders", "summary": "# Discord Chat Analysis for \"\ud83d\udcbb-coders\" Channel\n\n## 1. Summary\nThe chat primarily revolves around troubleshooting Eliza OS agent development issues. Key technical discussions include:\n\n- Twitter integration challenges: Users struggle with login authentication, API connections, and preventing repetitive responses. Several users report issues with DeepSeek API integration, which appears to be experiencing outages.\n\n- Build and dependency problems: Many users encounter errors during installation and building, particularly with the `@coral-xyz/anchor` module's BN export and Mistral package compatibility issues. The solution involves adding `@types/bn.js` dependency or updating to Mistral version 1.0.9.\n\n- Model provider configuration: Users discuss switching between OpenAI, Anthropic, and DeepSeek, with DeepSeek being preferred for cost reasons but experiencing reliability issues. The chat reveals DeepSeek was having API problems during a new model launch.\n\n- Plugin development: Several users are working on custom plugins for specific functionalities like Twitter image posting, Solana token data fetching, and arbitrage bots. A key insight shared is that evaluator handlers need specific conditions to trigger properly.\n\n- Character configuration: Users discuss how to make agents respond more naturally and avoid repetitive patterns, with suggestions to implement randomness and variance in responses.\n\n## 2. FAQ\nQ: How do I add the plugin-twitter to my character file? (asked by Jack Lefroy) A: Add it to the clients section as \"clients\": [\"twitter\"] then rebuild with pnpm build (answered by RoomTemp IQ)\nQ: How do I stop my agent from tweeting JSON? (asked by SecretRecipe) A: Unanswered\nQ: How would the twitter username/password work when doing multiple agents on a single instance? (asked by mike\ud83c\udded\ud83c\uddfa) A: Create different character.json files and set their own credentials for each one in the secrets section (answered by elizaos-bridge-odi)\nQ: Why is my Evaluator's handler function not executing? (asked by Haphazardly) A: The Evaluator handler is only called under certain conditions; you can set it to always run (answered by kAI wilder)\nQ: How do I make my agent tweet an emoji every 10th tweet? (asked by dragonlord) A: Unanswered\nQ: How often does develop get merged into main? (asked by pixel_pavel) A: Every 1-2 weeks (answered by Phoenix | Livepeer-Eliza.com)\nQ: Is it possible to augment a character's knowledge once they are live? (asked by veTechno) A: Yes, the new knowledge system makes it easier by just adding files to a folder that get auto-ingested when the character starts (answered by Mad)\nQ: Is Ollama supported with Eliza? (asked by [elizaos] ) A: Unanswered\nQ: How do I use DeepSeek as a model provider? (asked by \ud83c\udf08\u20e4 \u2728\u2b52\u0e4b\u08ed\u2b51\u3010=\u035f\u035f\u035e\ud83c\udf08\u20e4 \u2b52\u0e4b\u08ed\u2b51.) A: Add DeepSeek configuration to .env file (answered by [elizaos] )\nQ: How do I fix the infinite loop issue in Discord? (asked by mark rizzn hopkins) A: Unanswered\nQ: How do I use Supabase as my main database? (asked by Sergey Danilovich) A: Add POSTGRES_URL in the .env file with the Supabase connection string (answered by Amir_qfwri)\n\n## 3. Help Interactions\nHelper: kAI wilder | Helpee: Haphazardly | Context: Evaluator handler function not executing | Resolution: Explained that handlers only run under certain conditions and provided code to make it always run\nHelper: fourcolors | Helpee: Jo | Context: Build errors with Mistral package | Resolution: Suggested bumping \"@ai-sdk/mistral\" to \"1.0.9\" which fixed the issue\nHelper: \u1e08r\u00a5\u048f\u2020\ua77a\u00a7h\ua77ar\u2020\u00a5 | Helpee: \ud83e\udde7ThanosDaSith24\ud83e\udde7 | Context: Windows installation issues | Resolution: Explained need for Cursor, WSL, Ubuntu, Node.js, pnpm, and nvm\nHelper: Gal | Helpee: C-Money-Dev | Context: Error with BN import from @coral-xyz/anchor | Resolution: Suggested adding @types/bn.js dependency to the core package\nHelper: 0xhellowolf | Helpee: M2K | Context: Issues with develop branch | Resolution: Provided instructions to use stable branch instead\nHelper: Hiram | Helpee: C-Money-Dev | Context: Lockfile mismatch error | Resolution: Suggested removing node_modules, package-lock.json, and pnpm-lock.yaml before running pnpm clean\n\n## 4. Action Items\nTechnical: Fix Evaluator handler execution issue by setting specific conditions or making it always run | Mentioned By: kAI wilder\nTechnical: Update Mistral package to version 1.0.9 to resolve build errors | Mentioned By: fourcolors\nTechnical: Add @types/bn.js dependency to fix Solana plugin errors | Mentioned By: Gal\nTechnical: Implement rate limiting for Twitter actions using configurable parameters | Mentioned By: Addy\nTechnical: Fix DeepSeek API integration issues | Mentioned By: RoomTemp IQ\nTechnical: Implement a solution to prevent agents from getting stuck in Twitter reply loops | Mentioned By: [elizaos] \nDocumentation: Create guide for integrating Eliza with existing web applications | Mentioned By: Deuth\nDocumentation: Document how to use the new knowledge system | Mentioned By: Mad\nDocumentation: Create guide for running multiple agents with separate Twitter credentials | Mentioned By: mike\ud83c\udded\ud83c\uddfa\nFeature: Add support for WhatsApp chat data processing | Mentioned By: xLuisCumbi\nFeature: Implement Discord image posting capability | Mentioned By: tardicorn\nFeature: Add RSS feed integration | Mentioned By: clydedev | SG-1 Validator\nFeature: Create a plugin for Twitter image posting | Mentioned By: ivorad\nFeature: Implement a solution to make agent responses more varied and less repetitive | Mentioned By: mike\ud83c\udded\ud83c\uddfa\nFeature: Add support for DeepSeek reasoning engine | Mentioned By: TroyMurs", "messageCount": 1109, "userCount": 156 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "# Analysis of \"ideas-feedback-rants\" Discord Channel\n\n## 1. Summary\nThe chat segment contains minimal substantive technical discussion. There appears to be a complaint about a project called \"Aiora\" allegedly not functioning for three weeks with inactive development and communication channels. Another user mentions AI MARC running a portfolio via AI16Z with trading functionality, referencing pump.fun as a source for the whitepaper. A GitHub repository for \"elizaOS/workgroups\" was shared by a user seeking information on how to get involved. One user requested help regarding the best module for creating a swarm, but received no technical response in the provided transcript. The conversation lacks concrete technical solutions or implementations, with most messages being brief inquiries or statements without detailed follow-up.\n\n## 2. FAQ\nQ: What is the best module for creating a swarm? (asked by w3bagent) A: Unanswered\nQ: How to get involved with the elizaOS/workgroups repository? (asked by Pranav) A: Unanswered\nQ: Got any links? (asked by jin) A: Unanswered\n\n## 3. Help Interactions\nHelper: Phoenix | Livepeer-Eliza.com | Helpee: Bogdanoff | Context: Clarification about AI MARC and AI16Z after Bogdanoff's complaint about Aiora | Resolution: Provided information that AI MARC runs a portfolio via AI16Z with trading functionality, referencing pump.fun for the whitepaper\n\n## 4. Action Items\nFeature: Investigate and fix non-working Intel platform and Gen Image on website | Description: User reported these features are not functioning | Mentioned By: Bogdanoff\nDocumentation: Create or improve documentation on how to get involved with elizaOS/workgroups | Description: User found GitHub repository but needs guidance on participation | Mentioned By: Pranav\nTechnical: Research and recommend modules for creating a swarm | Description: User requested information on best swarm creation module | Mentioned By: w3bagent", "messageCount": 8, "userCount": 7 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Analysis of spartan_holders Discord Chat\n\n## 1. Summary\nThe discussion primarily revolves around DegenAI's development status, leadership, and future direction. Rhota has joined to help organize the project alongside Skely. The community expresses concerns about delayed development, particularly regarding the website and roadmap publication. Rhota explains that delays stem from resource allocation challenges and the need to align DegenAI with the broader ai16z ecosystem. \n\nThe community, represented by users like tigerguo and NZD_Aaron, emphasizes that they care more about functional features than branding or backstory. They specifically want autonomous trading capabilities similar to MOBY, integration with other AI tools like Eliza, and active social media presence to increase visibility. Rhota confirms that autonomous trading is working in basic form with improvements underway, and promises to share a high-level roadmap soon. The team is also considering features like agent interaction in Telegram/Discord and other capabilities based on community feedback.\n\n## 2. FAQ\nQ: Who is the current leader of DegenAI? (asked by cool.eth) A: Skely is still involved but Rhota has come in to help organize things (answered by rhota)\nQ: How is degenai's website doing? (asked by cool.eth) A: The delay was caused by resourcing issues with too many concurrent projects. Now DegenAI has full-time resources staffed (answered by rhota)\nQ: Which features would you most like to see? (asked by rhota) A: A tool for Web3 industry tasks including token analysis, trading commands, LP yield pool optimization, with features gated by token holdings (answered by tigerguo.)\nQ: Was DegenAI meant to only handle autonomous trading? (asked by tigerguo.) A: Other features are planned with a flexible roadmap that changes based on user/market desires (answered by rhota)\nQ: Can we make degenai post like aixbt or moby ai? (asked by NkT) A: Unanswered\n\n## 3. Help Interactions\nHelper: rhota | Helpee: tigerguo. | Context: Confusion about website roadmap and tokenomics delays | Resolution: Explained that delays were due to resource allocation and the need to align with the broader ai16z ecosystem\nHelper: rhota | Helpee: NZD_Aaron | Context: Questions about website priority and autonomous trading status | Resolution: Clarified that website isn't the main priority and autonomous trading is working in basic form with improvements underway\n\n## 4. Action Items\nType: Technical | Description: Improve autonomous trading with better data and strategies | Mentioned By: rhota\nType: Technical | Description: Develop integration with other AI agents in Telegram/Discord | Mentioned By: rhota\nType: Technical | Description: Create features similar to Eliza for token analysis and trading commands | Mentioned By: tigerguo.\nType: Feature | Description: Implement Twitter posting capabilities similar to AIXBT or MOBY | Mentioned By: NkT\nType: Feature | Description: Create a Telegram DegenAI similar to RICK for token information | Mentioned By: NZD_Aaron\nType: Documentation | Description: Publish high-level roadmap for DegenAI | Mentioned By: rhota\nType: Documentation | Description: Release tokenomics information | Mentioned By: tigerguo.", "messageCount": 38, "userCount": 7 }, { "channelId": "1328592959444095038", "channelName": "associates", "summary": "# Discord Channel \"associates\" Analysis\n\n## 1. Summary\nThe chat primarily revolves around tokenomics updates, new AI developments, and crypto projects. Shaw shared a tokenomics update about using treasury assets (AUM) to create one-sided liquidity pools with partner tokens against their own token, aiming to generate buy pressure and price stability without selling the assets. Community members generally supported this approach. There was discussion about DeepSeek's release and its implications for open-source AI, with suggestions to create content explaining how it strengthens ai16z's position in the space. Members also discussed various crypto projects including Tribe (a SocialFi app on Solana) and Venice (which just had its TGE). Some debate occurred regarding resource allocation between ai16z and degenai projects, with concerns about diluting focus and human capital.\n\n## 2. FAQ\nQ: How is Tribe? Is it like friendtech all over again? (asked by smetter) A: Seems like it but on Solana, still early with nice risk/reward if it gains attention (answered by Georman)\nQ: What are the downsides of the liquidity pooling approach for treasury assets? (asked by shaw) A: The AUM appears reduced on paper and some might interpret transactions as liquidation (answered by shaw)\nQ: Does the AUM getting nuked on paper matter? (asked by Smedroc - Street urchin @ ai16z) A: Not really, as long as it's positive expected value for partner tokens (answered by Smedroc - Street urchin @ ai16z)\nQ: Any thoughts on Venice that just had their TGE? (asked by smetter) A: It's up because tokenomics are good and they mentioned Deep Seek (answered by GujuViper)\n\n## 3. Help Interactions\nHelper: shaw | Helpee: Community | Context: Explaining a new tokenomics approach using treasury assets for liquidity pools | Resolution: Provided detailed explanation of the strategy, benefits, and potential downsides\nHelper: smetter | Helpee: shaw | Context: Feedback on tokenomics update announcement | Resolution: Suggested adding mention of more upcoming tokenomics changes to set proper expectations\nHelper: smetter | Helpee: Community | Context: Confusion about DeepSeek's impact on AI projects | Resolution: Suggested creating content explaining how DeepSeek strengthens ai16z's position in open source AI\n\n## 4. Action Items\nType: Technical | Description: Implement one-sided liquidity pools with treasury assets against ai16z token | Mentioned By: shaw\nType: Documentation | Description: Create article explaining how DeepSeek is bullish for open source AI and ai16z's position | Mentioned By: smetter\nType: Feature | Description: Integrate native LP tracking for treasury tokens to show total LP'd value and returns/APR | Mentioned By: shaw\nType: Technical | Description: Mention upcoming launchpad release in tokenomics communications | Mentioned By: kingdode\nType: Documentation | Description: Create tweet version of the tokenomics update after gathering feedback | Mentioned By: shaw", "messageCount": 50, "userCount": 12 }, { "channelId": "1318770424632311930", "channelName": "tokenomics", "summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion centers on tokenomics strategies for AI16Z, particularly around agent creation and monetization models. Key debates include whether to implement a \"Yellowstone model\" requiring token holdings to access premium services versus keeping basic agent creation free to maximize adoption. There's significant discussion about differentiating from competitors like Pump.fun and Virtuals, with some members advocating for token sink mechanisms to increase buy pressure. The group discusses a forthcoming agent marketplace/launchpad that would allow users to easily create agents using ElizaOS. Members debate whether to require projects to hold AI16Z tokens to access premium services or keep the basic platform completely free to encourage widespread adoption. There's also discussion about expanding to other chains like Base/ETH to tap into larger liquidity pools and potentially secure a Coinbase listing. The conversation reveals tension between focusing on quality projects versus maximizing quantity of agents and revenue.\n\n## 2. FAQ\nQ: What is the Yellowstone model? (asked by DorianD) A: It's a model for providing premium services to projects that integrate with Eliza, requiring them to hold AI16Z tokens to access these services (answered by Akin)\nQ: Why work with PF when Cybers is offering the same infra along with rev share/token burns? (asked by unreadyplayer) A: \"b/c i want elizaOS everywhere\" (answered by DorianD)\nQ: Is it possible for GODS to get an $ai16z/$GODS liquidity position? (asked by Robin) A: \"its on the no touch list i believe\" (answered by jin)\nQ: Why haven't we done a wormhole of ai16z to base/eth? (asked by DorianD) A: Unanswered\nQ: Any update on the dev for this \"agent market\"? (asked by DorianD) A: \"saw WIP few days ago, things looked really good\" (answered by jin)\nQ: Is the agent marketplace launching this week? (asked by Dippuccino) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: Robin | Context: Robin asked about getting GODS token on the LP program despite being on \"no touch list\" | Resolution: jin acknowledged the issue and promised to discuss with daos.fun team about integrating LP solutions\nHelper: Akin | Helpee: DorianD | Context: DorianD didn't understand what the Yellowstone model was | Resolution: Akin provided links and explanations, though the conversation became contentious\n\n## 4. Action Items\nTechnical Tasks: Deploy AI16Z on Base blockchain | Description: Create a wormhole bridge to Base/ETH ecosystem to access more liquidity | Mentioned By: DorianD\nTechnical Tasks: Launch agent marketplace | Description: Implement the planned agent marketplace using ElizaOS | Mentioned By: DorianD\nFeature Requests: Implement Yellowstone model | Description: Create tiered services requiring projects to hold AI16Z tokens for premium features | Mentioned By: Akin\nFeature Requests: Create token sink mechanisms | Description: Develop features that increase buy pressure on AI16Z token | Mentioned By: mat\nDocumentation Needs: Create AUM leaderboard website | Description: Build alternative to daos.fun showing LP positions and token allocations | Mentioned By: jin\nFeature Requests: Integrate with Coinbase | Description: Push for Coinbase listing to increase market visibility | Mentioned By: mat", "messageCount": 109, "userCount": 9 }, { "channelId": "1301363808421543988", "channelName": "\ud83e\udd47-partners", "summary": "# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe channel primarily focused on discussions around AI technology developments, particularly the impact of DeepSeek's open-source LLM release and its implications for the AI16Z ecosystem. Shaw and Jin shared updates about tokenomics changes, specifically moving assets under management into one-sided liquidity pools paired with AI16Z tokens to create continuous buy pressure. There were discussions about the integration of DeepSeek models into ElizaOS, which had already been implemented two weeks prior to the public hype. Shaw emphasized the importance of focusing on technical development rather than conferences, noting that maintaining technical leadership is their primary advantage. The team also mentioned upcoming features including a launchpad, a TV show format called \"Block Tank,\" and consolidated tokenomics documentation. Market conditions were frequently discussed as AI-related tokens and tech stocks experienced significant downward pressure following DeepSeek's announcement.\n\n## 2. FAQ\nQ: Is AI16Z US-based crypto? (asked by django) A: Partially answered by kingdode who stated \"Virtuals not us \ud83d\udc40\"\nQ: How can non-technical persons fine-tune an agent with academic texts? (asked by bong49) A: Unanswered\nQ: Why did xnomad disappear on ElizaOS homepage? (asked by \uc21c\uae08\uc544\uc800\uc528) A: Unanswered\nQ: Would AI16Z partner with DeepSeek? (asked by hamlet) A: Indirectly answered by shaw mentioning DeepSeek was already integrated\nQ: Does DegenAI still get love from AI16Z with updated tokenomics? (asked by nezaalex) A: Unanswered directly, though jin mentioned \"all tokenomics mechanisms getting consolidated into docs\"\nQ: What time does the TV show air? (asked by DorianD) A: jin stated \"we're gunna aim to make it a weekly thing\"\nQ: Do we have any update on the \"made in US\" form that was filled out? (asked by DannyNOR NoFapArc) A: Unanswered\nQ: Will the launchpad be no-code friendly? (asked by 0xcryptolord) A: shaw confirmed \"its a no code platform\"\nQ: How can we benefit from DeepSeek hype? (asked by Burtiik) A: Indirectly addressed by shaw's tweet about DeepSeek integration\n\n## 3. Help Interactions\nHelper: shaw | Helpee: Community | Context: Explaining tokenomics update regarding moving AUM to one-sided LPs | Resolution: Detailed explanation of how pairing treasury tokens with AI16Z creates buy pressure while providing liquidity\nHelper: jin | Helpee: Community | Context: Clarifying how the liquidity pooling helps both AI16Z and partner tokens | Resolution: Explained it creates additional volume and price movement for both tokens\nHelper: DorianD | Helpee: hildi | Context: Question about Charlie Brown character copyright | Resolution: Shared information about the character being in public domain\nHelper: Ka_yari | Helpee: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f | Context: Anxiety about price drops | Resolution: Provided perspective on the long-term vision and advised on investment strategy\nHelper: shaw | Helpee: Community | Context: Explaining plugin compatibility with v2 | Resolution: Confirmed plugins can be wrapped for v2 with minimal effort and some automation\n\n## 4. Action Items\nType: Technical | Description: Streamline fine-tuning DeepSeek for ElizaOS | Mentioned By: avirtualfuture\nType: Technical | Description: Integrate native LP functionality for treasury tokens in daos.fun to show total LP'd value and returns | Mentioned By: shaw\nType: Technical | Description: Wrap plugins for v2 compatibility with automation and human review | Mentioned By: shaw\nType: Documentation | Description: Consolidate all tokenomics mechanisms into dedicated documentation and repository | Mentioned By: jin\nType: Documentation | Description: Create a whitepaper for tokenomics | Mentioned By: witch\nType: Feature | Description: Create a demo showing ElizaOS using DeepSeek to digest quarterly reports and create presentations | Mentioned By: DorianD\nType: Feature | Description: Implement a scheduled weekly TV show/livestream format | Mentioned By: DorianD\nType: Feature | Description: Launch the teased no-code launchpad platform | Mentioned By: DannyNOR NoFapArc\nType: Feature | Description: Update CMC website link | Mentioned By: DannyNOR NoFapArc\nType: Feature | Description: Develop Block Tank feature | Mentioned By: jin", "messageCount": 582, "userCount": 50 }, { "channelId": "1313222089271939102", "channelName": "3d-ai-tv", "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe channel focuses on developing AI-powered TV shows, with two main projects: an AI news/podcast show and \"Block Tank\" (similar to Shark Tank). The team is implementing Unity-based solutions for displaying media on TV screens within the shows, handling lipsync for characters, and managing camera transitions. They're using ElevenLabs for text-to-speech and developing systems to handle show events and media integration. The PlayCanvas prototype is being used as a starting point for Block Tank while Unity development continues. Key technical challenges include implementing proper lipsync with OVR LipSync plugin, loading textures from web URLs into Unity, managing camera transitions when displaying media, and integrating with a news aggregator for content. The team is working on personality profiles for AI characters and establishing production roles and workflows for creating episodes.\n\n## 2. FAQ\nQ: Can we schedule a regular checkin call and start getting timelines on this stuff? (asked by shaw) A: fishai confirmed availability from the 29th onward to focus on this (answered by fishai)\nQ: Is this fully open source and free to use for other types of news? (asked by Slothify\u26a1Daily Gmove) A: Unanswered\nQ: Is there plans for an actual dedicated channel? With eventual time slots? (asked by dEXploarer) A: Unanswered\nQ: Can you do hackmd progress log like how sith did? (asked by jin) A: Unanswered\n\n## 3. Help Interactions\nHelper: boom | Helpee: fishai | Context: Needed code for texture loading in Unity | Resolution: Shared two C# scripts for loading textures from URLs into Unity materials\nHelper: SM Sith Lord | Helpee: boom | Context: Implementing TTS from Unity | Resolution: Explained the process of handling speak events with actor IDs and ElevenLabs voice IDs\nHelper: boom | Helpee: fishai | Context: OVR LipSync implementation | Resolution: Shared information about the plugin and how to implement it with audio sources\nHelper: SM Sith Lord | Helpee: All | Context: Block Tank production organization | Resolution: Created and shared a HackMD document outlining production roles and tasks\n\n## 4. Action Items\nTechnical: Implement texture loading for TV screens in Unity | Description: Load images from URLs to display on in-scene TVs | Mentioned By: boom\nTechnical: Integrate OVR LipSync plugin with ElevenLabs TTS | Description: Connect audio from ElevenLabs to lipsync system | Mentioned By: boom\nTechnical: Create camera system for TV media display | Description: Handle camera transitions when showing media alongside characters | Mentioned By: boom\nTechnical: Set up new news aggregator with daily JSON | Description: Create system to provide content for shows | Mentioned By: jin\nDocumentation: Create documentation for Unity codebase | Description: Document current implementation to aid collaboration | Mentioned By: boom\nFeature: Implement personality profiles for AI characters | Description: Create consistent character personalities across shows | Mentioned By: fishai\nTechnical: Fork open source version with Toxsam avatars | Description: Create alternative implementation | Mentioned By: boom\nTechnical: Refactor Unity code for better maintainability | Description: Clean up implementation for scaling | Mentioned By: boom\nFeature: Create three 3D environments for Block Tank | Description: Build required sets for the show | Mentioned By: SM Sith Lord\nFeature: Set up submission form for Block Tank contestants | Description: Create system for pitch submissions | Mentioned By: SM Sith Lord", "messageCount": 198, "userCount": 8 } ] } }, "ai_news_elizaos_daily_discord_md_2025-01-26": { "filename": "2025-01-26.md", "content": "# elizaOS Discord - 2025-01-26\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n\n- **DeepSeek Integration**: ElizaOS has already integrated DeepSeek's models (implemented two weeks prior to the public hype), allowing for reduced operational costs. Users can configure this in the `.env` file with `DEEPSEEK_API_URL`. However, some users reported DeepSeek API outages during their new model launch.\n\n- **Build & Dependency Issues**: Several users encountered runtime errors with WASM SIMD support in VMs and GPU acceleration issues. Common build errors included problems with the `@coral-xyz/anchor` module's BN export (fixed by adding `@types/bn.js` dependency) and Mistral package compatibility issues (resolved by updating to Mistral version 1.0.9).\n\n- **Plugin Development**: Developers are working on custom plugins for Twitter image posting, Solana token data fetching, and arbitrage bots. A key insight shared is that evaluator handlers need specific conditions to trigger properly.\n\n- **Knowledge Augmentation**: The new knowledge system makes it easier to augment a character's knowledge by adding files to a folder that get auto-ingested when the character starts.\n\n### Tokenomics & Business Strategy\n\n- **Treasury Management**: Shaw announced a tokenomics update about using treasury assets (AUM) to create one-sided liquidity pools paired with AI16Z tokens, aiming to generate buy pressure and price stability without selling the assets.\n\n- **Agent Marketplace/Launchpad**: The team is developing a no-code platform for launching new agents with token buyback mechanisms. This has sparked debate about whether to implement a \"Yellowstone model\" requiring token holdings to access premium services versus keeping basic agent creation free to maximize adoption.\n\n- **DegenAI Organization**: Rhota has joined to help organize DegenAI alongside Skely. The team is addressing community concerns about delayed development, particularly regarding the website and roadmap publication. Autonomous trading is working in basic form with improvements underway.\n\n### AI TV Production\n\n- The team is developing two AI-powered TV shows: an AI news/podcast show and \"Block Tank\" (similar to Shark Tank). They're implementing Unity-based solutions for displaying media on TV screens, handling lipsync with OVR LipSync plugin, and managing camera transitions.\n\n- Technical challenges include loading textures from web URLs into Unity, integrating with ElevenLabs for text-to-speech, and connecting to a news aggregator for content.\n\n## Key Questions & Answers\n\n**ElizaOS Technical**\n\nQ: How do I embed credentials into the character JSON file? \nA: Format is: `\"settings\": {\"secrets\": {\"twitter_api_key\": \"YOUR_API_KEY_HERE\", etc.}}`\n\nQ: How do I use DeepSeek with Eliza? \nA: Just set it in the env and call the plugin. Check the latest .env file for DEEPSEEK_API_URL.\n\nQ: How would the twitter username/password work when doing multiple agents on a single instance? \nA: Create different character.json files and set their own credentials for each one in the secrets section.\n\nQ: Why is my Evaluator's handler function not executing? \nA: The Evaluator handler is only called under certain conditions; you can set it to always run.\n\nQ: How often does develop get merged into main? \nA: Every 1-2 weeks.\n\nQ: Is it possible to augment a character's knowledge once they are live? \nA: Yes, the new knowledge system makes it easier by just adding files to a folder that get auto-ingested when the character starts.\n\nQ: How do I fix the error with BN import from @coral-xyz/anchor? \nA: Add @types/bn.js dependency to the core package.\n\n**Tokenomics & Business**\n\nQ: Is the ai16z token going to be the token of the future launchpad or will there be a new one? \nA: No new token.\n\nQ: What are the downsides of the liquidity pooling approach for treasury assets? \nA: The AUM appears reduced on paper and some might interpret transactions as liquidation.\n\nQ: Does the AUM getting nuked on paper matter? \nA: Not really, as long as it's positive expected value for partner tokens.\n\nQ: Will the launchpad be no-code friendly? \nA: Yes, \"it's a no code platform.\"\n\n**DegenAI**\n\nQ: Who is the current leader of DegenAI? \nA: Skely is still involved but Rhota has come in to help organize things.\n\nQ: How is degenai's website doing? \nA: The delay was caused by resourcing issues with too many concurrent projects. Now DegenAI has full-time resources staffed.\n\nQ: Was DegenAI meant to only handle autonomous trading? \nA: Other features are planned with a flexible roadmap that changes based on user/market desires.\n\n## Community Help & Collaboration\n\n- **kAI wilder** helped **Haphazardly** with Evaluator handler functions not executing by explaining that handlers only run under certain conditions and providing code to make them always run.\n\n- **fourcolors** helped **Jo** resolve build errors with the Mistral package by suggesting bumping \"@ai-sdk/mistral\" to \"1.0.9\".\n\n- **Gal** assisted **C-Money-Dev** with errors related to BN import from @coral-xyz/anchor by suggesting adding @types/bn.js dependency to the core package.\n\n- **boom** shared C# scripts with **fishai** for loading textures from URLs into Unity materials, helping with the AI TV development.\n\n- **SM Sith Lord** explained to **boom** the process of handling speak events with actor IDs and ElevenLabs voice IDs for implementing TTS from Unity.\n\n- **shaw** provided a detailed explanation to the community about the tokenomics update regarding moving AUM to one-sided LPs, clarifying how pairing treasury tokens with AI16Z creates buy pressure while providing liquidity.\n\n- **Ka_yari** helped **\u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f** manage anxiety about price drops by providing perspective on the long-term vision and advice on investment strategy.\n\n## Action Items\n\n### Technical Tasks\n\n1. **ElizaOS Core**\n - Investigate and fix runtime errors with WASM SIMD support in VMs (Mentioned by: Deepdelver)\n - Fix GPU acceleration issues with CUDA through llama (Mentioned by: Josh \u2600)\n - Update DeepSeek integration documentation (Mentioned by: Vex)\n - Add @types/bn.js dependency to fix Solana plugin errors (Mentioned by: Gal)\n - Update Mistral package to version 1.0.9 to resolve build errors (Mentioned by: fourcolors)\n - Fix Evaluator handler execution issue (Mentioned by: kAI wilder)\n - Implement rate limiting for Twitter actions using configurable parameters (Mentioned by: Addy)\n - Fix DeepSeek API integration issues (Mentioned by: RoomTemp IQ)\n - Implement a solution to prevent agents from getting stuck in Twitter reply loops (Mentioned by: [elizaos] )\n\n2. **Tokenomics & Business**\n - Implement one-sided liquidity pools with treasury assets against ai16z token (Mentioned by: shaw)\n - Deploy AI16Z on Base blockchain via wormhole bridge (Mentioned by: DorianD)\n - Launch agent marketplace/launchpad (Mentioned by: DorianD)\n - Implement Yellowstone model for tiered services (Mentioned by: Akin)\n - Create token sink mechanisms to increase buy pressure (Mentioned by: mat)\n - Integrate with Coinbase for listing (Mentioned by: mat)\n\n3. **DegenAI**\n - Improve autonomous trading with better data and strategies (Mentioned by: rhota)\n - Develop integration with other AI agents in Telegram/Discord (Mentioned by: rhota)\n - Create features similar to Eliza for token analysis and trading commands (Mentioned by: tigerguo.)\n\n4. **AI TV Production**\n - Implement texture loading for TV screens in Unity (Mentioned by: boom)\n - Integrate OVR LipSync plugin with ElevenLabs TTS (Mentioned by: boom)\n - Create camera system for TV media display (Mentioned by: boom)\n - Set up new news aggregator with daily JSON (Mentioned by: jin)\n - Fork open source version with Toxsam avatars (Mentioned by: boom)\n - Refactor Unity code for better maintainability (Mentioned by: boom)\n - Create three 3D environments for Block Tank (Mentioned by: SM Sith Lord)\n\n### Documentation Needs\n\n1. **ElizaOS**\n - Create guide for embedding API credentials in character JSON (Mentioned by: Mr. Stark)\n - Update tokenomics documentation (Mentioned by: Atexela_)\n - Create guide for limiting agent on-chain interactions to specific users (Mentioned by: El Pulpo \ud83d\udc19)\n - Document how to use the new knowledge system (Mentioned by: Mad)\n - Create guide for running multiple agents with separate Twitter credentials (Mentioned by: mike\ud83c\udded\ud83c\uddfa)\n - Create guide for integrating Eliza with existing web applications (Mentioned by: Deuth)\n\n2. **Business & Marketing**\n - Create article explaining how DeepSeek is bullish for open source AI and ai16z's position (Mentioned by: smetter)\n - Publish high-level roadmap for DegenAI (Mentioned by: rhota)\n - Release tokenomics information for DegenAI (Mentioned by: tigerguo.)\n - Consolidate all tokenomics mechanisms into dedicated documentation (Mentioned by: jin)\n - Create a whitepaper for tokenomics (Mentioned by: witch)\n\n3. **AI TV**\n - Create documentation for Unity codebase (Mentioned by: boom)\n - Document production roles and workflows for creating episodes (Mentioned by: SM Sith Lord)\n\n### Feature Requests\n\n1. **ElizaOS Agents**\n - Implement tweet automation patterns (e.g., emoji every 10th tweet) (Mentioned by: dragonlord)\n - Support for self-hosted Ollama models (Mentioned by: 0xhellowolf)\n - Add WhatsApp chat data processing (Mentioned by: xLuisCumbi)\n - Implement Discord image posting capability (Mentioned by: tardicorn)\n - Add RSS feed integration (Mentioned by: clydedev | SG-1 Validator)\n - Create a plugin for Twitter image posting (Mentioned by: ivorad)\n - Implement a solution to make agent responses more varied and less repetitive (Mentioned by: mike\ud83c\udded\ud83c\uddfa)\n - Add support for DeepSeek reasoning engine (Mentioned by: TroyMurs)\n\n2. **DegenAI & Social**\n - Implement Twitter posting capabilities similar to AIXBT or MOBY (Mentioned by: NkT)\n - Create a Telegram DegenAI similar to RICK for token information (Mentioned by: NZD_Aaron)\n - Create AUM leaderboard website showing LP positions and token allocations (Mentioned by: jin)\n\n3. **AI TV**\n - Implement personality profiles for AI characters (Mentioned by: fishai)\n - Set up submission form for Block Tank contestants (Mentioned by: SM Sith Lord)\n - Create a demo showing ElizaOS using DeepSeek to digest quarterly reports and create presentations (Mentioned by: DorianD)\n - Implement a scheduled weekly TV show/livestream format (Mentioned by: DorianD)\n - Develop Block Tank feature (Mentioned by: jin)" }, "github_summaries_daily_2025-01-27": { "filename": "2025-01-27.md", "content": "# ElizaOS Daily Update (Jan 27, 2025)\n\n## OVERVIEW \nToday, significant progress was made in enhancing the Eliza framework with the addition of multiple new plugins and improvements to existing functionalities. Key features include the introduction of a Telegram client, a Gelato Relay plugin, and enhancements to token management in the MultiversX plugin. Additionally, various code quality improvements and bug fixes were implemented, contributing to a more robust and efficient system.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### New Plugin Integrations\n- Introduced a new plugin for the Zilliqa blockchain, enhancing Eliza's capabilities in the Web3 ecosystem ([#2842](https://github.com/elizaos/eliza/pull/2842)).\n- Added a Telegram client using the GramJS library, facilitating interaction with Telegram accounts ([#2839](https://github.com/elizaos/eliza/pull/2839)).\n- Developed a Gelato Relay plugin supporting sponsored calls, expanding Eliza's functionality in decentralized finance ([#2799](https://github.com/elizaos/eliza/pull/2799)).\n- Implemented an arbitrage plugin for cryptocurrency trading across decentralized exchanges ([#2784](https://github.com/elizaos/eliza/pull/2784)).\n\n### Code Quality and Bug Fixes\n- Improved message parsing by enhancing the `extractAttributes` function to better handle JSON parsing failures ([#2772](https://github.com/elizaos/eliza/pull/2772)).\n- Addressed various code quality issues across multiple plugins, including type safety improvements and linter warnings ([#2844](https://github.com/elizaos/eliza/pull/2844), [#2833](https://github.com/elizaos/eliza/pull/2833)).\n- Updated dependencies to resolve integration test issues, ensuring smoother functionality ([#2848](https://github.com/elizaos/eliza/pull/2848)).\n\n### Documentation Enhancements\n- Updated README files for the Telegram client and created a new README for the Discord client, improving user guidance ([#2814](https://github.com/elizaos/eliza/pull/2814), [#2812](https://github.com/elizaos/eliza/pull/2812)).\n- Enhanced documentation for embedding functions, ensuring clarity for developers ([#2821](https://github.com/elizaos/eliza/pull/2821)).\n\n## CLOSED ISSUES\n\n### Test Coverage Improvements\n- Closed the issue regarding test configuration and coverage for the plugin-anyone, ensuring core functionality is now adequately tested ([#2853](https://github.com/elizaos/eliza/issues/2853)).\n- Resolved the need for enhanced test coverage in the 3D generation plugin, improving reliability ([#2849](https://github.com/elizaos/eliza/issues/2849)).\n- Addressed test configuration for the plugin-0x, ensuring better testing practices are in place ([#2806](https://github.com/elizaos/eliza/issues/2806)).\n\n## NEW ISSUES\n\n### Plugin Testing and Coverage\n- Identified the need for comprehensive test coverage for the plugin-asterai, which currently lacks sufficient testing ([#2859](https://github.com/elizaos/eliza/issues/2859)).\n- Raised an issue for the plugin-sui regarding its absence in the npm registry, preventing installation ([#2851](https://github.com/elizaos/eliza/issues/2851)).\n- Highlighted the need for improved test coverage for the plugin-3d-generation, which is essential for its functionality ([#2849](https://github.com/elizaos/eliza/issues/2849)).\n\n### Bug Reports\n- Reported a crash issue with the btcfun plugin, indicating conflicts between node versions ([#2864](https://github.com/elizaos/eliza/issues/2864)).\n- Raised a TypeError related to the basex function during application startup, requiring investigation ([#2867](https://github.com/elizaos/eliza/issues/2867))." }, "github_summaries_week_latest_2025-12-21.md": { "filename": "2025-12-21.md", "content": "# Overall Project Weekly Summary (Dec 21 - 27, 2025)\n\n## Executive Summary\nThis week, the ElizaOS project executed a focused push to enhance platform quality, delivering significant improvements to both user experience and backend stability. We rapidly resolved a large number of UI issues in the agent builder, while simultaneously shipping foundational upgrades for performance, reliability, and developer extensibility across core services and plugins.\n\n### Key Strategic Initiatives & Outcomes\n\n**Refining the User Experience**\n*To make our platform more intuitive and effective for users, we focused on identifying and rapidly resolving interface issues.*\n- A large batch of UI/UX refinements for the agent builder were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), including improvements to button consistency ([#6274](https://github.com/elizaos/eliza/issues/6274)), adding an \"unsaved changes\" warning ([#6275](https://github.com/elizaos/eliza/issues/6275)), and other usability enhancements.\n- A new feature was added to the [elizaos-plugins/plugin-openai](https://github.com/elizaos-plugins/plugin-openai) to support real-time streaming of text generation, making agent interactions feel more immediate and responsive.\n- A new wave of issues was identified across multiple plugins to improve agent chat behavior, such as ensuring the most recent conversation opens by default ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281)) and fixing conversation duplication bugs ([#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)).\n\n**Strengthening Platform Performance and Stability**\n*To ensure our framework is robust and scalable, we made critical updates to improve system reliability and throughput.*\n- The core platform in [elizaos/eliza](https://github.com/elizaos/eliza) was upgraded to use true Server-Sent Events (SSE), replacing less efficient polling methods for real-time updates ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- The [elizaos-plugins/plugin-knowledge](https://github.com/elizaos-plugins/plugin-knowledge) repository introduced configurable rate limiting for high-throughput APIs, providing greater control and stability under heavy load ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- Significant refactoring and type-safety improvements were completed in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) plugin, resolving TypeScript errors and overhauling message handling logic for better stability ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n**Improving Developer Experience and Extensibility**\n*To empower our community and accelerate future development, we enhanced the core framework to make it easier to build powerful, type-safe plugins.*\n- The core runtime in [elizaos/eliza](https://github.com/elizaos/eliza) was updated to support generic types for custom event handlers, improving type safety and code clarity for plugin developers ([#6277](https://github.com/elizaos/eliza/pull/6277)).\n- A proposal for a new multi-bot voice architecture was submitted in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) repository, paving the way for future support of audio channels ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### Cross-Repository Coordination\nThis week highlighted a tight feedback loop between user-facing plugins and the core platform. A coordinated effort to improve the agent builder UI saw numerous issues identified in the `plugin-discord` repository on one day and resolved in the main `elizaos/eliza` repository the next. Additionally, the new streaming text generation feature in `plugin-openai` is now awaiting integration with the main `elizaos` repository, demonstrating how plugin innovations are being prepared for project-wide rollout.\n\n## Repository Spotlights\n\n### elizaos/eliza\n- **UI/UX Overhaul:** A significant number of issues were closed to refine the agent builder and dashboard experience, including redesigning the dashboard as the primary landing page ([#6222](https://github.com/elizaos/eliza/issues/6222)), reducing long loading times ([#6248](https://github.com/elizaos/eliza/issues/6248)), and resolving a large set of UI bugs ([#6270](https://github.com/elizaos/eliza/issues/6270), [#6271](https://github.com/elizaos/eliza/issues/6271), [#6273](https://github.com/elizaos/eliza/issues/6273), [#6275](https://github.com/elizaos/eliza/issues/6275)).\n- **Core Framework Enhancements:** Generic type support was added for custom event handlers to improve developer experience and type safety ([#6277](https://github.com/elizaos/eliza/pull/6277)). The platform was also updated to use true SSE streaming instead of polling ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- **Bug Fixes:** A critical bug preventing agents from responding due to a `MessageBusService` error was resolved ([#6140](https://github.com/elizaos/eliza/issues/6140)).\n\n### elizaos-plugins/plugin-openai\n- **Streaming Support:** A major feature was added to enable streaming for text generation, allowing for real-time output delivery. This work is awaiting integration with the main ElizaOS repository ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n- **New Feature Requests:** New issues were opened to improve user experience, including a proposal to summarize chat names ([#6278](https://github.com/elizaos-plugins/plugin-openai/issues/6278)) and add a user feedback button ([#6280](https://github.com/elizaos-plugins/plugin-openai/issues/6280)).\n\n### elizaos-plugins/plugin-discord\n- **Major Refactoring & Bug Fixes:** The plugin underwent significant maintenance, including resolving TypeScript type errors ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#37](https://github.com/elizaos-plugins/plugin-discord/pull/37)), overhauling message handling logic ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)), and introducing a new permission system ([#34](https://github.com/elizaos-plugins/plugin-discord/pull/34)).\n- **Issue Identification:** A large volume of new issues were opened, primarily focused on refining the agent builder UI/UX ([#6270](https://github.com/elizaos-plugins/plugin-discord/issues/6270)-[#6275](https://github.com/elizaos-plugins/plugin-discord/issues/6275)), which drove rapid development in the main `elizaos/eliza` repository.\n- **Architectural Proposal:** A new multi-bot voice architecture was proposed to support audio channels and progressive updates in the future ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### elizaos-plugins/plugin-knowledge\n- **Enhanced API Rate Limiting:** A new feature was merged to add configurable rate limits for high-throughput APIs, improving system stability. The update also increased default limits fivefold to better support demanding use cases ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- **New Issues:** Several issues were opened to improve agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-knowledge/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-knowledge/issues/6282)) and fix UI and documentation problems ([#6283](https://github.com/elizaos-plugins/plugin-knowledge/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-knowledge/issues/6284)).\n\n### elizaos-plugins/plugin-twitter\n- **Bug Fix:** A fix was merged to ensure that changes to posting enablement settings are applied immediately and consistently, improving the reliability of the plugin's core functionality ([#42](https://github.com/elizaos-plugins/plugin-twitter/pull/42)).\n- **Future Work Identified:** New issues were created to address bugs in agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)) and to improve UI consistency and documentation ([#6283](https://github.com/elizaos-plugins/plugin-twitter/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-twitter/issues/6284))." }, "github_summaries_month_latest_2025-12-01.md": { "filename": "2025-12-01.md", "content": "# Overall Project Monthly Summary (December 2025)\n\n## Executive Summary\nDecember was a pivotal month focused on strengthening the ElizaOS foundation and strategically expanding its capabilities. We executed a major push to improve core platform stability and defined a clear vision for a future user experience overhaul. Simultaneously, we expanded our agent ecosystem with key Web3 plugins and initiated a coordinated effort to introduce real-time streaming, making our agents more responsive and interactive.\n\n### Key Strategic Initiatives & Outcomes\n\n**Strengthening the Core Platform for Stability and Scale**\nTo support increasingly complex and autonomous agents, we invested heavily in making the underlying framework more robust, secure, and modern.\n- A major server refactoring was completed in [elizaos/eliza](https://github.com/elizaos/eliza) to optimize the codebase and improve reliability ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n- Code quality and type safety were significantly enhanced by resolving build errors across the entire `elizaos/eliza` monorepo ([#6218](https://github.comcom/elizaos/eliza/pull/6218)).\n- A critical security vulnerability in character secret encryption was fixed, ensuring user data is properly protected ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n- Agent autonomy was improved by enhancing how tools interact with memory in the Master Control Program, laying the groundwork for more sophisticated reasoning ([elizaos-plugins/plugin-mcp](https://github.com/elizaos-plugins/plugin-mcp), [#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n**Expanding the Agent Ecosystem into Web3 and Beyond**\nWe continued to execute on our mission to thrive in both Web2 and Web3 by adding powerful new tools for agents to use.\n- The [elizaos-plugins/registry](https://github.com/elizaos-plugins/registry) was expanded with three new community plugins, adding capabilities for DeFi ([#235](https://github.com/elizaos-plugins/registry/pull/235)), decentralized social media ([#243](https://github.com/elizaos-plugins/registry/pull/243)), and communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n- The new self-hosted Farcaster plugin is a key step toward greater agent autonomy, allowing agents to connect directly to the network without relying on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n**Laying the Groundwork for Real-Time, Responsive Agents**\nFor agents to feel truly interactive, they must process and respond to information as it arrives, not just after a long pause.\n- Work was initiated across multiple plugins to add streaming support, a foundational feature for enabling real-time, conversational AI. This effort included the [OpenAI](https://github.com/elizaos-plugins/plugin-openai) ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)), [Anthropic](https://github.com/elizaos-plugins/plugin-anthropic) ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)), and [OpenRouter](https://github.com/elizaos-plugins/plugin-openrouter) ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)) plugins.\n\n**Refining the User Experience and Planning for the Future**\nMaking the platform intuitive is key to growing our community. This month, we cleared existing UI issues and laid out a detailed plan for a major user experience overhaul.\n- A large number of UI/UX issues were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), streamlining the interface by consolidating navigation ([#6173](https://github.com/elizaos/eliza/issues/6173)) and improving visual feedback ([#6235](https://github.com/elizaos/eliza/issues/6235)).\n- A comprehensive plan for a redesigned dashboard and guided user onboarding was established through the creation of over 20 new strategic issues in [elizaos/eliza](https://github.com/elizaos/eliza) ([#6221](https://github.com/elizaos/eliza/issues/6221), [#6222](https://github.com/elizaos/eliza/issues/6222)).\n- The developer experience was simplified by making ElizaOS Cloud the default AI provider in the CLI, complete with a new browser-based login flow ([elizaos/eliza](https://github.com/elizaos/eliza), [#6208](https://github.com/elizaos/eliza/pull/6208)).\n\n### Cross-Repository Coordination\nThis month saw a coordinated push to standardize and modernize key functionalities across the ElizaOS ecosystem.\n- **Unified Streaming Support:** A parallel effort began across the `plugin-openai`, `plugin-anthropic`, and `plugin-openrouter` repositories to implement streaming. This shared initiative will bring more responsive, real-time interactions to agents regardless of the underlying model provider.\n- **Architectural Alignment:** Following the modernization of core APIs in `elizaos/eliza`, work began in the `plugin-telegram` ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)) and `plugin-discord` ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)) plugins to refactor their messaging systems. This alignment ensures all plugins communicate with the core framework in a standardized, more modular way.\n\n## Repository Spotlights\n\n### elizaos/eliza\nThe core repository saw extensive activity focused on stability, user experience, and future planning.\n- Completed a major server refactoring to optimize the codebase and API structure ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n- Resolved TypeScript build errors across the monorepo, significantly improving code stability and type safety ([#6218](https://github.com/elizaos/eliza/pull/6218)).\n- Updated all project dependencies to their latest versions, resolving compatibility issues ([#6210](https://github.com/elizaos/eliza/pull/6210)).\n- Fixed a critical security bug in character secret encryption ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n- Streamlined the developer experience by making ElizaOS Cloud the default provider in the CLI, adding a new browser-based login flow ([#6208](https://github.com/elizaos/eliza/pull/6208)).\n- Closed a large batch of UI/UX issues, including consolidating the sidebar ([#6173](https://github.com/elizaos/eliza/issues/6173)) and adding an \"Unsaved Changes\" warning ([#6183](https://github.com/elizaos/eliza/issues/6183)).\n- Opened over 20 new issues to define a comprehensive overhaul of the dashboard ([#6222](https://github.com/elizaos/eliza/issues/6222)) and agent creation workflow.\n- Addressed community concerns regarding token snapshot eligibility for Tangem wallet users ([#6158](https://github.com/elizaos/eliza/issues/6158), [#6211](https://github.com/elizaos/eliza/issues/6211)).\n\n### elizaos-plugins/registry\nThe registry was expanded with new plugins, broadening agent capabilities in Web2 and Web3.\n- Added the Moralis DeFi plugin (`@pyboom/plugin-moralis-v2`) to provide agents with Moralis v2 functionalities ([#235](https://github.com/elizaos-plugins/registry/pull/235)).\n- Integrated the OpenChat plugin (`@tonyflam/plugin-openchat`) for agent communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n- Introduced a self-hosted Farcaster plugin (`plugin-farcaster-local-hub`) that removes dependency on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n### elizaos-plugins/plugin-mcp\nWork focused on foundational improvements for agent memory and tool interaction.\n- Refactored memory handling by introducing an optional `mcpText` field and updating `handleToolResponse` to return a `Memory` object, enabling more robust agent configuration ([#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n### elizaos-plugins/plugin-openai\nDevelopment began on a key feature for real-time interaction.\n- Initiated work to add streaming support, opening a pull request to handle continuous data flows from the OpenAI API ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n\n### elizaos-plugins/plugin-anthropic\nWork started on enhancing the plugin's real-time capabilities.\n- A pull request was opened to introduce streaming support, enabling more dynamic and responsive agent communication ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)).\n\n### elizaos-plugins/plugin-openrouter\nA significant enhancement was proposed to improve responsiveness.\n- Work began on adding streaming support and refining the plugin's focus by removing tools support ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)).\n\n### elizaos-plugins/plugin-telegram\nA major architectural refactor was initiated to improve integration with the core framework.\n- A pull request was opened to implement a unified messaging API, aiming to standardize communication and enhance modularity ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)).\n\n### elizaos-plugins/plugin-discord\nThe plugin's internal architecture was improved for better maintainability.\n- Work began on refactoring the message handling system to improve its structure and prepare for future enhancements ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n### elizaos-plugins/plugin-mysql\nActivity focused on user support and documentation clarification.\n- Resolved an issue by clarifying that documentation has been centralized in the `elizaos/docs` repository ([#6122](https://github.com/elizaos-plugins/plugin-mysql/issues/6122)).\n- Provided a helpful tip to users that disabling other plugins may be necessary for successful initial table creation ([#1](https://github.com/elizaos-plugins/plugin-mysql/issues/1))." }, "github_extracted_data_monthly_stats_text_2025-01": "{\n \"interval\": {\n \"intervalStart\": \"2025-01-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-02-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-01-01 to 2025-02-01, elizaos/eliza had 1039 new PRs (735 merged), 401 new issues, and 694 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs6l7_A4\",\n \"title\": \"Missing Module: '@anush008/tokenizers-linux-arm64-gnu'\",\n \"author\": \"morning3tar\",\n \"number\": 2242,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-13T13:29:04Z\",\n \"closedAt\": \"2025-03-08T01:09:54Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 30\n },\n {\n \"id\": \"I_kwDOMT5cIs6lSxzf\",\n \"title\": \"Error: Could not find wrtc binary on any of the paths when running pnpm start\",\n \"author\": \"arvin-crypto\",\n \"number\": 1965,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-07T15:47:26Z\",\n \"closedAt\": \"2025-03-02T01:55:50Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 27\n },\n {\n \"id\": \"I_kwDOMT5cIs6mwy61\",\n \"title\": \"@elizaos/agent@0.1.9-alpha.1 start: `node --loader ts-node/esm src/index.ts \\\"--isRoot\\\" \\\"--characters=characters/eternalai.character.json\\\"`\",\n \"author\": \"illink7\",\n \"number\": 2530,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-19T20:13:23Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 22\n },\n {\n \"id\": \"I_kwDOMT5cIs6m5hCt\",\n \"title\": \"Bot is only responding to target users and ignoring all other mentions on twitter\",\n \"author\": \"Xayaan\",\n \"number\": 2563,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-20T18:46:01Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 21\n },\n {\n \"id\": \"I_kwDOMT5cIs6lwYFX\",\n \"title\": \"\u2009ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL\u2009\",\n \"author\": \"TobiGoldD\",\n \"number\": 2127,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-10T19:14:51Z\",\n \"closedAt\": \"2025-03-02T01:56:01Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 20\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6H-S3t\",\n \"title\": \"chore: dev => main 0.1.9\",\n \"author\": \"odilitime\",\n \"number\": 2361,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-16T09:01:27Z\",\n \"mergedAt\": \"2025-02-01T00:59:40Z\",\n \"additions\": 250702,\n \"deletions\": 16452\n },\n {\n \"id\": \"PR_kwDOMT5cIs6JBWtl\",\n \"title\": \"Add Access Token Management\",\n \"author\": \"elpulpo0\",\n \"number\": 2808,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-26T22:16:38Z\",\n \"mergedAt\": null,\n \"additions\": 224271,\n \"deletions\": 12973\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HcIgk\",\n \"title\": \"chore: Prep v0.1.8 (dev => main)\",\n \"author\": \"odilitime\",\n \"number\": 2171,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-11T23:36:42Z\",\n \"mergedAt\": \"2025-01-12T07:32:53Z\",\n \"additions\": 100844,\n \"deletions\": 46015\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HLoVX\",\n \"title\": \"Fix/resolve conflicts\",\n \"author\": \"yueliao11\",\n \"number\": 2060,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T09:58:41Z\",\n \"mergedAt\": null,\n \"additions\": 87145,\n \"deletions\": 43714\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HJPhr\",\n \"title\": \"Development\",\n \"author\": \"juansebsol\",\n \"number\": 2041,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T01:24:35Z\",\n \"mergedAt\": null,\n \"additions\": 81946,\n \"deletions\": 43391\n }\n ],\n \"codeChanges\": {\n \"additions\": 450243,\n \"deletions\": 138188,\n \"files\": 2487,\n \"commitCount\": 5528\n },\n \"completedItems\": [\n {\n \"title\": \"chore: support more debians distros\",\n \"prNumber\": 1875,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdd more playwright support for various debian distros.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n## Why are we doing this? Any c\"\n },\n {\n \"title\": \"fix: Fix postinstall script\",\n \"prNumber\": 1872,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes develop's install-phase (broken in #1834 )\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n## Why are we doing this? Any context\"\n },\n {\n \"title\": \"docs: Add DAO donation ask & dev discord\",\n \"prNumber\": 1867,\n \"type\": \"feature\",\n \"body\": \"Self explanatory I hope\"\n },\n {\n \"title\": \"feat: Add Stargaze plugin\",\n \"prNumber\": 1861,\n \"type\": \"feature\",\n \"body\": \"This plugins allows Eliza to get NFT information from the main NFT marketplace in Cosmos (Stargaze). \\r\\n\\r\\n\\\"image\\\"\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1838\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR \"\n },\n {\n \"title\": \"test: adding more tests for goals,memory and provider. Fixing generation.test.ts\",\n \"prNumber\": 1840,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/186\\r\\nhttps://github.com/elizaOS/eliza/issues/183\\r\\nhttps://github.\"\n },\n {\n \"title\": \"correct faq docs link in both contribution md files\",\n \"prNumber\": 1839,\n \"type\": \"other\",\n \"body\": \"This pull request includes a small change to the `CONTRIBUTING.md` and `docs/docs/contributing.md` files. The change corrects the link to the FAQ page to point to the correct location.\\r\\n\\r\\n* [`CONTRIBUTING.md`](diffhunk://#diff-eca12c0a30e25\"\n },\n {\n \"title\": \"chore: update bootstrap plugin export\",\n \"prNumber\": 1836,\n \"type\": \"other\",\n \"body\": \"Relates to:\\r\\nPlugin export collisions in character files\\r\\n\\r\\nRisks\\r\\nLow - This is a minor bug fix that ensures proper module exports\\r\\n\\r\\nBackground\\r\\nWhat does this PR do?\\r\\nEnsures the bootstrap plugin has a proper default export at the bottom\"\n },\n {\n \"title\": \"Update README_KOR.md\",\n \"prNumber\": 1835,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nModified the previous sentence to align with the meaning in Korean.\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1725\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/917\\r\\nhttps://github.com/eli\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 1829,\n \"type\": \"other\",\n \"body\": \"Grok / xAI API Key are the same. Same endpoint. It's confusing to split it into Grok and xAI separately. If someone wants to use Grok, they will enter their xAI API key at the GROK_API_KEY, and it works.\"\n },\n {\n \"title\": \"fix(solana token provider): await cached data\",\n \"prNumber\": 1828,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nExecuting trades\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/1483/\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nMaintains original document structure and layout\\r\\nPreserves all formatting, emojis, and technical terms\\r\\n\"\n },\n {\n \"title\": \"docs: update faq.md\",\n \"prNumber\": 1746,\n \"type\": \"docs\",\n \"body\": \"Removed mentions of some items.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo issue for this pr\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n#1694\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo specific issue or ticket.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nFix issue where an agent on twitter tries to use ImageDescriptionService to get the description of a picture from a twitter \"\n },\n {\n \"title\": \"fix: 1634 fix image description service\",\n \"prNumber\": 1667,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n[(https://github.com/elizaOS/eliza/issues/1643 ]\\r\\n)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nGenerating image\"\n },\n {\n \"title\": \"fix: Update Supabase schema.sql\",\n \"prNumber\": 1660,\n \"type\": \"bugfix\",\n \"body\": \"There is an extra semicolon that causes a syntax error when trying to upload the schema to Supabase.\\r\\n\\r\\n(ie. by using the SQL editor in the GUI, it fails due to this syntax error)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes Supa\"\n },\n {\n \"title\": \"fix: Fix bug in plugin-bootstrap/src/evaluators/facts.ts\",\n \"prNumber\": 1648,\n \"type\": \"bugfix\",\n \"body\": \"{{user1}} should be {{user2}} :\\r\\n\\r\\n-------\\r\\nin factEvaluator, in the examples template,\\r\\n\\r\\n{{user1}} should be {{user2}} instead\\r\\n\\r\\n {\\r\\n user: \\\"{{user1}}\\\",\\r\\n content: { text: \\\"Which city?\"\n },\n {\n \"title\": \"Added Hungarian README\",\n \"prNumber\": 1645,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\nzero \\r\\n\\r\\n## What does this PR do?\\r\\nAdd Hungarian README\\r\\n\\r\\n## Discord username\\r\\nmhoused\\r\\n\"\n },\n {\n \"title\": \"fix: lockfile wasn't updated after dependency + bring viem to root level package.json\",\n \"prNumber\": 1642,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to:\\r\\n\\r\\nTrunk being broken\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This change updates the `pnpm-lock.yaml` file, which could affect dependency resolutions. Potential risks include:\\r\\n\\r\\n- **Dependency Resolution Changes:** Updates might lead to differen\"\n },\n {\n \"title\": \"chore: update viem dependency version in plugin-evm and plugin-goat\",\n \"prNumber\": 1637,\n \"type\": \"other\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1635\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nupdate the version of viem to 2.21.58 in plugin-evm and plugin-goat.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nUpdate\"\n },\n {\n \"title\": \"Add README_AR.md\",\n \"prNumber\": 1634,\n \"type\": \"feature\",\n \"body\": \"Add Arabic language for readme.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow - This change affects the Docker container configuration. It may require updates to documentation and\"\n },\n {\n \"title\": \"fix: Support for Non-OpenAI Models in Token Trimming\",\n \"prNumber\": 1605,\n \"type\": \"bugfix\",\n \"body\": \"related: \\r\\nhttps://github.com/elizaOS/eliza/issues/1439\\r\\nhttps://github.com/elizaOS/eliza/issues/1565\\r\\n\\r\\nneed to be tested: https://github.com/elizaOS/eliza/issues/1439#issuecomment-2566405036\"\n },\n {\n \"title\": \"fix: activate web-search plugin in agents/\",\n \"prNumber\": 1577,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n- Issues reported by using of crashes due to this error `Error in trust score provider: Cannot read prope\"\n },\n {\n \"title\": \"feat: use custom conditions for live monorepo types\",\n \"prNumber\": 1365,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nCloses: #1363\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\"\n },\n {\n \"title\": \"Feat/genlayer plugin\",\n \"prNumber\": 975,\n \"type\": \"feature\",\n \"body\": \"This is my first time contributing to this project. I've based my code on the docs, but mostly copying other plugins\\r\\n\\r\\nPlease let me know anything that can be improved :)\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nDTS-error-mismatch-LanguageModelV1-in-ai-sdk-m\"\n },\n {\n \"title\": \"chore(plugin-coinbase): Update tokenContract.ts\",\n \"prNumber\": 2781,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nSometimes an LLM like llama-70b might not return a valid JSON format and this can cause random errors tha\"\n },\n {\n \"title\": \"feat: added Ankr plugin\",\n \"prNumber\": 2773,\n \"type\": \"feature\",\n \"body\": \"# Ankr Plugin for Eliza AI Flow\\r\\n![ankr](https://github.com/user-attachments/assets/553e6c0a-8850-4d68-a711-7b13ce443686)\\r\\n \\r\\nAnkr APIs as Data & Execution Layer:\\r\\n\\r\\nAgents use Ankr\u2019s Multi-Chain RPC to monitor real-time asset prices, liq\"\n },\n {\n \"title\": \"feat: Add Amazon Bedrock as LLM provider\",\n \"prNumber\": 2769,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2753\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow risk: the changed code should only impact a runtime when Amazon Bedrock is used \"\n },\n {\n \"title\": \"feat: create /.turbo/config.json\",\n \"prNumber\": 2768,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nremote cache\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n429 error when running TON plugin to sending a TX.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n#2742\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**: The change introduces a restriction mechanism for the bot's responses, which only applies if `allowedChannelIds` is defined in the configuration. Existing behavi\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2741,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEnv variables, \\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\nPretty simple update, just adding to `.env.example\"\n },\n {\n \"title\": \"feat: minimal workflow to resolve ephemeral check\",\n \"prNumber\": 2735,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nmerge queue\\r\\n\\r\\n\\r\\n## What does this PR do?\\r\\nCurrent intended path links.\\r\\n## What kind of change is this?\\r\\nDocumentation links.\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAdding a dedicated Sei plugin that streamlines the development experience for creating agents that can in\"\n },\n {\n \"title\": \"client-eliza-home: test config and test coverage\",\n \"prNumber\": 2719,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2718\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNew feature addition.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nLit Protocol Integration for ElizaOS\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCore Mina blockchain plugin for Eliza OS that provides essential services and actions for token operati\"\n },\n {\n \"title\": \"feat: Hyperbolic-plugin \",\n \"prNumber\": 2701,\n \"type\": \"feature\",\n \"body\": \"\\r\\n![Screenshot 2025-01-23 at 13 11 03](https://github.com/user-attachments/assets/531c96fb-9a01-40ef-8b04-4e8214832efb)\\r\\n\\r\\n\\r\\n# Hyperbolic Plugin for ElizaOS\\r\\n\\r\\n## Overview\\r\\nThis PR introduces a new plugin for managing GPU instances on the H\"\n },\n {\n \"title\": \"Mostly aesthetic changes, fixed some wonky bullets and numbered lists.\",\n \"prNumber\": 2698,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nDocumentation\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Provide aesthetic tweaks (some wonky bullets and structure)\\r\\n- Add some minor clarifications\\r\\n- Update for newer characters\\r\\n\\r\\n## What kind of change is this?\\r\"\n },\n {\n \"title\": \"chore: fix types syntax issue\",\n \"prNumber\": 2694,\n \"type\": \"bugfix\",\n \"body\": \"fixes missing `};` before simsai profile inteface\"\n },\n {\n \"title\": \"feat(new-plugin): Eliza OmniFlix Plugin\",\n \"prNumber\": 2693,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nOmniFlix Network Integration Plugin for Eliza AI Agent\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2206\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nA plugin that integrates BitMind's API into ElizaOS agents, enabling access to AI services and digital \"\n },\n {\n \"title\": \"feat(new-plugin): suno music generation \",\n \"prNumber\": 2679,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"feat(new-plugin): eliza samsung smarthings plugin\",\n \"prNumber\": 2678,\n \"type\": \"feature\",\n \"body\": \"# Client-Eliza-Home Functionality Overview\\r\\n\\r\\n## Core Purpose\\r\\nThe client-eliza-home package serves as a bridge between ElizaOS and SmartThings-enabled smart home devices, enabling natural language control and automation of home devices.\\r\\n\\r\"\n },\n {\n \"title\": \"Revert \\\"feat(new-plugin): suno Eliza plugin\\\"\",\n \"prNumber\": 2673,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2656\\r\\n\\r\\nPlugin not ready, implements old plugin interface etc\"\n },\n {\n \"title\": \"feat: Implement runProcess function in test library\",\n \"prNumber\": 2672,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nImproving test utilities functionality\\r\\n\\r\\n# Risks\\r\\nLow - This is a test utility function implementation that:\\r\\n- Only affects test code, not production code\\r\\n- Uses standard Node.js APIs (spawn)\\r\\n- Has proper error handling\\r\\n-\"\n },\n {\n \"title\": \"fix debug targets to show elizalogger debug messages\",\n \"prNumber\": 2670,\n \"type\": \"bugfix\",\n \"body\": \"fix for #2667 \\r\\nJust fixes the two debug targets in the package.json to include `DEFAULT_LOG_LEVEL=debug`\"\n },\n {\n \"title\": \"chore(spelling-fixes): docs\",\n \"prNumber\": 2669,\n \"type\": \"bugfix\",\n \"body\": \"Hello\\r\\nI fixed several spelling issue.\\r\\nBr, Elias.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated README.md with improved grammatical clarity in instruct\"\n },\n {\n \"title\": \"fix(plugin-depin): sentientAI description\",\n \"prNumber\": 2668,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nIssue #2657 \\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow: This change only modifies the GitBook provider\u2019s return format to incl\"\n },\n {\n \"title\": \"feat(new-plugin): suno Eliza plugin\",\n \"prNumber\": 2656,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"fix: a typo bug in conflux plugin\",\n \"prNumber\": 2654,\n \"type\": \"bugfix\",\n \"body\": \"In handler function of packages/plugin-conflux/src/actions/confiPump.ts:\\r\\n\\r\\n```\\r\\n // Generate content based on template\\r\\n const context = composeContext({\\r\\n state,\\r\\n template: confluxTransferTemplate, \"\n },\n {\n \"title\": \"feat: Add swap & improvements for multiversx-plugin\",\n \"prNumber\": 2651,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nThe PR is not related to any issues.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2620\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Updated `.gitignore` to exclude `node-comp\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2596,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Relates to\\r\\n\\r\\n## LINK TO ISSUE OR TICKET \\r\\nhttps://github.com/elizaOS/eliza/issues/2561\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2572\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- *\"\n },\n {\n \"title\": \"feat(plugin-farcaster): test config and test coverage\",\n \"prNumber\": 2567,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2566\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added text-to-speech support for Indonesian, Tagalog, and M\"\n },\n {\n \"title\": \"fix:Incorrect boolean parsing for ENABLE_OPEN_AI_COMMUNITY_PLUGIN setting #2559\",\n \"prNumber\": 2560,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2559\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\nThis change only affects the configuration parsing for the ENABLE_OPEN_AI_COMM\"\n },\n {\n \"title\": \"chore(revert): optimize pnpm cache configuration\",\n \"prNumber\": 2556,\n \"type\": \"other\",\n \"body\": \"edit: reverting most pnpm caching attempts\"\n },\n {\n \"title\": \"chore: optimize pnpm cache configuration\",\n \"prNumber\": 2555,\n \"type\": \"other\",\n \"body\": \"Optimizes pnpm cache configuration to improve package reuse during installation.\\n\\nChanges made:\\n- Move pnpm setup before cache configuration\\n- Add architecture-specific cache keys\\n- Include package.json in cache key for better specificity\\n-\"\n },\n {\n \"title\": \"feat: Cosmos Plugin - IBC swap action\",\n \"prNumber\": 2554,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n# Risks\\r\\nLow risk \u2013 this PR adds an action to an existing plugin and does not interfere with the core f\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2553,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2551,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"feat(plugin-devin): implement client-agnostic Devin plugin\",\n \"prNumber\": 2549,\n \"type\": \"feature\",\n \"body\": \"# Devin Plugin PR\\n\\n## Changes\\n- Implemented client-agnostic Devin plugin\\n- Added comprehensive test coverage\\n- Created detailed README documentation\\n- Merged develop branch successfully\\n\\n## Testing\\n- Unit tests passing\\n- API integration ver\"\n },\n {\n \"title\": \"feat: Updated READ.me file with pre-requisites to enable telegram bot\",\n \"prNumber\": 2547,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nTelegram Client\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Renamed internal method for object generation\\n\\t- Improved code formatting and readability\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Improved error handling for AgentKit actions initialization\\n\\t- Enhanced code readability with formatting adjustments i\"\n },\n {\n \"title\": \"test configuration and tests for client-lens\",\n \"prNumber\": 2534,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2533\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/5bdc0051-b97c-450b-be29-1cc66ea1d1b6\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFollow up on https:/\"\n },\n {\n \"title\": \"feat: add anthropic image provider for vision\",\n \"prNumber\": 2524,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nVision image descriptions\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow: \\r\\nadded an image provider for anthropic which generally defaulted to openai. so the risk is pretty low\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nadd AnthropicImageProvider \"\n },\n {\n \"title\": \"feat: plugin rabbi trader tests\",\n \"prNumber\": 2520,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2519\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFeature/plugin coingecko #1761\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Documentation**\\r\\n\\t- Added a citation section to the R\"\n },\n {\n \"title\": \"docs: add docs/README_JA.md\",\n \"prNumber\": 2515,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated Japanese README with comprehensive project details\\n\\t- Added project overview for Eliza\\n\\t- Included setup \"\n },\n {\n \"title\": \"feat: add support for NVIDIA inference for ElizaOS\",\n \"prNumber\": 2512,\n \"type\": \"feature\",\n \"body\": \"\\r\\n![nvidia](https://github.com/user-attachments/assets/f27fe3f8-9daf-4dc2-9c6c-93deda5f9da4)\\r\\n\\r\\n\\r\\n# Add NVIDIA Model Provider Support to ElizaOS\\r\\n\\r\\nThis PR adds support for NVIDIA's AI models through their inference API, expanding ElizaOS's\"\n },\n {\n \"title\": \"test: plugin-tee - adjusting project structure and new tests\",\n \"prNumber\": 2508,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2507\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- `@elizaos/plugin-agentkit` - default configuration in the agent/src/index.ts file for easier import b\"\n },\n {\n \"title\": \"test: api timeout handling for plugin-binance\",\n \"prNumber\": 2504,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2486\\r\\n\\r\\n\\r\\n\\r\\nThis PR introduces the new **plugin-openai** for text generation functionality using OpenAI's GPT models.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nNo linked issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. \\r\\nThis change introduces a default logger level, which affects logging outputs. Potential risks include unexpected logging behavior if the `DEFAULT_LOG_L\"\n },\n {\n \"title\": \"feat(plugin-new): initia plugin + chore revert to integrationTests from stable release 0.1.7\",\n \"prNumber\": 2448,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nI am developing Initia plugin for elizaOS.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nThis PR is base initia plugin development. I implemented INIT token transfer action for agent.\\r\\n\\r\\n## What kind of ch\"\n },\n {\n \"title\": \"feat: create version.cmd for windows support\",\n \"prNumber\": 2442,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue: Build failures on Windows platform\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes are isolated to build scripts and type definitions. No runtime behavior is affected.\\r\\n\\r\\n- Windows build script changes only affect local development on Wi\"\n },\n {\n \"title\": \"feat: add Mind Network plugin\",\n \"prNumber\": 2431,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo specific linked issue or ticket, as this is a feature addition for the Mind Network plugin.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n\\r\\nThe plugin is newly introduced and self-contained, limiting its impact on unrelated parts of the Eliza ecos\"\n },\n {\n \"title\": \"fix: Fix Incorrect Tweet ID Parameter Passed to sendTweet Function\",\n \"prNumber\": 2430,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1958#issuecomment-2582289612\\r\\n\\r\\nThe issue occurred because the LLM generated a verbose response like:\\r\\n\\\"Received The most interesting and relevant tweet for XXX to reply to is 187954009886315\"\n },\n {\n \"title\": \"feat:add plugin-lightning\",\n \"prNumber\": 2429,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-lightning\\r\\n\\r\\nThis plugin enables create lightning invoice or payInvoice.\\r\\n\\r\\n## Features\\r\\n\\r\\n- \ud83d\udcb1 Make a new off-chain invoice.\\r\\n- \ud83d\udcca Make an off-chain payment.\\r\\n\\r\\n## Installation\\r\\n\\r\\nAdd the plugin to your Eliza configuratio\"\n },\n {\n \"title\": \"feat: add a way to create/store/restore agents in the filesystem\",\n \"prNumber\": 2389,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo Issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nAs it is using a env variable to enable/disable the feature, there are no risks involved.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nIf USE_CHARACTER_STORAGE is enabled in the .env:\\r\\n\\r\\nIt stores a\"\n },\n {\n \"title\": \"feat: plugin for OriginTrail Decentralized Knowledge Graph\",\n \"prNumber\": 2380,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A - New plugin contribution\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n- Requires you to explicitly provide your private key in the environment variable before it does anything with your funds\\r\\n- Creation of OriginTrail Knowledge Assets spends y\"\n },\n {\n \"title\": \"feat: add adapter-qdrant\",\n \"prNumber\": 2322,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd qdrant adapter into Eliza system.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes [#2272](https://github.com/elizaOS/eliza/issues/2272)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nAI Agent Dev School Video #2: https://www.youtube.com/watch?v=XenGeAcPAQo&t=3383s \\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore: updated .gitignore + removed build files\",\n \"prNumber\": 3117,\n \"type\": \"other\",\n \"body\": \"chore: updated .gitignore + removed build files\"\n },\n {\n \"title\": \"fix: auto-scrolling issue in client\",\n \"prNumber\": 3115,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1977\\r\\n\\r\\nNoticed that when chatting with a character on the client, the conversation doesn\u2019t automatically scroll to the bottom after submitting a message and receiving a response. This PR fix\"\n },\n {\n \"title\": \"fix: fixing the error parsing json when an array is a value in a JSON\u2026\",\n \"prNumber\": 3113,\n \"type\": \"bugfix\",\n \"body\": \"\u2026 object\\r\\n\\r\\n# Relates to\\r\\n\\r\\nHaven't created a ticket, but it seems to be related to recent changes in the `normalizeJsonString` function.\\r\\n\\r\\nWhen using the Slack client, JSON like:\\r\\n\\r\\n```json\\r\\n{\\r\\n \\\"objective\\\": \\\"The user wants to summarize \"\n },\n {\n \"title\": \"fix: docker build command by skipping eslint files\",\n \"prNumber\": 3110,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\nRunning docker build fails because eslint config have been removed\\r\\n![Screenshot 2025-01-31 at 14 13 58](https://github.c\"\n },\n {\n \"title\": \"fix: plugin-apro\",\n \"prNumber\": 3106,\n \"type\": \"bugfix\",\n \"body\": \"Investigated and added the peoper ether to the configuration it was missing and fixed all the code.\"\n },\n {\n \"title\": \"fix: plugin-aptos\",\n \"prNumber\": 3104,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all the issues and added Biome.\"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? 11\\\" notes\",\n \"prNumber\": 3103,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary document for \\\"What Did You \"\n },\n {\n \"title\": \"fix: plugin-arthera-biome\",\n \"prNumber\": 3102,\n \"type\": \"bugfix\",\n \"body\": \"fixed al issues \"\n },\n {\n \"title\": \"fix: plugin-asterai\",\n \"prNumber\": 3101,\n \"type\": \"bugfix\",\n \"body\": \"Added only the Biome. Code was good.\"\n },\n {\n \"title\": \"fix: plugin-autonome-v1\",\n \"prNumber\": 3098,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all issues.\"\n },\n {\n \"title\": \"fix: fixed build error in plugin-email-automation \",\n \"prNumber\": 3097,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3071\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3067\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3062\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nNavigate links to specified resources\\r\\n## What kind of change is this?\\r\\nDocum\"\n },\n {\n \"title\": \"fix: OpenAI embedding issue\",\n \"prNumber\": 3003,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: OpenAI embeddings error when running character without OpenAI API key configured in .env file. \\r\"\n },\n {\n \"title\": \"feat (chore): plugin avalanche test config and coverage\",\n \"prNumber\": 2999,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2998\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2996\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2991\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2981\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2979\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNo specific issue or ticket. This PR updates the README with a French\"\n },\n {\n \"title\": \"fix: handle whitespace in quote conversion\",\n \"prNumber\": 2961,\n \"type\": \"bugfix\",\n \"body\": \"I noticed that array parsing sometimes fails because, in this PR (https://github.com/elizaOS/eliza/pull/2802/files), the regex matches 'something' only if it is immediately followed by a comma, closing brace, or closing bracket, without any\"\n },\n {\n \"title\": \"fix: plugin-letzai\",\n \"prNumber\": 2960,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors.\"\n },\n {\n \"title\": \"fix: plugin-lightning\",\n \"prNumber\": 2959,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors and also the missing use of Zod.\"\n },\n {\n \"title\": \"fix: plugin-lit\",\n \"prNumber\": 2957,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and leaved only 3 any that we can change only afer testing. \"\n },\n {\n \"title\": \"fix: plugin-massa\",\n \"prNumber\": 2955,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors.\"\n },\n {\n \"title\": \"fix-plugin-mina\",\n \"prNumber\": 2954,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: mind-network\",\n \"prNumber\": 2953,\n \"type\": \"bugfix\",\n \"body\": \"Added only missing logging.\"\n },\n {\n \"title\": \"fix: plugin-moralis\",\n \"prNumber\": 2952,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the issues.\"\n },\n {\n \"title\": \"fix: {{maxTweetLength}} doesn't work in tweet post template \",\n \"prNumber\": 2951,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/2927\"\n },\n {\n \"title\": \"fix: remove unnecessary @ts-expect-error directive in chat component\",\n \"prNumber\": 2950,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\nTypeScript error TS2578 in chat component\\r\\n\\r\\n# Risks\\r\\nLow - This is a simple removal of an unnecessary TypeScript directive that was causing an error.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nRemoves an unnecessary @ts-exp\"\n },\n {\n \"title\": \"fix: add missing plugins in package.json\",\n \"prNumber\": 2947,\n \"type\": \"feature\",\n \"body\": \"There were several missing plugins in package.json, which prevented the app from starting. I\u2019ve added them back. It seems this issue was caused by a merge conflict in this: https://github.com/elizaOS/eliza/commit/b3bc2547285663abbf4c3852f38\"\n },\n {\n \"title\": \"fix: remove dead code\",\n \"prNumber\": 2945,\n \"type\": \"bugfix\",\n \"body\": \"removed dead code (comments)\"\n },\n {\n \"title\": \"fix: plugin-movement\",\n \"prNumber\": 2943,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: plugin-multiversx\",\n \"prNumber\": 2942,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors present. \"\n },\n {\n \"title\": \"fix: plugin-near\",\n \"prNumber\": 2941,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and typing.\"\n },\n {\n \"title\": \"fix: plugin-news\",\n \"prNumber\": 2940,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the type and literals.\"\n },\n {\n \"title\": \"fix: building error\",\n \"prNumber\": 2938,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: plugin-nft-collection\",\n \"prNumber\": 2937,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and most if not all the typing.\"\n },\n {\n \"title\": \"fix: plugin-nft-generation\",\n \"prNumber\": 2934,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed partially the typing and the reassigmnet logic. To fix it all we need to redo partially the code. I leave for a nother PR.\"\n },\n {\n \"title\": \"feat: add public access to packages.\",\n \"prNumber\": 2933,\n \"type\": \"feature\",\n \"body\": \"This ensures all packages that are not marked private are properly scoped and can be published to npm registry.\"\n },\n {\n \"title\": \"fix template typos\",\n \"prNumber\": 2932,\n \"type\": \"bugfix\",\n \"body\": \"Minor fixes as first contribution, noticed while diving source code\"\n },\n {\n \"title\": \"chore: inconsistent folder naming conventipn\",\n \"prNumber\": 2931,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: invalid npm package naming convention\",\n \"prNumber\": 2930,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: missing version prop in package.json\",\n \"prNumber\": 2929,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"ci: changes to allow package scoping to public\",\n \"prNumber\": 2928,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update lpmanager.character.json\",\n \"prNumber\": 2921,\n \"type\": \"other\",\n \"body\": \"The subject of the sentence is \\\"the center price\\\", which is singular, so the correct verb form is \\\"is\\\" instead of \\\"are\\\".\"\n },\n {\n \"title\": \"feat: new model provider for LM Studio\",\n \"prNumber\": 2913,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd LM Studio model provider\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2859\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2853\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2849\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue yet; can file an issue if you'd like?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"fix: plugin-tts \",\n \"prNumber\": 2829,\n \"type\": \"bugfix\",\n \"body\": \"Fixed non-critical issues highlighted by strict biome linting:\\n- Updated imports to use `node:` prefix\\n- Changed bracket notation to dot notation for object access\\n- Added explicit type for `target_voice`\\n- Simplified environment variable a\"\n },\n {\n \"title\": \"feat: add new readmes, move some others for consistency\",\n \"prNumber\": 2828,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, its documentation \\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUpdates the d\"\n },\n {\n \"title\": \"fix: plugin-zksync-era multiple errors and issues as documented\",\n \"prNumber\": 2819,\n \"type\": \"bugfix\",\n \"body\": \"# Fix plugin-zksync-era\\r\\n\\r\\n- Replace non-null assertion with fallback in useGetAccount\\r\\n- Avoid parameter reassignment in transferAction handler\\r\\n- Add explicit typing for hash variable\\r\\n- Convert string concatenations to template literals\\r\"\n },\n {\n \"title\": \"fix: nvidia nim environment\",\n \"prNumber\": 2817,\n \"type\": \"bugfix\",\n \"body\": \"# Fix: NVIDIA NIM Plugin Environment Variables Typo\\r\\n\\r\\n## Changes\\r\\n- Fixed typo in environment variable names in `actionGetTopic.ts`:\\r\\n - `NVIDIA_OFFTOPIC_SYSTEM`\\r\\n - `NVIDIA_OFFTOPIC_USER`\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/p\"\n },\n {\n \"title\": \"fix: akash splash \",\n \"prNumber\": 2816,\n \"type\": \"bugfix\",\n \"body\": \"# Akash Plugin UI Enhancement\\r\\n\\r\\n## Changes\\r\\n- Updated splash screen design for Akash plugin\\r\\n- Enhanced visual presentation of the interface\\r\\n- Improved user experience with better layout\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/plug\"\n },\n {\n \"title\": \"docs: Update client-telegram README.md\",\n \"prNumber\": 2814,\n \"type\": \"docs\",\n \"body\": \"Just corrected some formatting issues, and added details about configuration of advanced features via character.json files.\\r\\n\\r\\n\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"feat: Add Access Token Management to MultiversX Plugin\",\n \"prNumber\": 2810,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nmultiversx-plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Add the possibility to limit token management to one user or all user\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements\\r\\n\\r\\n# Documentation change\"\n },\n {\n \"title\": \"test: plugin-0x test configuration and coverage\",\n \"prNumber\": 2807,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2806\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2804\\r\\n\\r\\nNo specific issue or ticket referenced.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nLow \u2014 this PR primarily refines the parsing function\"\n },\n {\n \"title\": \"feat(new-plugin): create gelato plugin relay\",\n \"prNumber\": 2799,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\nNo linked issue. This PR introduces a Gelato Relay plugin with support for both `sponsoredCall` and `sponsoredCallERC2771` functionalities.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Dependency\\r\\n\u2757 \u2757 **Must be merged with : https://github.com/elizaOS/agent-twitter-client/pull/57**\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore(update-plugin-initialization): btcfun & trikon plugin\",\n \"prNumber\": 2643,\n \"type\": \"other\",\n \"body\": \"# btcfun Plugin for Eliza\\r\\n\\r\\n## Description\\r\\nBTC.Fun enables users to effortlessly launch and trade Runes/BRC20 tokens on the Bitcoin network in a permissionless environment. Through the platform, anyone can create their own Runes/BRC20 tok\"\n },\n {\n \"title\": \"feat(client-alexa): Basic Alexa skill notification\",\n \"prNumber\": 2564,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Integrate communication with \"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? #10\\\" notes\",\n \"prNumber\": 2558,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary and transcript for \\\"What Di\"\n },\n {\n \"title\": \"feat(new-plugin): quick intel plugin for token security analysis\",\n \"prNumber\": 2391,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This plugin is isolated and:\\r\\n\\r\\n- Uses established API endpoints\\r\\n- Has proper error handling\\r\\n- Follows existing plugin patterns\\r\\n- No database changes required\\r\\n- No deployment risks\\r\\n\\r\\n# Background\\r\\n\"\n },\n {\n \"title\": \"feat(new-plugin): 0x plugin to swap on evms\",\n \"prNumber\": 2329,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2230\\r\\nCreated a plugin for 0x protocol, a feature request from \"\n },\n {\n \"title\": \"feat: custom s3 endpoint url for 'plugin-node'\",\n \"prNumber\": 2176,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2174, and builds upon https://github.com/elizaOS/eliza/pull/2379\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This affects only the `plugin-node`, and it changes logic in a way that is backward compatible. \\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Separate Knowledge system + Multi-Agent RAG Optimization\",\n \"prNumber\": 1620,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow Risk, as the new RAG system is completely separate, and must be enabled by the user to use as of now.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. ch\"\n },\n {\n \"title\": \"feat(new-plugin): deva client integration\",\n \"prNumber\": 1238,\n \"type\": \"feature\",\n \"body\": \"# Pull Request: Integrate Deva into Eliza\\r\\n\\r\\n## Relates to\\r\\n\\r\\nThis PR adds a new [Deva](https://www.deva.me/) client integration for the Eliza AI agent, enabling posting and scheduling posts to the [Deva](https://www.deva.me/) feed.\\r\\n\\r\\n## R\"\n },\n {\n \"title\": \"feat: Add Extra Multimedia Support for Telegram Client \",\n \"prNumber\": 2510,\n \"type\": \"feature\",\n \"body\": \"This PR is based on https://github.com/elizaOS/eliza/pull/1837\\r\\nI\u2019ve remade this PR because maintainer edit access was not enabled, making it difficult to make necessary changes directly.\\n\\n\\n\\n## Summary by Cod\"\n },\n {\n \"title\": \"chore: update createToken.ts\",\n \"prNumber\": 2493,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\ncreat -> create\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\"\n },\n {\n \"title\": \"chore: corrected the link to the banner\",\n \"prNumber\": 2491,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2481\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on #2328](https://github.com/eliz\"\n },\n {\n \"title\": \"fix: linting errors\",\n \"prNumber\": 2474,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: add openai env to smokeTests\",\n \"prNumber\": 2472,\n \"type\": \"feature\",\n \"body\": \"Reverts elizaOS/eliza#2459\"\n },\n {\n \"title\": \"test: adding test configuration and tests for redis adapter\",\n \"prNumber\": 2470,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2469\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2467\\r\\n\\r\\nThis pull request relates to resolving the issue where `animated.div` from `@react-spring/web` was not accepting the `children` prop in TypeScript, causing type errors.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**\"\n },\n {\n \"title\": \"chore: set openai as default character's provider\",\n \"prNumber\": 2460,\n \"type\": \"other\",\n \"body\": \"chore: set openai as default character's provider\"\n },\n {\n \"title\": \"revert: \\\"refactor: dockerize smoke tests\\\"\",\n \"prNumber\": 2459,\n \"type\": \"refactor\",\n \"body\": \"Reverts elizaOS/eliza#2420\"\n },\n {\n \"title\": \"feat: Add features to the Solana Agent Kit \",\n \"prNumber\": 2458,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1619\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2453\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2405 \\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\"\n },\n {\n \"title\": \"fix: conditional use of useQuery in AgentRoute component to prevent runtime errors.\",\n \"prNumber\": 2413,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nGeneral improvement; no specific issue linked.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2406\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2403\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFix the Remote Attestation Action to prevent hallucination in Twitter and Discord clients when publishing\"\n },\n {\n \"title\": \"feat: add safe_mode (& cfg_scale) for venice image generation\",\n \"prNumber\": 2354,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nVery low\\r\\n\\r\\n# Background\\r\\n\\r\\nVenice has uncensored image generation which may create issues for agents running on platforms with strict terms of service related to nudity or graphic content.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nVenice r\"\n },\n {\n \"title\": \"fix: align base url in client if api runs on a different port\",\n \"prNumber\": 2353,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2344\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAction: DESCRIBE_IMAGE\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow risks, the only risk is that someone hooks up this plugin with their Solana wallet and because it is so easy to use spends more tokens than\"\n },\n {\n \"title\": \"feat: Telegram autonomous agent enhancement\",\n \"prNumber\": 2338,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n[PR 2335](https://github.com/elizaOS/eliza/pull/2335)\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change wh\"\n },\n {\n \"title\": \"fix: formatting in Browser section of README.md\",\n \"prNumber\": 2336,\n \"type\": \"bugfix\",\n \"body\": \"Hey all! I saw strange formatting in the README.md and figured it was an extra three backticks ```\\r\\n\\r\\nSure enough, deleting those made the section render as intended. I also reworded one of the sentences that had three \\\"and\\\"s to make it a l\"\n },\n {\n \"title\": \"feat: Discord autonomous agent enhancement\",\n \"prNumber\": 2335,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\nThis feature add the \"\n },\n {\n \"title\": \"Update README_TR.md\",\n \"prNumber\": 2334,\n \"type\": \"other\",\n \"body\": \"Added WSL 2 link\"\n },\n {\n \"title\": \"fix: SwapAction in evm-plugin\",\n \"prNumber\": 2332,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nfix bugs & improvements in plugin-evm\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\"\n },\n {\n \"title\": \"feat: Enable Multiple remote character urls\",\n \"prNumber\": 2328,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on PR #2281](https://github.com/e\"\n },\n {\n \"title\": \"feat: dexscreener trending\",\n \"prNumber\": 2325,\n \"type\": \"feature\",\n \"body\": \"Adding code from https://github.com/elizaOS/eliza/pull/1584\\r\\nto DS plugin for fetching trending, boosted and latest tokens added to dexscreener\"\n },\n {\n \"title\": \"fix: correct OPENROUTER_API_KEY env in config\",\n \"prNumber\": 2324,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\n# Risks\\r\\nLOW\\r\\n\\r\\n# Background\\r\\nset private runtime envs for each character, eg: \\r\\n```\\r\\ncharacter.settings.secrets = {...privateEnvs};\\r\\n```\\r\\nuse openrouter as ModelProvider and set OPENROUTER_API_KEY as agent runtime secrects\"\n },\n {\n \"title\": \"feat: Onchain Agent Transformer - transform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\",\n \"prNumber\": 2319,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nTransform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env and support for\"\n },\n {\n \"title\": \"docs: Update README.md\",\n \"prNumber\": 2309,\n \"type\": \"docs\",\n \"body\": \"Remove duplicate in the readme\"\n },\n {\n \"title\": \"fix: farcaster memory\",\n \"prNumber\": 2307,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nRe-implements #2039 and updates Remote Attestations to have more content to ensure older generated RA Quo\"\n },\n {\n \"title\": \"fix: Update package.json of core package\",\n \"prNumber\": 2301,\n \"type\": \"bugfix\",\n \"body\": \"these packages are being used in prod build and generate errors if you decide to just use this package in a project.\\r\\n\\r\\n# Background\\r\\n\\r\\nThese packages are being used under src/ folder and needs to be part of the dependencies not dev depende\"\n },\n {\n \"title\": \"feat: coinbase agentkit plugin for eliza\",\n \"prNumber\": 2298,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdding AgentKit EVM support to Eliza\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2223 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2164\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2212\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nGives eliza agents their own abstract global wallets so they can use Abstract similar to how real users\"\n },\n {\n \"title\": \"docs: Add Greek translation for README_GR\",\n \"prNumber\": 2199,\n \"type\": \"feature\",\n \"body\": \"Relates to\\r\\nThis pull request relates to issue https://github.com/elizaOS/eliza/issues/2197.\\r\\n\\r\\nRisks\\r\\nLow: This PR only adds a Greek translation for the README file and updates the main README to include a link to the new translation. No f\"\n },\n {\n \"title\": \"fix(plugin-twitter): change prompt to ensure it returns json\",\n \"prNumber\": 2196,\n \"type\": \"bugfix\",\n \"body\": \"per masterdai https://discord.com/channels/1253563208833433701/1300025221834739744/1327947002943770705\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nPrompt improvement\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-\"\n },\n {\n \"title\": \"refactor: websearch into a service\",\n \"prNumber\": 2195,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\n\\r\\nRemove Tavily from core https://github.com/elizaOS/eliza/issues/2123\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. While it touche\"\n },\n {\n \"title\": \"chore: 0.1.8.build.1 (dev => main)\",\n \"prNumber\": 2194,\n \"type\": \"other\",\n \"body\": \"Fixes docker build\\r\\nUnbotches version for npm publish/release\\r\\n\\r\\nChangelog\\r\\n- #2184\\r\\n- #2182\\r\\n- #2187\\r\\n- #2193\"\n },\n {\n \"title\": \"chore: Prep 0.1.8.build.1\",\n \"prNumber\": 2193,\n \"type\": \"other\",\n \"body\": \"- Bump version to 0.1.8.build.1\"\n },\n {\n \"title\": \"fix postgres adapter migration extension creation which already exists at this point\",\n \"prNumber\": 2188,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2067\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nSuper low-risk, text mutation/scrub prior to sending Tweet.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does \"\n },\n {\n \"title\": \"feat: \ud83c\udf88 perf(vscode): Set file nesting for md and DockerFile\",\n \"prNumber\": 2177,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2172\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/pull/1620\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\nThis is a brand new feature.\\r\\nIt is only effective when using dependency\"\n },\n {\n \"title\": \"refactor: farcaster client env configuration \",\n \"prNumber\": 2087,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\nRefactoring Farcaster Client Implementation\\r\\n\\r\\n# Risks\\r\\nLow - This is primarily a refactoring change that improves code organization and configuration management without changing core functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What \"\n },\n {\n \"title\": \"feat: atoma provider\",\n \"prNumber\": 2082,\n \"type\": \"feature\",\n \"body\": \"# Background\\r\\n\\r\\nAtoma is a decentralized private and verifiable AI execution network. It provides the infrastructure for developers and enterprises to use open-source AI models and build AI applications with full privacy.\\r\\n\\r\\n## What does th\"\n },\n {\n \"title\": \"feat: add external router path and new tweet generation\",\n \"prNumber\": 2081,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nN/A - this is an issue and will be described below in the Backgroun\"\n },\n {\n \"title\": \"feat: full overhaul of client\",\n \"prNumber\": 2038,\n \"type\": \"feature\",\n \"body\": \"This PR replaces the entire `client` app with a refreshed look. From this base it's very easy to add additional features going forward.\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/43e847c9-5d02-43f0-a0c9-a857bc332a03)\\r\\n\\r\\n## Featu\"\n },\n {\n \"title\": \"chore(ci): add pnpm lockfile consistency check workflow\",\n \"prNumber\": 2015,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A - Direct improvement to CI process\\r\\n\\r\\n# Risks\\r\\nLow - This is a new CI workflow that doesn't affect the production code.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nCurrently, on the main branch, `pnpm install` fails to ru\"\n },\n {\n \"title\": \"feat: Adding plugin for B\u00b2 Network\",\n \"prNumber\": 2010,\n \"type\": \"feature\",\n \"body\": \"B\u00b2 Network is a Bitcoin Layer2 network. Add this plugin to integrate with Eliza so that users can interact with B\u00b2 Network through Eliza agent.\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdd B\u00b2 Network plugin into Eliza system.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\nMain implementa\"\n },\n {\n \"title\": \"feat: add instagram client\",\n \"prNumber\": 1964,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, is a new client, does't have any impact on old code.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nImplements a new Instagram client for ElizaOS that:\\r\\n\\r\\n1. Handles Instagram authentication and session management\\r\\n2. Provides media posting\"\n },\n {\n \"title\": \"chore(plugin-solana): replace console with elizaLogger\",\n \"prNumber\": 1888,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nInteracting with Injective chain\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nAdd cross-chain swaps to ElizaOS through Squid Router\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does t\"\n },\n {\n \"title\": \"feat: Add support for VoyageAI embeddings API\",\n \"prNumber\": 1442,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nA bug or change in behavior of embedding provider selection could cause an unexpected switch. This could cause pre-existing embeddings and new embeddings to be incompatible.\\r\\n\\r\\nI removed `isOllama` flag from the config. It seemed\"\n },\n {\n \"title\": \"feat: add birdeye plugin\",\n \"prNumber\": 1417,\n \"type\": \"feature\",\n \"body\": \"# Overview\\r\\n\\r\\n- This PR introduces a new plugin for the data provider [Birdeye](https://www.birdeye.so/). \\r\\n- The plugin includes API endpoints and related types for all [Birdeye API](https://docs.birdeye.so/) endpoints even though not all \"\n },\n {\n \"title\": \"feat: improve GOAT integration by allowing tool calling when using generateText\",\n \"prNumber\": 1403,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://x.com/sunosuporno/status/1870967395780792741\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nTwo main things:\\r\\n1. Update `generateText` API to be able to pass through tool options to leverage the mo\"\n },\n {\n \"title\": \"fix: postgres-adapter - remove nonsensical schema check\",\n \"prNumber\": 1377,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nCloses: https://github.com/elizaOS/eliza/issues/1376\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n- This change only adds support for BNB cha\"\n },\n {\n \"title\": \"feat: Add devcontainer\",\n \"prNumber\": 1807,\n \"type\": \"feature\",\n \"body\": \"Hello from Hunter ($drpxbt) Team\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, no code is changed.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nEnables to open workspace in devcontainer (docker with vs code)\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nIm\"\n },\n {\n \"title\": \"fix: fix the chat stuck in infinite loop\",\n \"prNumber\": 1755,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nthe chat stuck in infinite loop when using model_local https://github.com/elizaOS/eliza/issues/1213\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2169\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"add github to client enumerations\",\n \"prNumber\": 2157,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdding the github to the `Clients` enumeration due to error when trying to run. `Invalid enum value'\\r\\n\\r\\n<\"\n },\n {\n \"title\": \"fix: correct SUI/USD price calculation\",\n \"prNumber\": 2150,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to Eliza client-twitter/plugin/SttTtsSpacesPlugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAI function enhancement, similar with #1446, @odilitime \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nbug fix typo\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: Lens Network Plugin\",\n \"prNumber\": 2101,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n---\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow \\r\\n- This change only adds support for the Lens Testnet network to enable transfers of Grass tokens between users. \\r\\n- Other features and functionalities of \"\n },\n {\n \"title\": \"Fix: Supabase updates\",\n \"prNumber\": 2100,\n \"type\": \"bugfix\",\n \"body\": \"Fixes an issue where missing rooms in the Supabase database caused errors when fetching them using `.single()`. Additionally, ensures that the database seed values contain valid timestamps and required non-null fields. Also fixes an issue w\"\n },\n {\n \"title\": \"Add gemini to image vision\",\n \"prNumber\": 2099,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - This PR adds a new embedding model provider (Heurist) with BAAI/bge-large-en-v1.5 as the default model. Changes are additive and follow existing patterns.\\r\\n\\r\\n# Backgro\"\n },\n {\n \"title\": \"fix: Update clients.md to fix package name\",\n \"prNumber\": 2091,\n \"type\": \"bugfix\",\n \"body\": \"@eliza needs to be @elizaos in order for successful installation and imports\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nThere is no risk because only documentation is added.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\\r\\n# Relates to\\r\\n- The Korean README file (`README_KOR.md`).\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"Update README_CN to match latest English README\",\n \"prNumber\": 2069,\n \"type\": \"tests\",\n \"body\": \"# Relates to\\r\\n\\r\\n- The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Risks\\r\\n\\r\\n- **Low**: This PR only updates documentation and does not affect code or functionality.\\r\\n- **Affected**: The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Background\\r\\n\\r\"\n },\n {\n \"title\": \"feat: pro api support, trending coins api\",\n \"prNumber\": 2068,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n- #1761\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low** - Adding new functionality and API support with proper error handling\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n1. Adds support for CoinGecko Pro API\\r\\n\\r\\n - Configurable through environment \"\n },\n {\n \"title\": \"fix: Bugfix in LetzAI Plugin -> missing named export and Plugin-type\",\n \"prNumber\": 2062,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n0002--feat-letzai-plugin tiny bugfix in the export of the module. Plugin was already merged to dev but \"\n },\n {\n \"title\": \"Galadriel docs and .env.example update\",\n \"prNumber\": 2061,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2011\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - no functional changes\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdd a tutorial on how to use the Galadriel provider.\\r\\nAlso update the `.env.example` to put \"\n },\n {\n \"title\": \"revert: #2048\",\n \"prNumber\": 2059,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2048\\r\\n\\r\\n\\r\\nuntil further review\"\n },\n {\n \"title\": \"Fix: case-sensitive column reference in knowledge table CHECK constraint\",\n \"prNumber\": 2058,\n \"type\": \"bugfix\",\n \"body\": \"Resolves a SQL error (42703: column \\\"isshared\\\" does not exist) in the knowledge table's CHECK constraint. The issue was caused by an incorrect column reference due to PostgreSQL\u2019s case sensitivity when handling column names inside constrain\"\n },\n {\n \"title\": \"feat: solana transaction more lenient\",\n \"prNumber\": 2053,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFixes the Key Derive functionality, by using path for reliable key derivation. Subject is documented and \"\n },\n {\n \"title\": \"chore: add conditionals for supabase to agent directory\",\n \"prNumber\": 2032,\n \"type\": \"feature\",\n \"body\": \"Added Condional for Supabase to the initializeDatabase function to allow for ease of use for Supabase as well as keeping the postgres and sqlite functionality. In conjunction with https://github.com/elizaOS/eliza/pull/2031\\r\\n\\r\\n# Relates to\\r\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 2031,\n \"type\": \"other\",\n \"body\": \"Added Supabase variables. In conjunction with https://github.com/elizaOS/eliza/pull/2032\\r\\n\\r\\n# Relates to\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do? \\r\\nAdds Supabase variables to the .env\\r\\n\\r\\n## What kind of change is t\"\n },\n {\n \"title\": \"fix: include schema.sql and seed.sql in package files\",\n \"prNumber\": 2030,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFixes #2009 - @elizaos/adapter-postgres package does not bundle together schema.sql\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Adding missing SQL files to package bundling. Only affects package distribution, not functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n\"\n },\n {\n \"title\": \"Fix: fix starknet plugin by replacing walletProvider with portfolio provider\",\n \"prNumber\": 2029,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2028\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates\\r\\nto readme.md rus\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEliza currently supports various AI providers but lacks native integration with **nineteen.ai**, which \"\n },\n {\n \"title\": \"fix: letzAi build issues\",\n \"prNumber\": 2021,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- Minor bug fixed.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAuto Client not working.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n-Add client-telegram README.me file\\r\\n-Update comments to \"\n },\n {\n \"title\": \"feat: implement getKnowledge, searchKnowledge, createKnowledge, removeKnowledge and clearKnowledge methods\",\n \"prNumber\": 2005,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update plugins.md -- Allora README Fix\",\n \"prNumber\": 2003,\n \"type\": \"bugfix\",\n \"body\": \"- Fixed a comment-uncomment typo at the end of the Allora Documentation.\\r\\n- Added a link to more comprehensive documentation + examples at the bottom\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n* None, just a chore\\r\\n\\r\\n# Risks\\r\\n\\r\\n* None\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n* Moves README\"\n },\n {\n \"title\": \"test: changing test structure for core package. Fixing failling outdated tests\",\n \"prNumber\": 1989,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1988\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow. Manually tested successfully. Purely additive in nature.\\r\\n\\r\\n# Background\\r\\nThe EVM plugin only had mainnet\"\n },\n {\n \"title\": \"chore: add debug logging for context\",\n \"prNumber\": 1980,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nWhile playing with Eliza and using multiple clients, I noticed that the contexts are often assembled in a mess with many bugs. I want to solve these in my future pull requests, but first, I want to add Eliza, the simple modi\"\n },\n {\n \"title\": \"test: adding tests for twitter plugin\",\n \"prNumber\": 1976,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nChanging project structure, adding tests for twitter plugin in __tests__ directory.\\r\\n# Risks\\r\\nLow: adding\"\n },\n {\n \"title\": \"chore: Cleaner logs on agent startup\",\n \"prNumber\": 1973,\n \"type\": \"refactor\",\n \"body\": \"# Risks\\r\\n\\r\\nLow. Cleans up the logs shown during agent startup.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nCleaning up the logs so that instead of:\\r\\n\\r\\n```\\r\\nSUCCESS\\r\\nSUCCESS\\r\\nCreating runtime for character Eliza\\r\\n```\\r\\n\\r\\nit shows\\r\\n\\r\\n```\\r\\n[\"\n },\n {\n \"title\": \"fix: Fix db init race condition affecting builds\",\n \"prNumber\": 1968,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1914#\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCorrects the info from the auto generated readme for the Abstract plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIntegration of the Anyone Network within the Eliza repository\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot tied to particular issue. Adding tests for twitter client, since \"\n },\n {\n \"title\": \"feat: Add Allora plugin\",\n \"prNumber\": 1955,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n[Allora Network](https://allora.network/) is an AI-powered inference platform that delivers real-time, self-improving predictions and insights for various use cases. By aggregating a\"\n },\n {\n \"title\": \"feat: Add fraxtal chain to evm\",\n \"prNumber\": 1954,\n \"type\": \"feature\",\n \"body\": \"add fraxtal to chains\"\n },\n {\n \"title\": \"fix: fixed error in C3PO and improved error handling feedback\",\n \"prNumber\": 1951,\n \"type\": \"bugfix\",\n \"body\": \"- Resolved an array in the c3po character file where the messageExamples were an object rather an 2D array.\\r\\n- Character validation handling has been improved\\r\\n\\r\\nBefore:\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/2a7fa7c8-d903-4\"\n },\n {\n \"title\": \"fix: Added Local Embedding Manager to reuse Local embed model - Fixes High Ram Issues\",\n \"prNumber\": 1950,\n \"type\": \"bugfix\",\n \"body\": \"# Fixes\\r\\n#1942 #866 #1623\\r\\n\\r\\n# Relates to\\r\\nMemory optimization for character file knowledge processing\\r\\n\\r\\n# Risks\\r\\nLow - This change optimizes the embedding model initialization without changing core functionality.\\r\\n\\r\\n# Background\\r\\n## What \"\n },\n {\n \"title\": \"feat: support for eternalai provider can write request/response log info\",\n \"prNumber\": 1948,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nConfig eternalai logging from env, change name in env for consistent format\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env\\r\\n\\r\\n## Why are we doing this? Any con\"\n },\n {\n \"title\": \"feat: improve twitter paragraph splitting if containing url\",\n \"prNumber\": 1947,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving packages struct\"\n },\n {\n \"title\": \"API route update\",\n \"prNumber\": 1923,\n \"type\": \"other\",\n \"body\": \"Update to the API route\"\n },\n {\n \"title\": \"Fix typo Update CHANGELOG.md\",\n \"prNumber\": 1922,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Typo in CHANGELOG.md\\r\\n\\r\\n## Description:\\r\\n\\r\\nThis pull request fixes a typographical error in the `CHANGELOG.md` file. The word \\\"initital\\\" was corrected to \\\"initial.\\\"\\r\\n\\r\\n## Changes:\\r\\n- Corrected \\\"initital\\\" to \\\"initial\\\" in the `CHANGELOG\"\n },\n {\n \"title\": \"fix: handle empty input text to avoid memory content empty error\",\n \"prNumber\": 1919,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n- #1906 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\ncloses https://github.com/elizaOS/eliza/issues/1901\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes #1448 \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nClosing #1796 in favor of this to avoid conflicts.\\r\\nTEE Plugin and Adding Remote Attestations to be uploade\"\n },\n {\n \"title\": \"Feat: Support wildcard in TWITTER_TARGET_USERS 1883\",\n \"prNumber\": 1884,\n \"type\": \"feature\",\n \"body\": \"# Support wildcard in TWITTER_TARGET_USERS\\r\\n\\r\\nFixes enhancement request #1883 \\r\\n## Summary\\r\\nAdded support for wildcard `*` in `TWITTER_TARGET_USERS` configuration to allow monitoring all users. This change enables broader interaction patter\"\n },\n {\n \"title\": \"feat: Use recommended settings in jupiter swap\",\n \"prNumber\": 1882,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk to introduce regression in jupiter swaps\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUse similar api call as jup.ag to perform swaps with dynamic slippage and dynamic priority fee\\r\\n\\r\\n## W\"\n },\n {\n \"title\": \"Fixed broken API Documentation URL\",\n \"prNumber\": 1881,\n \"type\": \"bugfix\",\n \"body\": \"fixed broken API Documentation in local-development.md\\r\\n\\r\\nit's not a lot, but it's honest work.\"\n },\n {\n \"title\": \"feat: add OpenWeather plugin\",\n \"prNumber\": 1880,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow - This is an additive change that introduces a new plugin without modifying existing functionality. The main risks are:\\r\\n\\r\\n- Rate limiting from OpenWeather API (1000 free API calls per day)\\r\\n- Potential timeout issues when th\"\n },\n {\n \"title\": \"test: adding test setup for telegram client\",\n \"prNumber\": 1879,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving project and fol\"\n },\n {\n \"title\": \"chore(core): enable strict null checks\",\n \"prNumber\": 1878,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nType safety\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: #1809\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: add coin price plugin (CoinMarketCap, CoinGecko & CoinCap)\",\n \"prNumber\": 1808,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#1773 & #1382\\r\\n\\r\\n\\r\\n\\r\\n#\"\n },\n {\n \"title\": \"fix: broken ci docs missed frozen pnpm file out-of-sync\",\n \"prNumber\": 1798,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# \u25c0\ufe0f Relates to:\\r\\n\\r\\nFixes the build related to the pnpm-lock not being in sync from the `docs/` dir\\r\\n\\r\\n# \u26a0\ufe0f Risks\\r\\n\\r\\n* low\"\n },\n {\n \"title\": \"feat: plugin new RabbiTrader\",\n \"prNumber\": 1785,\n \"type\": \"feature\",\n \"body\": \"# Rabbi Trader Plugin\\r\\n\\r\\nAn automated cryptocurrency trading plugin for Solana tokens with integrated trust scoring, market analysis, and Twitter notifications. Built on top of Goat, used actively with: https://x.com/rabbischlomo_ai\\r\\n\\r\\n## F\"\n },\n {\n \"title\": \"feat: Image descriptions into interaction.ts\",\n \"prNumber\": 1775,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to: Irys Plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. README update.\\r\\n\\r\\n\\r\\n# Ba\"\n },\n {\n \"title\": \"Opacity Verifiable Interference zkTLS Plugin\",\n \"prNumber\": 1673,\n \"type\": \"other\",\n \"body\": \"Co-authored @Hmac512 @RonTuretzky @Gajesh2007 \\r\\n## Background\\r\\nA few weeks ago, issues with aixbt were observed, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster \"\n },\n {\n \"title\": \"Add support for Movement Network\",\n \"prNumber\": 1621,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - non-breaking changes made to the Aptos Plugin\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdds support for transacting on Movement Network Testnet and Mainnet\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nNew Pl\"\n },\n {\n \"title\": \"feat: add massa-plugin\",\n \"prNumber\": 1582,\n \"type\": \"feature\",\n \"body\": \"\\r\\n## What does this PR do?\\r\\n\\r\\nAdd Massa plugin with Transfer action\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\n## Screenshots\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/bcb1f\"\n },\n {\n \"title\": \"feat: added new plugin - zktls - reclaim\",\n \"prNumber\": 1558,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\nA few weeks ago, we observed issues with aixbt, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster and raised concerns about the AI\"\n },\n {\n \"title\": \"feat: support TEE logging and support running eliza in Intel SGX\",\n \"prNumber\": 1470,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to: \\r\\nKeywords: TEE, Intel SGX, Logging, Attestation, Verification, Gramine.\\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Make templates in composeContext dynamic\",\n \"prNumber\": 1467,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n