{ "date_generated_for": "2025-01-28", "ai_news_elizaos_discord_md_2025-01-27": { "filename": "2025-01-27.md", "content": "# elizaOS Discord - 2025-01-27\n\n## Overall Discussion Highlights\n\n### ElizaOS Framework & Development\n- **DeepSeek R1 Integration**: The integration of DeepSeek's R1 model into ElizaOS has been completed and is available in the latest development branch. This is seen as a significant improvement for cost efficiency while maintaining quality. Users can configure it via the DEEPSEEK_API_URL in the .env file.\n- **Version Roadmap**: The project is transitioning from v1 to v2, with an intermediate v1.5 release planned that includes plugin rearchitecture. Development teams are working on various components (v1/v2/launchpad/tokenomics/AI traders).\n- **Rebranding Progress**: The project is officially rebranding from ai16z to ElizaOS for a more distinct, unified brand identity. The $ai16z ticker remains for now, with future changes to be voted on by the community when the DAO voting module launches.\n- **Builder Demo Day**: A recent event showcased projects built on the ElizaOS framework, though there was mention of a project called PVPAI that allegedly \"rugged\" shortly after presenting.\n\n### Technical Challenges & Solutions\n- **Solana Plugin Issues**: Many users reported the \"BN not found\" error related to the Solana plugin's dependency on @coral-xyz/anchor. The solution involves modifying node_modules/@solana-developers/helpers/dist/esm/lib/transaction.js to use import pkg syntax.\n- **DeepSeek API Issues**: Users experienced problems with DeepSeek responses containing unwanted text like \"(NONE)\". Solutions include modifying the system prompt or using OpenRouter as an intermediary.\n- **Memory Management**: Discussions about optimizing memory usage with different database options (SQLite, PostgreSQL, Supabase) to prevent context length exceeded errors.\n- **Deployment Options**: Recommendations for VPS providers like Contabo, Docker containers, and cloud services for hosting ElizaOS agents in production.\n\n### Projects & Applications\n- **AI TV Show Development**: A team is developing an AI news show and \"Block Tank\" (similar to Shark Tank) using Unity. Technical implementations include texture loading for TV screens, Oculus LipSync integration, and camera management systems.\n- **DegenAI Trading Bot**: The autonomous trading bot project is facing development delays but is implementing improvements including a new data layer, execution integration to reduce failed transactions, and a sentiment layer similar to aixbt.\n- **Agent Marketplace/Launchpad**: Development of an agent marketplace is in progress with tokenomics documentation nearly complete. The community is eager for its launch to create more utility for the AI16Z token.\n\n### Tokenomics & Market Discussions\n- **Yellowstone Model**: Discussions about implementing the Yellowstone model for AI16Z token utility, where projects would hold tokens to access premium services rather than paying tributes.\n- **Liquidity Concerns**: The AI16Z/SOL liquidity pool has an imbalance ($3M of AI16Z vs only $600K of SOL), creating vulnerability to downward price pressure.\n- **Blockchain Expansion**: Proposals to deploy AI16Z on Base blockchain to increase liquidity and potential for Coinbase listing, following Venice's (VVV) successful launch strategy.\n\n## Key Questions & Answers\n\n**Q: Is DeepSeek R1 supported in ElizaOS?** \nA: Yes, it's already supported in the latest .env file via DEEPSEEK_API_URL. (answered by kingdode)\n\n**Q: How can I use DeepSeek with Eliza?** \nA: Either use DeepSeek directly with proper API configuration or use it through OpenRouter with \"deepseek/deepseek-r1\" model setting. (answered by kAI wilder and ICJR)\n\n**Q: How to fix the \"Named export 'BN' not found\" error from @coral-xyz/anchor?** \nA: Modify node_modules/@solana-developers/helpers/dist/esm/lib/transaction.js to use import pkg syntax instead of direct named imports. (answered by tcm390 and custodian)\n\n**Q: What's the best way to deploy Eliza in production?** \nA: Options include VPS providers like Contabo, Docker containers, and cloud services like AWS. (answered by multiple users)\n\n**Q: How to fix context_length_exceeded errors?** \nA: Reduce the knowledge and topics sections in your character file. (answered by Mr. Stark)\n\n**Q: What's happening with the rebranding from ai16z to ElizaOS?** \nA: The project is rebranding to ElizaOS for a more distinct, unified brand identity that will facilitate partnerships with established players. (answered by jin)\n\n**Q: Will the token ticker change with the rebrand?** \nA: The $ai16z ticker remains for now, with future changes to be voted on by the community when the DAO voting module launches. (answered by jin)\n\n**Q: Did a16z (Andreessen Horowitz) ask ai16z to change its name?** \nA: They politely worked with us rather than pursuing legal action. (answered by jasyn_bjorn)\n\n**Q: Was DegenAI meant to only handle autonomous trading or were other features planned?** \nA: Yes other features are planned. Like any software it's also meant to be flexible, with a roadmap that changes based on user/market desires. (answered by rhota)\n\n## Community Help & Collaboration\n\n- **DeepSeek Integration**: kAI wilder shared a fix for DeepSeek responses containing unwanted text by modifying the system prompt, helping multiple users improve their agent responses.\n\n- **Solana Plugin Fix**: custodian and tcm390 provided a solution for the widespread \"BN not found\" error by modifying the transaction.js file to use CommonJS import syntax, helping numerous users resolve this blocking issue.\n\n- **Memory Management**: ITZMIZZLE helped multiple users experiencing memory errors when using WSL by providing commands to create a swapfile for extra memory.\n\n- **Unity Development**: boom shared complete TextureLoader and TextureLoaderEditor scripts for implementing web image loading in Unity, helping fishai with their implementation for the AI TV show project.\n\n- **Animation System**: PENDINGREALITY suggested using a parent/master actor with child actors that retarget animations at runtime in UE5, helping boom improve the animation architecture for the TV show project.\n\n- **Liquidity Pool Education**: \ud83d\udd25\ud83d\udd25\ud83d\udd25 provided a detailed explanation to Smedroc about how the $3M AI16Z vs $600K SOL liquidity pool imbalance creates asymmetric price impact, helping the community understand market dynamics.\n\n## Action Items\n\n### Technical\n- Fix DeepSeek API integration to handle line breaks and JSON parsing properly (mentioned by kAI wilder)\n- Implement proper memory management for agents to prevent context length exceeded errors (mentioned by joaointech)\n- Create a Docker deployment guide for Eliza (mentioned by Magnacor)\n- Fix the @coral-xyz/anchor import issue in the Solana plugin (mentioned by multiple users)\n- Address liquidity pool imbalance by adding more SOL and wBTC (mentioned by Smedroc)\n- Deploy AI16Z on Base blockchain to increase liquidity and potential for Coinbase listing (mentioned by mat)\n- Create wormhole or interchain liquidity between Base and Solana (mentioned by yikesawjeez)\n- Launch the agent marketplace/launchpad (mentioned by DorianD)\n- Implement TV image loading functionality for AI TV show (mentioned by boom)\n- Integrate Oculus LipSync with ElevenLabs API (mentioned by boom)\n- Implement DeepSeek integration for ElizaOS to reduce costs (mentioned by avirtualfuture)\n- Develop v1.5 with plugin rearchitecture (mentioned by jin)\n\n### Documentation\n- Create a guide for deploying Eliza to cloud services (mentioned by Magnacor)\n- Document how to integrate RSS feeds with Eliza (mentioned by clydedev)\n- Create a guide for running multiple agents simultaneously (mentioned by mike\ud83c\udded\ud83c\uddfa)\n- Document how to use DeepSeek with Eliza properly (mentioned by multiple users)\n- Create a Discord role for bounty hunters to improve coordination (mentioned by jin)\n- Create a list of Discord names + projects + tribute percentages (mentioned by jin)\n- Consolidate tokenomics mechanisms into documentation (mentioned by jin)\n- Improve communication of project structure (mentioned by bong49)\n- Create a news aggregator for DAO-relevant information (mentioned by jin)\n- Create documentation for current code implementation of AI TV show (mentioned by boom)\n\n### Features\n- Add support for responding to Twitter direct messages (mentioned by Sergey Danilovich)\n- Implement scheduling capabilities for agents to perform actions at specific times (mentioned by [elizaos] <_uwotm8>)\n- Add support for image posting on Twitter (mentioned by allensapp)\n- Implement a bounty structure similar to Eigen Layer's for hackathons (mentioned by Kenk)\n- Develop podcast audio transcription plugin using Whisper (mentioned by nullfoxgiven)\n- Create news and social aggregator for personalized daily information (mentioned by nullfoxgiven)\n- Implement new data layer & trading execution integration for DegenAI (mentioned by rhota)\n- Add sentiment layer to identify trending tokens similar to aixbt (mentioned by rhota)\n- Implement Yellowstone model for premium services requiring projects to hold AI16Z tokens (mentioned by Akin)\n- Create a pro tier with additional services for projects holding more tokens (mentioned by Akin)\n- Implement NSFW agent capabilities using Venice's image generation API (mentioned by Patt)\n- Add pupil tracking for characters in AI TV show (mentioned by boom)\n- Add more character animations for AI TV show (mentioned by boom)\n- Implement global illumination from TV in Unity (mentioned by boom)" }, "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_daily_json_2025-01-27": { "filename": "2025-01-27.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-01-27", "categories": [ { "title": "Eliza Project Updates: New Plugins, Bugfixes, and Testing Improvements", "content": [ { "text": "## New Features and Plugins\n\nThe Eliza project has added several new plugins and features:\n\n- A new plugin for the Zilliqa blockchain (#2842)\n- Telegram account client integration (#2839)\n- MultiversX Plugin with Access Token Management (#2810)\n- Gelato plugin relay (#2799)\n- BTC Fun Plugin (#2797)\n- APRO plugin support (#2794)\n- XMTP Client (#2786)\n- Arbitrage plugin with example character (#2784)\n- Trikon plugin (#2653)\n- Deva client integration (#1238)\n- Twitter media posting capability (#2818)\n- New model provider for LM Studio (#2913)\n- Public access to packages (#2933)", "sources": [ "https://github.com/elizaOS/eliza/pull/2842", "https://github.com/elizaOS/eliza/pull/2839", "https://github.com/elizaOS/eliza/pull/2810", "https://github.com/elizaOS/eliza/pull/2799", "https://github.com/elizaOS/eliza/pull/2797", "https://github.com/elizaOS/eliza/pull/2794", "https://github.com/elizaOS/eliza/pull/2786", "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/2913", "https://github.com/elizaOS/eliza/pull/2933" ], "images": [], "videos": [] }, { "text": "## Bug Fixes\n\nNumerous bug fixes have been implemented across various plugins and components:\n\n- Updated bs58 version to resolve integration test dependency issues (#2848)\n- Simplified and fixed exports in Imgflip meme generation plugin (#2846)\n- Fixed issues in multiple plugins including Story, Sui, Suno, Akash splash, TEE-Marlin, TEE-Verifiable-Log, ThirdWeb, TON, TTS, Twitter, Udio, Video-Generation, Zerion, ZkSync-Era, Arbitrage, Omniflix, Opacity, Open-Weather, OpenAI, Primus, Quai, Quick-Intel, Sei, SGX, Spheron, Squid-Router, and Starknet\n- Updated cookie dependency to v0.7.0 for security (#2834)\n- Fixed Farcaster client loop to continue running even after errors (#2830)\n- Fixed NVIDIA NIM environment (#2817)\n- Fixed JSON parsing bug with single quotes (#2802)\n- Fixed client server port (#2886)\n- Fixed LOG_JSON_FORMAT environment variable setting (#2881)\n- Changed default character from OpenAI to LlamaLocal (#2880)", "sources": [ "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/2837", "https://github.com/elizaOS/eliza/pull/2836", "https://github.com/elizaOS/eliza/pull/2834", "https://github.com/elizaOS/eliza/pull/2833", "https://github.com/elizaOS/eliza/pull/2832", "https://github.com/elizaOS/eliza/pull/2830", "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/2817", "https://github.com/elizaOS/eliza/pull/2802", "https://github.com/elizaOS/eliza/pull/2886", "https://github.com/elizaOS/eliza/pull/2881", "https://github.com/elizaOS/eliza/pull/2880", "https://github.com/elizaOS/eliza/pull/2905", "https://github.com/elizaOS/eliza/pull/2902", "https://github.com/elizaOS/eliza/pull/2900", "https://github.com/elizaOS/eliza/pull/2899", "https://github.com/elizaOS/eliza/pull/2898", "https://github.com/elizaOS/eliza/pull/2893", "https://github.com/elizaOS/eliza/pull/2892", "https://github.com/elizaOS/eliza/pull/2890", "https://github.com/elizaOS/eliza/pull/2877", "https://github.com/elizaOS/eliza/pull/2872", "https://github.com/elizaOS/eliza/pull/2870", "https://github.com/elizaOS/eliza/pull/2868", "https://github.com/elizaOS/eliza/pull/2866" ], "images": [], "videos": [] }, { "text": "## Testing Improvements\n\nTest coverage and configuration have been enhanced for several plugins:\n\n- Added test configuration and coverage for plugin-anyone (#2854)\n- Added test configuration and coverage for plugin-3d generation (#2850)\n- Added test configuration and coverage for plugin-0x (#2807)\n- Added test configuration and coverage for plugin-0g (#2805)\n- Added test configuration and coverage for plugin-asterai (#2860)", "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/2860" ], "images": [], "videos": [] }, { "text": "## Documentation and Other Updates\n\n- Added new READMEs and moved others for consistency (#2828)\n- Updated embedding function documentation (#2821)\n- Updated client-telegram README.md (#2814)\n- Created client-discord readme.md (#2812)\n- Added exclusion for extra folder for faster future rebase (#2813)\n- Updated pnpm to v9.15.0 for security (#2888)\n- Updated systeminformation dependency to v5.23.8 for security (#2887)\n- Bumped version to 0.1.9 (#2883)\n- Fixed inconsistent folder naming convention (#2931)\n- Fixed invalid npm package naming convention (#2930)\n- Fixed missing version property in package.json (#2929)\n- Made changes to allow package scoping to public (#2928)\n- Fixed spelling errors (#2909)\n- Updated LICENSE (#2903)", "sources": [ "https://github.com/elizaOS/eliza/pull/2828", "https://github.com/elizaOS/eliza/pull/2821", "https://github.com/elizaOS/eliza/pull/2814", "https://github.com/elizaOS/eliza/pull/2812", "https://github.com/elizaOS/eliza/pull/2813", "https://github.com/elizaOS/eliza/pull/2888", "https://github.com/elizaOS/eliza/pull/2887", "https://github.com/elizaOS/eliza/pull/2883", "https://github.com/elizaOS/eliza/pull/2931", "https://github.com/elizaOS/eliza/pull/2930", "https://github.com/elizaOS/eliza/pull/2929", "https://github.com/elizaOS/eliza/pull/2928", "https://github.com/elizaOS/eliza/pull/2909", "https://github.com/elizaOS/eliza/pull/2903" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Open Source AI and Crypto Developments", "content": [ { "text": "Open source AI is gaining momentum with DeepSeek models making waves in the AI community. The release of these models has sparked optimism about the future of open source AI, with users noting how it feels to use DeepSeek models with Eliza. This development is seen as a win for open source technology in general.", "sources": "https://twitter.com/dankvr/status/1883900392628752427, https://twitter.com/dankvr/status/1883935328593129832", "images": "https://pbs.twimg.com/ext_tw_video_thumb/1883899121838202880/pu/img/MnHre3DyvjMqvkR1.jpg", "videos": "https://video.twimg.com/ext_tw_video/1883899121838202880/pu/vid/avc1/1280x720/Efn5FUD3nYF9Tozj.mp4?tag=12" }, { "text": "The impact of DeepSeek's advancements is significant for the AI ecosystem. As noted by Shaw, DeepSeek's success is making VCs more willing to invest in smaller labs, potentially leading to hundreds of new labs getting funded. This is particularly bullish for teams who have been developing AI solutions and are about to have their moment.", "sources": "https://twitter.com/shawmakesmagic/status/1884002809382924784", "images": "", "videos": "" }, { "text": "There's a strong sentiment that open source AI improvements benefit everyone in the ecosystem. As models get better and cheaper, AI products and agents become smarter at no additional cost. The trend shows AI labs leapfrogging each other in capabilities, with DeepSeek currently leading the pack.", "sources": "https://twitter.com/shawmakesmagic/status/1883831555392770470, https://twitter.com/shawmakesmagic/status/1883704494879559789", "images": "", "videos": "" }, { "text": "The intersection of AI and crypto is highlighted with mentions of collaborative training of open source models coordinated on Solana. There's enthusiasm about DAOs, open source, AI, and crypto working together, with calls for more people from big AI companies to join this 'wild west' ecosystem.", "sources": "https://twitter.com/shawmakesmagic/status/1884011621988851862, https://twitter.com/dankvr/status/1883692238884254096", "images": "", "videos": "" }, { "text": "AI16z DAO is mentioned as a 'hyperbolic time chamber' where teams are 'eating their own dog food' while speed running development stages. There's also discussion about tools like Dework, described as a blend of GitHub, Discord, Trello with bounties that make it easy to attach crypto to tasks.", "sources": "https://twitter.com/dankvr/status/1883694865466433922, https://twitter.com/dankvr/status/1883706963336556932", "images": "https://pbs.twimg.com/media/GiQ5jvGXgAAYSYG.png", "videos": "" }, { "text": "The sentiment toward market fluctuations remains positive with statements like 'Nice shakeout, Not selling' and questions about why AI advancements would negatively impact crypto AI space when it's 'unbelievably bullish.' There's also excitement about 'Season 2' beginning, suggesting a new phase in the AI/crypto landscape.", "sources": "https://twitter.com/dankvr/status/1883696911141711915, https://twitter.com/shawmakesmagic/status/1883830918357692486, https://twitter.com/shawmakesmagic/status/1883676926008778941", "images": "https://pbs.twimg.com/media/GiQ8QkgXIAAwKJX.jpg, https://pbs.twimg.com/ext_tw_video_thumb/1883674060850376704/pu/img/z7ZrMzV1O1cxTz92.jpg", "videos": "https://video.twimg.com/ext_tw_video/1883674060850376704/pu/vid/avc1/1280x720/TAqCm2A4xNXHauxy.mp4?tag=12" } ], "topic": "tweet" }, { "title": "Recent Issues in the elizaOS/eliza GitHub Repository", "content": [ { "text": "The elizaOS/eliza GitHub repository has several open issues related to plugins, functionality, and technical problems:\n\n1. Plugin Development Issues:\n - Issue #2851: Request to publish plugin-sui\n - Issue #2859: plugin-asterai needs test configuration and improved test coverage\n - Issue #2815: Integration with node-llama-cpp\n\n2. Feature Requests:\n - Issue #2856: A feature to collect information from Telegram groups or Discord channels\n - Issue #2918: Proposal to consolidate RAG Knowledge into a unified Knowledge system (marked as V2)\n\n3. Technical Problems:\n - Issue #2864: Btcfun crash reported\n - Issue #2885: Eliza chatbot client not running on localhost:5173\n - Issue #2871: Error after updating to the latest version\n - Issue #2891: Second tweet from agent incorrectly replies to user instead of initial agent tweet\n - Issue #2914: ragKnowledge functionality causing problems by retrieving entire documents, which bloats the prompt", "sources": [ "https://github.com/elizaOS/eliza/issues/2851", "https://github.com/elizaOS/eliza/issues/2864", "https://github.com/elizaOS/eliza/issues/2856", "https://github.com/elizaOS/eliza/issues/2815", "https://github.com/elizaOS/eliza/issues/2859", "https://github.com/elizaOS/eliza/issues/2885", "https://github.com/elizaOS/eliza/issues/2891", "https://github.com/elizaOS/eliza/issues/2871", "https://github.com/elizaOS/eliza/issues/2918", "https://github.com/elizaOS/eliza/issues/2914" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2851", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2864", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2856", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2815", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2859", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2885", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2891", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2871", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2918", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2914" ], "videos": [] } ], "topic": "issue" }, { "title": "Recent Pull Requests to the Eliza Framework", "content": [ { "text": "The Eliza framework has seen several new plugin integrations and feature additions through recent pull requests. These contributions expand Eliza's capabilities across various domains:\n\n- A new Storyteller feature (PR #2831) has been proposed by Mettulus\n- AIFlowML added Hyperliquid plugin integration with WebSocket support (PR #1497)\n- Julian-dev28 contributed an OKX DEX integration (PR #2865)\n- An arbitrage plugin with example character was added by mmarfinetz (PR #2784)\n- Lit Protocol plugin was introduced by madschristensen99 (PR #2912)\n- Tarnadas developed an Orderly Network plugin (PR #2925)\n- A draft PR for model refactoring was submitted by lalalune (PR #2910)\n- Aman-14 integrated Hash Network Plugin for verifiable inference (PR #2894)\n- General Eliza updates were contributed by magacek (PR #2874)\n\nThese contributions demonstrate the active development of the Eliza framework, with a particular focus on expanding its plugin ecosystem for various blockchain, DeFi, and AI-related functionalities.", "sources": [ "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", "https://github.com/elizaOS/eliza/pull/2912", "https://github.com/elizaOS/eliza/pull/2925", "https://github.com/elizaOS/eliza/pull/2910", "https://github.com/elizaOS/eliza/pull/2894", "https://github.com/elizaOS/eliza/pull/2874" ], "images": [ "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", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2912", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2925", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2910", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2894", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2874" ], "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 27-28, 2025, there were 39 new pull requests with 42 merged, 11 new issues created, and 40 active contributors. Activity increased the following day (January 28-29, 2025) with 50 new pull requests, 37 merged pull requests, 15 new issues, and 44 active contributors. Overall, the project maintained strong development momentum with consistent contributor engagement.", "sources": [ "From 2025-01-27 to 2025-01-28, elizaos/eliza had 39 new PRs (42 merged), 11 new issues, and 40 active contributors.", "From 2025-01-28 to 2025-01-29, elizaos/eliza had 50 new PRs (37 merged), 15 new issues, and 44 active contributors." ], "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 or their contributions to the project. Without additional information, it's not possible to generate a detailed summary about the individual contributors, their roles, or the nature of their contributions to the elizaOS/eliza project.", "sources": [ "Top contributors for elizaOS/eliza" ], "images": [], "videos": [] } ], "topic": "contributors" } ], "date": 1737936000 } }, "ai_news_elizaos_daily_md_2025-01-27": { "filename": "2025-01-27.md", "content": "# Eliza Project Updates: New Plugins, Bugfixes, and Testing Improvements\n\n## New Features and Plugins\n\nThe Eliza project has added several new plugins and features:\n\n- A new plugin for the Zilliqa blockchain\n- Telegram account client integration\n- MultiversX Plugin with Access Token Management\n- Gelato plugin relay\n- BTC Fun Plugin\n- APRO plugin support\n- XMTP Client\n- Arbitrage plugin with example character\n- Trikon plugin\n- Deva client integration\n- Twitter media posting capability\n- New model provider for LM Studio\n- Public access to packages\n\n## Bug Fixes\n\nNumerous bug fixes have been implemented across various plugins and components:\n\n- Updated bs58 version to resolve integration test dependency issues\n- Simplified and fixed exports in Imgflip meme generation plugin\n- Fixed issues in multiple plugins including Story, Sui, Suno, Akash splash, and many others\n- Updated cookie dependency to v0.7.0 for security\n- Fixed Farcaster client loop to continue running even after errors\n- Fixed NVIDIA NIM environment\n- Fixed JSON parsing bug with single quotes\n- Fixed client server port\n- Fixed LOG_JSON_FORMAT environment variable setting\n- Changed default character from OpenAI to LlamaLocal\n\n## Testing Improvements\n\nTest coverage and configuration have been enhanced for several plugins:\n\n- Added test configuration and coverage for plugin-anyone\n- Added test configuration and coverage for plugin-3d generation\n- Added test configuration and coverage for plugin-0x\n- Added test configuration and coverage for plugin-0g\n- Added test configuration and coverage for plugin-asterai\n\n## Documentation and Other Updates\n\n- Added new READMEs and moved others for consistency\n- Updated embedding function documentation\n- Updated client-telegram README.md\n- Created client-discord readme.md\n- Added exclusion for extra folder for faster future rebase\n- Updated pnpm to v9.15.0 for security\n- Updated systeminformation dependency to v5.23.8 for security\n- Bumped version to 0.1.9\n- Fixed inconsistent folder naming convention\n- Fixed invalid npm package naming convention\n- Fixed missing version property in package.json\n- Made changes to allow package scoping to public\n- Fixed spelling errors\n- Updated LICENSE\n\n# Open Source AI and Crypto Developments\n\n- DeepSeek models are making waves in the AI community, sparking optimism about the future of open source AI\n- DeepSeek's success is making VCs more willing to invest in smaller labs, potentially leading to hundreds of new labs getting funded\n- Open source AI improvements benefit everyone in the ecosystem as models get better and cheaper\n- AI labs are leapfrogging each other in capabilities, with DeepSeek currently leading\n- Collaborative training of open source models is being coordinated on Solana\n- AI16z DAO is described as a 'hyperbolic time chamber' where teams are rapidly developing\n- Tools like Dework (a blend of GitHub, Discord, Trello with bounties) make it easy to attach crypto to tasks\n- Positive sentiment toward market fluctuations with statements like \"Nice shakeout, Not selling\"\n- Excitement about \"Season 2\" beginning, suggesting a new phase in the AI/crypto landscape\n\n# Recent Issues in the elizaOS/eliza GitHub Repository\n\n## Plugin Development Issues\n- Request to publish plugin-sui\n- plugin-asterai needs test configuration and improved test coverage\n- Integration with node-llama-cpp\n\n## Feature Requests\n- A feature to collect information from Telegram groups or Discord channels\n- Proposal to consolidate RAG Knowledge into a unified Knowledge system\n\n## Technical Problems\n- Btcfun crash reported\n- Eliza chatbot client not running on localhost:5173\n- Error after updating to the latest version\n- Second tweet from agent incorrectly replies to user instead of initial agent tweet\n- ragKnowledge functionality causing problems by retrieving entire documents\n\n# Recent Pull Requests to the Eliza Framework\n\nThe Eliza framework has seen several new plugin integrations and feature additions:\n\n- A new Storyteller feature proposed by Mettulus\n- AIFlowML added Hyperliquid plugin integration with WebSocket support\n- Julian-dev28 contributed an OKX DEX integration\n- An arbitrage plugin with example character was added by mmarfinetz\n- Lit Protocol plugin was introduced by madschristensen99\n- Tarnadas developed an Orderly Network plugin\n- A draft PR for model refactoring was submitted by lalalune\n- Aman-14 integrated Hash Network Plugin for verifiable inference\n- General Eliza updates were contributed by magacek\n\n# ElizaOS GitHub Activity Update\n\nThe elizaos/eliza repository showed significant activity:\n\n- January 27-28, 2025: 39 new pull requests with 42 merged, 11 new issues created, and 40 active contributors\n- January 28-29, 2025: 50 new pull requests, 37 merged pull requests, 15 new issues, and 44 active contributors\n- Overall, the project maintained strong development momentum with consistent contributor engagement" }, "ai_news_elizaos_daily_discord_json_2025-01-27": { "filename": "2025-01-27.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-01-27", "date": 1737936000, "stats": { "totalMessages": 3811, "totalUsers": 365 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe discussion channel primarily revolves around ElizaOS, an open-source framework for building AI agents, and related tokens (AI16Z and DegenAI). Users frequently ask about technical aspects of ElizaOS, including model integration, deployment options, and upcoming features. There's significant discussion about using DeepSeek's R1 model with ElizaOS, which appears to be supported in the latest development branch. The chat reveals that ElizaOS can work with various LLM backends to reduce operational costs. A Builder Demo Day was announced featuring projects built on the ElizaOS framework. Users also discussed token performance and upcoming features like an \"agent launchpad.\" BOSSU, an AI assistant in the channel, redirects technical questions to appropriate channels while maintaining a lighthearted presence. There was also mention of a project called PVPAI that allegedly \"rugged\" (abandoned after taking funds) shortly after presenting at a demo event.\n\n## 2. FAQ\nQ: Is DeepSeek R1 supported in ElizaOS? (asked by Vex) A: Yes, it's already supported in the latest .env file via DEEPSEEK_API_URL (answered by kingdode)\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: What's the difference between a traditional trading bot and Eliza Agent doing it? (asked by bartjh) A: Eliza runs on love and vibes, regular bots just do math (answered by BOSSU)\nQ: How to deploy an agent to fly.io? (asked by TovarishFin) A: AWS or DigitalOcean will work fine, deployment is straightforward once you get the basics (answered by BOSSU)\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 there a scheduled release cycle for ElizaOS? (asked by tmarwen) A: New builds drop when they're ready (answered by BOSSU)\nQ: What happened to the trenches channel? (asked by ooeygg) A: Trenches have been murdered (answered by frank)\nQ: Is launchpad related to metav? (asked by jojp) A: Unanswered\nQ: Is the ai16z token going to be used for the future launchpad or will there be a new one? (asked by Atexela_) A: No new token (answered by kingdode)\nQ: When will the launchpad be launched? (asked by Atexela_) A: Soon (answered by BOSSU)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Sarthak | Context: User was having errors with the develop branch | Resolution: Jin suggested errors are opportunities to learn/fix/improve/earn and directed to coders channel\nHelper: [[{{,,,}}]] | Helpee: claimzilla | Context: How to use DeepSeek with Eliza | Resolution: Advised to set it in the env and call the plugin\nHelper: BOSSU | Helpee: Josh \u2600 | Context: Errors using CUDA GPU accelerator through llama to run agent | Resolution: Directed to coders channel for GPU-specific help\nHelper: BOSSU | Helpee: Notsef | Context: User kept getting kicked from server despite verifying | Resolution: Suggested re-verifying and directed to support channel\nHelper: witch | Helpee: D.Morpheus | Context: User comparing token performance with misaligned charts | Resolution: Witch aligned the charts to provide accurate comparison\nHelper: SotoAlt | BOSSU | Helpee: bersezk | Context: Explaining how DeepSeek integration benefits AI16z | Resolution: Explained it makes agents more cost-efficient\n\n## 4. Action Items\nTechnical: Integrate DeepSeek R1 model with ElizaOS for more cost-efficient agent operation | Mentioned By: bersezk\nTechnical: Fix verification system that's causing some users to be kicked despite verifying | Mentioned By: Notsef\nTechnical: Update CMC links which are currently outdated | Mentioned By: TOD\nTechnical: Investigate and fix errors in the develop branch | Mentioned By: Sarthak\nTechnical: Provide documentation on deploying agents to production environments | Mentioned By: TovarishFin\nFeature: Launch the agent launchpad with buybacks | Mentioned By: frank\nFeature: Implement DeepSeek plugin for AI16z codebase | Mentioned By: bersezk\nDocumentation: Create guide for using DeepSeek with ElizaOS | Mentioned By: claimzilla\nDocumentation: Update documentation on how to use different local models | Mentioned By: claimzilla\nDocumentation: Create deployment guides for hosting ElizaOS agents | Mentioned By: TovarishFin", "messageCount": 478, "userCount": 147 }, { "channelId": "1300025221834739744", "channelName": "\ud83d\udcbb-coders", "summary": "# Analysis of Discord Chat in \"\ud83d\udcbb-coders\" Channel\n\n## 1. Summary\nThe discussion primarily revolves around technical issues with the Eliza AI agent framework. Users are experiencing various deployment and configuration challenges. A recurring issue is the \"BN not found\" error related to the Solana plugin's dependency on @coral-xyz/anchor. Many users report problems with the DeepSeek AI model, which appears to be experiencing API issues. Several workarounds are shared, including using OpenRouter as an intermediary for DeepSeek or switching to Anthropic's Claude. There are discussions about hosting options, with recommendations for VPS providers like Contabo. Users also discuss memory management with different database options (SQLite, PostgreSQL, Supabase). The chat reveals ongoing development with new pull requests for features like WhatsApp integration and arbitrage plugins. Docker deployment is mentioned as a solution for dependency issues, though some users report challenges with it.\n\n## 2. FAQ\nQ: How to fix the \"Named export 'BN' not found\" error from @coral-xyz/anchor? (asked by multiple users) A: Modify node_modules/@solana-developers/helpers/dist/esm/lib/transaction.js to use import pkg syntax instead of direct named imports (answered by tcm390 and custodian)\nQ: How to use DeepSeek with Eliza? (asked by multiple users) A: Either use DeepSeek directly with proper API configuration or use it through OpenRouter with \"deepseek/deepseek-r1\" model setting (answered by kAI wilder and ICJR)\nQ: What's the best way to deploy Eliza in production? (asked by zadkielm and others) A: Options include VPS providers like Contabo, Docker containers, and cloud services like AWS (answered by multiple users)\nQ: How to fix Twitter login failures? (asked by multiple users) A: Ensure your IP matches previous login locations, set up email in configuration, and possibly disable 2FA (answered by Silasneo)\nQ: How to make an agent post autonomously on Twitter? (asked by 0xMAR$H) A: Configure POST_INTERVAL_MIN, POST_INTERVAL_MAX, and ENABLE_ACTION_PROCESSING in the .env file (answered by allensapp)\nQ: How to integrate RSS feeds with Eliza? (asked by clydedev) A: Unanswered\nQ: How to handle vector dimension mismatch errors? (asked by Magicred1) A: Switch to PostgreSQL with Supabase to store the cache instead of SQLite (answered by Magicred1)\nQ: How to run multiple agents simultaneously? (asked by mike\ud83c\udded\ud83c\uddfa) A: Unanswered\nQ: How to make an agent respond to specific tweets? (asked by KubaRozruba) A: Use TWITTER_TARGET_USERS in the .env file (answered by elizaos-bridge-odi)\nQ: How to fix context_length_exceeded errors? (asked by joaointech) A: Reduce the knowledge and topics sections in your character file (answered by Mr. Stark)\n\n## 3. Help Interactions\nHelper: tenshin4860 | Helpee: C-Money-Dev | Context: Unable to clone and run a specific version of Eliza | Resolution: Provided git commands to fetch a specific commit\nHelper: tcm390 | Helpee: RoomTemp IQ | Context: DeepSeek model not working with Twitter image recognition | Resolution: Suggested adding \"imageVisionModelProvider\" in character file\nHelper: custodian | Helpee: RoomTemp IQ | Context: Solana plugin causing errors with @coral-xyz/anchor imports | Resolution: Provided a fix by modifying the transaction.js file to use CommonJS import syntax\nHelper: elizaos-bridge-odi | Helpee: mystic | Context: WSL2 setup for Llama with CUDA | Resolution: Provided configuration for Ollama with proper environment variables\nHelper: Gal | Helpee: C-Money-Dev | Context: BN import error from @coral-xyz/anchor | Resolution: Suggested adding @types/bn.js dependency\nHelper: ITZMIZZLE | Helpee: multiple users | Context: Memory errors when using WSL | Resolution: Provided commands to create a swapfile for extra memory\nHelper: kAI wilder | Helpee: multiple users | Context: DeepSeek responses containing (NONE) and other unwanted text | Resolution: Shared a fix by modifying the system prompt\nHelper: Hiram | Helpee: C-Money-Dev | Context: Lockfile issues | Resolution: Provided commands to remove node_modules and lock files\n\n## 4. Action Items\nType: Technical | Description: Fix DeepSeek API integration to handle line breaks and JSON parsing properly | Mentioned By: kAI wilder\nType: Technical | Description: Implement proper memory management for agents to prevent context length exceeded errors | Mentioned By: joaointech\nType: Technical | Description: Create a Docker deployment guide for Eliza | Mentioned By: Magnacor\nType: Technical | Description: Fix the @coral-xyz/anchor import issue in the Solana plugin | Mentioned By: multiple users\nType: Technical | Description: Implement a solution for Twitter login issues from different IP addresses | Mentioned By: Silasneo\nType: Feature | Description: Add support for responding to Twitter direct messages | Mentioned By: Sergey Danilovich\nType: Feature | Description: Implement scheduling capabilities for agents to perform actions at specific times | Mentioned By: [elizaos] <_uwotm8>\nType: Feature | Description: Add support for image posting on Twitter | Mentioned By: allensapp\nType: Documentation | Description: Create a guide for deploying Eliza to cloud services | Mentioned By: Magnacor\nType: Documentation | Description: Document how to integrate RSS feeds with Eliza | Mentioned By: clydedev\nType: Documentation | Description: Create a guide for running multiple agents simultaneously | Mentioned By: mike\ud83c\udded\ud83c\uddfa\nType: Documentation | Description: Document how to use DeepSeek with Eliza properly | Mentioned By: multiple users", "messageCount": 1745, "userCount": 161 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "# Analysis of \"ideas-feedback-rants\" Discord Channel\n\n## 1. Summary\nThe channel contains minimal substantive technical discussion. Users are primarily seeking connections, sharing resources, and proposing ideas rather than engaging in deep technical problem-solving. Key points include: a GitHub repository for ElizaOS workgroups was shared; a user inquired about creating a swarm module; someone shared a video example with \"futuristic, hopeful\" vibes for a TV Show team; a suggestion to implement a bounty structure similar to Eigen Layer's for hackathons; and a user mentioned building a podcast transcription tool using Whisper that could potentially be developed as an Eliza plugin. There's also interest in news aggregation capabilities and ZKP implementation on Solana.\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 GitHub repository? (asked by Pranav) A: Unanswered\nQ: How to contract with eliza core commiter wtfsayo? (asked by shaka) A: Unanswered\nQ: Does anyone have any experience with ZKPs on SOL? (asked by Zardique) A: Unanswered\n\n## 3. Help Interactions\nHelper: DorianD | Helpee: Unknown | Context: User needed to connect with someone specific | Resolution: DorianD directed them to another user via mention\nHelper: Space_air.o | Helpee: Unknown user (968830394508115980) | Context: User needed guidance | Resolution: Directed them to check dashboard for sent guide\nHelper: Random Disco | Helpee: Unknown | Context: Shared example video for TV Show team with specific aesthetic direction | Resolution: Provided visual reference and expressed willingness to collaborate\n\n## 4. Action Items\nFeature: Implement a bounty structure similar to Eigen Layer's for hackathons to incentivize ElizaOS usage | Description: Reward anyone using ElizaOS at hackathons to capture mindshare at crypto conferences | Mentioned By: Kenk\nFeature: Podcast audio transcription plugin using Whisper | Description: Tool that monitors podcast RSS feeds, transcribes and summarizes new episodes with optimizations for file size and usage fees | Mentioned By: nullfoxgiven\nFeature: News and social aggregator for personalized daily information | Description: Monitor relevant information from various spaces and provide daily summaries | Mentioned By: nullfoxgiven", "messageCount": 14, "userCount": 10 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Analysis of \"spartan_holders\" Discord Channel\n\n## 1. Summary\nThe discussion centers around DegenAI, an autonomous trading bot project facing development delays and community frustration. Project manager rhota explains that DegenAI's development has been slowed by resource allocation issues and the need to align with the broader ai16z ecosystem. The team is currently implementing trading improvements with a new data layer and execution integration that will reduce failed transactions. A sentiment layer similar to aixbt is being added to help DegenAI identify trending tokens. The team is also working on improving DegenAI's Twitter presence to make posts more contextual and in-character. A high-level roadmap is being prepared for community review. Community members express concerns about slow development pace, lack of marketing, and shifting priorities away from the original autonomous trading vision. Some suggest DegenAI should be more active on social media like other AI trading bots (aixbt, MOBY) to increase visibility and mindshare.\n\n## 2. FAQ\nQ: Was DegenAI meant to only handle autonomous trading or were other features planned? (asked by tigerguo.) A: Yes other features are planned. Like any software it's also meant to be flexible, with a 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: This will pick up as we continue to roll out improvements. (answered by rhota)\nQ: When is DegenAI going to get his own potato servers? (asked by DorianD) A: Unanswered\nQ: Is Skyle still leading the development of degenai? (asked by mmbig) A: Unanswered\nQ: What trading strategies would you like to see? (asked by rhota) A: Unanswered\n\n## 3. Help Interactions\nHelper: cool.eth | Helpee: tigerguo. | Context: User asking about project leadership and updates | Resolution: Directed user to where they can get latest news and who to tag for progress updates\n\n## 4. Action Items\nType: Technical | Description: Implement new data layer & trading execution integration to reduce failed transactions | Mentioned By: rhota\nType: Technical | Description: Add sentiment layer to identify trending tokens similar to aixbt | Mentioned By: rhota\nType: Technical | Description: Improve Twitter posting to reduce duplicates and make posts more contextual | Mentioned By: rhota\nType: Documentation | Description: Deliver high-level roadmap to community by end of week | Mentioned By: rhota\nType: Feature | Description: Enable DegenAI to interact with other agents in Telegram/Discord | Mentioned By: rhota\nType: Feature | Description: Create a Telegram bot for DegenAI that provides token information | Mentioned By: NZD_Aaron\u0f3c \u3064 \u25d5_\u25d5 \u0f3d\u3064\nType: Feature | Description: Implement take profit/stop loss and Fibonacci trading strategies | Mentioned By: rhota", "messageCount": 49, "userCount": 14 }, { "channelId": "1328592959444095038", "channelName": "associates", "summary": "# Analysis of \"associates\" Discord Channel\n\n## 1. Summary:\nThe chat primarily revolves around market conditions affecting AI16Z and DegenAI tokens, with discussions about strategy during a market downturn. Members express concern about token price, liquidity issues, and resource allocation. A key technical issue identified is the imbalanced liquidity pool composition ($3M of AI16Z vs only $600K of SOL), creating vulnerability to downward price pressure. There's discussion about Venice's image generation API integration with Eliza for NSFW capabilities. Members debate whether to focus resources exclusively on AI16Z or maintain support for DegenAI. The community also discusses the need for better coordination mechanisms for bounty hunters and contributors, with suggestions for Discord role implementation to facilitate faster communication during critical periods.\n\n## 2. FAQ:\nQ: What about holder of degenai? Leave them to dead? (asked by Wilcox) A: Unanswered\nQ: Any thoughts on venice that just had their TGE? (asked by smetter) A: \"I think its up bc tokenomics are good and they mentioned Deep Seek\" (answered by GujuViper)\n\n## 3. Help Interactions:\nHelper: \ud83d\udd25\ud83d\udd25\ud83d\udd25 | Helpee: Smedroc - Street urchin @ ai16z | Context: Explaining liquidity pool imbalance issues | Resolution: Detailed explanation of how $3M AI16Z vs $600K SOL creates asymmetric price impact\nHelper: jin | Helpee: Community | Context: Need for better coordination with contributors | Resolution: Proposed creating a Discord role system for bounty hunters and past contributors\n\n## 4. Action Items:\nType: Technical | Description: Address liquidity pool imbalance by adding more SOL and wBTC | Mentioned By: Smedroc - Street urchin @ ai16z\nType: Technical | Description: Create a Discord role for bounty hunters to improve coordination | Mentioned By: jin\nType: Documentation | Description: Create a list of Discord names + projects + tribute percentages | Mentioned By: jin\nType: Feature | Description: Implement NSFW agent capabilities using Venice's image generation API | Mentioned By: Patt\nType: Documentation | Description: Write/generate an article explaining how DeepSeek is bullish for open source AI | Mentioned By: smetter", "messageCount": 62, "userCount": 11 }, { "channelId": "1318770424632311930", "channelName": "tokenomics", "summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion primarily focused on token utility strategies and platform expansion. Key topics included:\n\n- Implementing the Yellowstone model for AI16Z token utility, where projects would hold tokens to access premium services rather than paying tributes\n- Debate about the agent marketplace/launchpad development status and go-to-market strategy\n- Discussion about expanding to Base blockchain to increase liquidity and potential for Coinbase listing\n- Comparison with Venice (VVV) which successfully launched on Base and demonstrated strong metrics (400k users, 50k DAU)\n- Concerns about token visibility on daos.fun and the need for better representation of LP positions\n- Debate about free vs. paid agent creation, with consensus that basic agent creation should remain free\n- Discussion of token sink mechanisms to improve tokenomics and create buy pressure\n\nThe conversation revealed tension between focusing on quick revenue generation versus building sustainable value. There was agreement on the need for the launchpad to launch soon, with jin confirming it was in progress with tokenomics documentation nearly complete.\n\n## 2. FAQ\nQ: Is it possible for a project that sent 10% of tokens to the DAO to get an $ai16z/$GODS liquidity position? (asked by Robin) A: jin indicated it's being discussed with the daos.fun team about integrating LP solutions.\nQ: What is the Yellowstone model? (asked by DorianD) A: Akin shared a link to the model, explaining it's a framework that can be leveraged for compute or other services.\nQ: Any update on the dev for the \"agent market\"? (asked by DorianD) A: jin mentioned seeing work in progress that \"looked really good\" with tokenomics documentation nearly complete.\nQ: When will the official rebrand happen? (asked by DannyNOR NoFapArc) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: Robin | Context: Robin asked about visibility of token allocations to the DAO on daos.fun and LP program participation | Resolution: jin acknowledged the issue and committed to discussing with daos.fun team about integrating LP solutions.\nHelper: Akin | Helpee: DorianD | Context: DorianD didn't understand the Yellowstone model | Resolution: Akin shared links and explanations about the model, though the conversation became contentious.\n\n## 4. Action Items\nTechnical: Deploy AI16Z on Base blockchain to increase liquidity and potential for Coinbase listing | Mentioned By: mat\nTechnical: Create wormhole or interchain liquidity between Base and Solana | Mentioned By: yikesawjeez\nTechnical: Launch the agent marketplace/launchpad | Mentioned By: DorianD\nFeature: Implement Yellowstone model for premium services requiring projects to hold AI16Z tokens | Mentioned By: Akin\nFeature: Create a pro tier with additional services for projects holding more tokens | Mentioned By: Akin\nFeature: Create a new AUM leaderboard website to show LP positions | Mentioned By: jin\nDocumentation: Create clear tokenomics documentation for the agent marketplace | Mentioned By: jin", "messageCount": 108, "userCount": 10 }, { "channelId": "1301363808421543988", "channelName": "\ud83e\udd47-partners", "summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around discussions about ai16z/ElizaOS rebranding, communication strategies, and market conditions. Key technical discussions include:\n\nThe integration of DeepSeek, an open-source LLM, into the ElizaOS framework. This was merged two weeks prior to public awareness, with developers already using it. The community views this as a positive development for open-source AI, potentially reducing costs while maintaining quality.\n\nThe team is working on consolidating tokenomics mechanisms into documentation, a dedicated repository, and updates. There's ongoing development of a news aggregator for automated information gathering, with plans to filter based on DAO interests.\n\nThe project is transitioning from v1 to v2, with an intermediate v1.5 release planned that will include plugin rearchitecture. The team has structured development teams working on various components (v1/v2/launchpad/tokenomics/AI traders).\n\nPartners expressed concerns about communication strategies, with suggestions to improve how announcements are structured and disseminated. The team acknowledged these concerns and indicated they're working on a more cohesive communication strategy.\n\nThe project has secured partnerships, including being featured on Solana's AI page, though some partners felt this wasn't adequately communicated.\n\n## 2. FAQ\nQ: Is DeepSeek integrated into ElizaOS? (asked by ricky) A: Yes, it's integrated already and has been for two weeks. (answered by shaw)\nQ: What's happening with the rebranding from ai16z to ElizaOS? (asked by bong49) A: The project is rebranding to ElizaOS for a more distinct, unified brand identity that will facilitate partnerships with established players. (answered by jin)\nQ: Will the token ticker change with the rebrand? (asked by Burtiik) A: The $ai16z ticker remains for now, with future changes to be voted on by the community when the DAO voting module launches. (answered by jin)\nQ: Is DegenAI still getting included in the new tokenomics models? (asked by nezaalex) A: Yes, it always has been. (answered 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)\nQ: Did a16z (Andreessen Horowitz) ask ai16z to change its name? (asked by litn) A: They politely worked with us rather than pursuing legal action. (answered by jasyn_bjorn)\nQ: When will the rebrand officially happen? (asked by DannyNOR NoFapArc) A: Shaw will stream later to discuss it. (answered by jin)\nQ: How will the ElizaOS Twitter account and the ai16zdao account be managed after rebranding? (asked by Avanc) A: They will be consolidated, waiting for X to respond about handle transfer. (answered by jin)\nQ: Is there a Venice integration? (asked by Akin) A: Yes, we have Venice integration. (answered by shaw)\n\n## 3. Help Interactions\nHelper: jin | Helpee: pragmatiko | Context: Improving communication strategy for the project | Resolution: Jin offered to discuss comms strategy and share current plans, suggesting a one-to-many form of communication to address as many people as possible.\nHelper: DorianD | Helpee: hildi | Context: Concerns about using Charlie Brown character in promotional material | Resolution: DorianD shared information about the character being in the public domain.\nHelper: m1hawk/\u98ce\u7b54 | Helpee: jin | Context: How to wish happy Chinese New Year | Resolution: Provided traditional Chinese greetings \"\u606d\u559c\u53d1\u8d22\" (wish you rich) and \"\u86c7\u5e74\u5927\u5409\" (wish you lucky in the year of snake).\nHelper: jin | Helpee: Community | Context: Explaining the structure of the organization | Resolution: Clarified that there are dedicated teams working on different aspects of the project with decent runway from OTC deals.\nHelper: jasyn_bjorn | Helpee: renameless | Context: Question about token contract ownership and ability to change ticker | Resolution: Explained that metadata can be updated without migration using SPL token 2022.\n\n## 4. Action Items\nTechnical: Implement DeepSeek integration for ElizaOS to reduce costs | Description: Test and optimize DeepSeek for the framework | Mentioned By: avirtualfuture\nTechnical: Develop v1.5 with plugin rearchitecture | Description: Create an intermediate release before v2 with improved plugin structure | Mentioned By: jin\nTechnical: Streamline finetuning DeepSeek for Eliza | Description: Make the process of creating finetunes easier | Mentioned By: avirtualfuture\nDocumentation: Consolidate tokenomics mechanisms into documentation | Description: Create dedicated repo and updates for tokenomics | Mentioned By: jin\nDocumentation: Improve communication of project structure | Description: Better explain the teams and roles within the organization | Mentioned By: bong49\nDocumentation: Create a news aggregator for DAO-relevant information | Description: Filter news based on DAO interests | Mentioned By: jin\nFeature: Implement a voting system for the DAO | Description: Allow community to vote on changes like token ticker | Mentioned By: renameless\nFeature: Develop a more cohesive brand identity | Description: Unify colors, communications channels, and brand voice | Mentioned By: pragmatiko\nFeature: Create a calendar for coordinated communications | Description: Schedule announcements to avoid missing major things | Mentioned By: pragmatiko\nFeature: Establish a comms strategy for major announcements | Description: Prepare partners and create graphics for important news | Mentioned By: pragmatiko", "messageCount": 1068, "userCount": 66 }, { "channelId": "1313222089271939102", "channelName": "3d-ai-tv", "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe channel discussions focus on developing a TV show system with AI-driven characters. The team is working on two main projects: an AI news show and \"Block Tank\" (similar to Shark Tank). Key technical developments include:\n\n- Implementation of a texture loader for displaying images on a TV screen within Unity, using UnityWebRequest to fetch and apply textures to emission channels\n- Integration of Oculus LipSync plugin for lip synchronization with audio from ElevenLabs API\n- Discussion of camera management for scenes with TV displays, including how to handle camera positioning when showing both anchors and media content\n- Development of a news aggregator that provides daily JSON data for the show content\n- Debate about JSON structure for the news data, with suggestions to rename \"text\" nodes to \"categories\" or \"topic\"\n- Implementation of animation systems including IK (Inverse Kinematics) for character movement\n- Exploration of video media loading options, with AVPro being expensive ($900) and the team looking for open-source alternatives\n- Discussion of a multi-agent writers room system for generating show content, with SM Sith Lord seeking someone with AI expertise to help implement it\n\nThe team is balancing immediate implementation needs with planning for scale and maintainability.\n\n## 2. FAQ\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: How are you loading up the video atlas for the stonks? (asked by boom) A: Unanswered\nQ: Do you have any simple solutions on how to get an emotion response from a set list with each returned response in Eliza? (asked by PENDINGREALITY) A: I would just tell it to assign one of the emotions to each reply, and then list out the available emotions. Depending on how \"disagreeable\" the personality is, it should usually work. (answered by SM Sith Lord)\n\n## 3. Help Interactions\nHelper: boom | Helpee: fishai | Context: Sharing texture loader code for loading web images into Unity | Resolution: Provided complete TextureLoader and TextureLoaderEditor scripts for implementation\nHelper: boom | Helpee: PENDINGREALITY | Context: How to handle emotion responses in character dialogue | Resolution: Explained the current system using action/emotion tags in dialogue JSON that get parsed into animations\nHelper: PENDINGREALITY | Helpee: boom | Context: Animation system architecture advice | Resolution: Suggested using a parent/master actor with child actors that retarget animations at runtime in UE5\nHelper: SM Sith Lord | Helpee: boom | Context: Camera positioning for TV display | Resolution: Suggested using the presence of an image as a modifier for camera selection, or positioning the graphic between anchors\n\n## 4. Action Items\nTechnical: Implement TV image loading functionality | Description: Create system to display images on TV screen in Unity | Mentioned By: boom\nTechnical: Integrate Oculus LipSync with ElevenLabs API | Description: Connect lip sync to audio from ElevenLabs while keeping show event stream synced | Mentioned By: boom\nTechnical: Refactor animation code for better maintainability | Description: Create an \"Uber ultimate rig\" with all animations to make adding new characters easier | Mentioned By: boom\nTechnical: Find open-source video plugins for Unity | Description: Need alternative to expensive AVPro ($900) for loading video media | Mentioned By: boom\nTechnical: Implement camera management for TV display | Description: Create system to handle camera positioning when showing both anchors and media content | Mentioned By: boom\nTechnical: Create multi-agent writers room | Description: Develop system for generating show content with multiple AI agents | Mentioned By: SM Sith Lord\nDocumentation: Create documentation for current code implementation | Description: Record and transcribe what the current system does | Mentioned By: boom\nFeature: Add pupil tracking for characters | Description: Implement eye movement for models that have eye bones | Mentioned By: boom\nFeature: Add more character animations | Description: Expand the animation library for characters | Mentioned By: boom\nFeature: Implement global illumination from TV | Description: Add realtime lighting effects from the TV display | Mentioned By: boom", "messageCount": 287, "userCount": 10 } ] } }, "ai_news_elizaos_daily_discord_md_2025-01-27": { "filename": "2025-01-27.md", "content": "# elizaOS Discord - 2025-01-27\n\n## Overall Discussion Highlights\n\n### ElizaOS Framework & Development\n- **DeepSeek R1 Integration**: The integration of DeepSeek's R1 model into ElizaOS has been completed and is available in the latest development branch. This is seen as a significant improvement for cost efficiency while maintaining quality. Users can configure it via the DEEPSEEK_API_URL in the .env file.\n- **Version Roadmap**: The project is transitioning from v1 to v2, with an intermediate v1.5 release planned that includes plugin rearchitecture. Development teams are working on various components (v1/v2/launchpad/tokenomics/AI traders).\n- **Rebranding Progress**: The project is officially rebranding from ai16z to ElizaOS for a more distinct, unified brand identity. The $ai16z ticker remains for now, with future changes to be voted on by the community when the DAO voting module launches.\n- **Builder Demo Day**: A recent event showcased projects built on the ElizaOS framework, though there was mention of a project called PVPAI that allegedly \"rugged\" shortly after presenting.\n\n### Technical Challenges & Solutions\n- **Solana Plugin Issues**: Many users reported the \"BN not found\" error related to the Solana plugin's dependency on @coral-xyz/anchor. The solution involves modifying node_modules/@solana-developers/helpers/dist/esm/lib/transaction.js to use import pkg syntax.\n- **DeepSeek API Issues**: Users experienced problems with DeepSeek responses containing unwanted text like \"(NONE)\". Solutions include modifying the system prompt or using OpenRouter as an intermediary.\n- **Memory Management**: Discussions about optimizing memory usage with different database options (SQLite, PostgreSQL, Supabase) to prevent context length exceeded errors.\n- **Deployment Options**: Recommendations for VPS providers like Contabo, Docker containers, and cloud services for hosting ElizaOS agents in production.\n\n### Projects & Applications\n- **AI TV Show Development**: A team is developing an AI news show and \"Block Tank\" (similar to Shark Tank) using Unity. Technical implementations include texture loading for TV screens, Oculus LipSync integration, and camera management systems.\n- **DegenAI Trading Bot**: The autonomous trading bot project is facing development delays but is implementing improvements including a new data layer, execution integration to reduce failed transactions, and a sentiment layer similar to aixbt.\n- **Agent Marketplace/Launchpad**: Development of an agent marketplace is in progress with tokenomics documentation nearly complete. The community is eager for its launch to create more utility for the AI16Z token.\n\n### Tokenomics & Market Discussions\n- **Yellowstone Model**: Discussions about implementing the Yellowstone model for AI16Z token utility, where projects would hold tokens to access premium services rather than paying tributes.\n- **Liquidity Concerns**: The AI16Z/SOL liquidity pool has an imbalance ($3M of AI16Z vs only $600K of SOL), creating vulnerability to downward price pressure.\n- **Blockchain Expansion**: Proposals to deploy AI16Z on Base blockchain to increase liquidity and potential for Coinbase listing, following Venice's (VVV) successful launch strategy.\n\n## Key Questions & Answers\n\n**Q: Is DeepSeek R1 supported in ElizaOS?** \nA: Yes, it's already supported in the latest .env file via DEEPSEEK_API_URL. (answered by kingdode)\n\n**Q: How can I use DeepSeek with Eliza?** \nA: Either use DeepSeek directly with proper API configuration or use it through OpenRouter with \"deepseek/deepseek-r1\" model setting. (answered by kAI wilder and ICJR)\n\n**Q: How to fix the \"Named export 'BN' not found\" error from @coral-xyz/anchor?** \nA: Modify node_modules/@solana-developers/helpers/dist/esm/lib/transaction.js to use import pkg syntax instead of direct named imports. (answered by tcm390 and custodian)\n\n**Q: What's the best way to deploy Eliza in production?** \nA: Options include VPS providers like Contabo, Docker containers, and cloud services like AWS. (answered by multiple users)\n\n**Q: How to fix context_length_exceeded errors?** \nA: Reduce the knowledge and topics sections in your character file. (answered by Mr. Stark)\n\n**Q: What's happening with the rebranding from ai16z to ElizaOS?** \nA: The project is rebranding to ElizaOS for a more distinct, unified brand identity that will facilitate partnerships with established players. (answered by jin)\n\n**Q: Will the token ticker change with the rebrand?** \nA: The $ai16z ticker remains for now, with future changes to be voted on by the community when the DAO voting module launches. (answered by jin)\n\n**Q: Did a16z (Andreessen Horowitz) ask ai16z to change its name?** \nA: They politely worked with us rather than pursuing legal action. (answered by jasyn_bjorn)\n\n**Q: Was DegenAI meant to only handle autonomous trading or were other features planned?** \nA: Yes other features are planned. Like any software it's also meant to be flexible, with a roadmap that changes based on user/market desires. (answered by rhota)\n\n## Community Help & Collaboration\n\n- **DeepSeek Integration**: kAI wilder shared a fix for DeepSeek responses containing unwanted text by modifying the system prompt, helping multiple users improve their agent responses.\n\n- **Solana Plugin Fix**: custodian and tcm390 provided a solution for the widespread \"BN not found\" error by modifying the transaction.js file to use CommonJS import syntax, helping numerous users resolve this blocking issue.\n\n- **Memory Management**: ITZMIZZLE helped multiple users experiencing memory errors when using WSL by providing commands to create a swapfile for extra memory.\n\n- **Unity Development**: boom shared complete TextureLoader and TextureLoaderEditor scripts for implementing web image loading in Unity, helping fishai with their implementation for the AI TV show project.\n\n- **Animation System**: PENDINGREALITY suggested using a parent/master actor with child actors that retarget animations at runtime in UE5, helping boom improve the animation architecture for the TV show project.\n\n- **Liquidity Pool Education**: \ud83d\udd25\ud83d\udd25\ud83d\udd25 provided a detailed explanation to Smedroc about how the $3M AI16Z vs $600K SOL liquidity pool imbalance creates asymmetric price impact, helping the community understand market dynamics.\n\n## Action Items\n\n### Technical\n- Fix DeepSeek API integration to handle line breaks and JSON parsing properly (mentioned by kAI wilder)\n- Implement proper memory management for agents to prevent context length exceeded errors (mentioned by joaointech)\n- Create a Docker deployment guide for Eliza (mentioned by Magnacor)\n- Fix the @coral-xyz/anchor import issue in the Solana plugin (mentioned by multiple users)\n- Address liquidity pool imbalance by adding more SOL and wBTC (mentioned by Smedroc)\n- Deploy AI16Z on Base blockchain to increase liquidity and potential for Coinbase listing (mentioned by mat)\n- Create wormhole or interchain liquidity between Base and Solana (mentioned by yikesawjeez)\n- Launch the agent marketplace/launchpad (mentioned by DorianD)\n- Implement TV image loading functionality for AI TV show (mentioned by boom)\n- Integrate Oculus LipSync with ElevenLabs API (mentioned by boom)\n- Implement DeepSeek integration for ElizaOS to reduce costs (mentioned by avirtualfuture)\n- Develop v1.5 with plugin rearchitecture (mentioned by jin)\n\n### Documentation\n- Create a guide for deploying Eliza to cloud services (mentioned by Magnacor)\n- Document how to integrate RSS feeds with Eliza (mentioned by clydedev)\n- Create a guide for running multiple agents simultaneously (mentioned by mike\ud83c\udded\ud83c\uddfa)\n- Document how to use DeepSeek with Eliza properly (mentioned by multiple users)\n- Create a Discord role for bounty hunters to improve coordination (mentioned by jin)\n- Create a list of Discord names + projects + tribute percentages (mentioned by jin)\n- Consolidate tokenomics mechanisms into documentation (mentioned by jin)\n- Improve communication of project structure (mentioned by bong49)\n- Create a news aggregator for DAO-relevant information (mentioned by jin)\n- Create documentation for current code implementation of AI TV show (mentioned by boom)\n\n### Features\n- Add support for responding to Twitter direct messages (mentioned by Sergey Danilovich)\n- Implement scheduling capabilities for agents to perform actions at specific times (mentioned by [elizaos] <_uwotm8>)\n- Add support for image posting on Twitter (mentioned by allensapp)\n- Implement a bounty structure similar to Eigen Layer's for hackathons (mentioned by Kenk)\n- Develop podcast audio transcription plugin using Whisper (mentioned by nullfoxgiven)\n- Create news and social aggregator for personalized daily information (mentioned by nullfoxgiven)\n- Implement new data layer & trading execution integration for DegenAI (mentioned by rhota)\n- Add sentiment layer to identify trending tokens similar to aixbt (mentioned by rhota)\n- Implement Yellowstone model for premium services requiring projects to hold AI16Z tokens (mentioned by Akin)\n- Create a pro tier with additional services for projects holding more tokens (mentioned by Akin)\n- Implement NSFW agent capabilities using Venice's image generation API (mentioned by Patt)\n- Add pupil tracking for characters in AI TV show (mentioned by boom)\n- Add more character animations for AI TV show (mentioned by boom)\n- Implement global illumination from TV in Unity (mentioned by boom)" }, "github_summaries_daily_2025-01-28": { "filename": "2025-01-28.md", "content": "# ElizaOS Daily Update (Jan 28, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the ElizaOS framework with new features, bug fixes, and optimizations. Significant improvements were made to package accessibility, model provider integration, and various plugins. The team also addressed several issues related to typing and functionality across multiple components, ensuring a more robust and reliable system.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Introduced public access to packages, allowing non-private packages to be published to the npm registry ([#2933](https://github.com/elizaos/eliza/pull/2933)).\n- Added a new model provider for LM Studio, enhancing the framework's capabilities ([#2913](https://github.com/elizaos/eliza/pull/2913)).\n- Improved gas price optimization and volume calculation in the arbitrage plugin, building on previous updates ([#2869](https://github.com/elizaos/eliza/pull/2869)).\n- Enhanced tweet scraping functionality by adding more data during the process ([#2644](https://github.com/elizaos/eliza/pull/2644)).\n\n### Bug Fixes\n- Resolved multiple issues related to package naming conventions and missing properties in `package.json` ([#2930](https://github.com/elizaos/eliza/pull/2930), [#2929](https://github.com/elizaos/eliza/pull/2929)).\n- Fixed various typing errors and logical issues across several plugins, including `plugin-openai`, `plugin-omniflix`, and `plugin-arbitrage` ([#2898](https://github.com/elizaos/eliza/pull/2898), [#2902](https://github.com/elizaos/eliza/pull/2902), [#2905](https://github.com/elizaos/eliza/pull/2905)).\n- Corrected minor template typos and spelling errors in documentation ([#2932](https://github.com/elizaos/eliza/pull/2932), [#2909](https://github.com/elizaos/eliza/pull/2909)).\n\n### Code Quality Improvements\n- Addressed multiple linting issues across various plugins, improving code quality and maintainability ([#2868](https://github.com/elizaos/eliza/pull/2868), [#2866](https://github.com/elizaos/eliza/pull/2866)).\n- Updated dependencies for security enhancements, including `pnpm` and `systeminformation` ([#2888](https://github.com/elizaos/eliza/pull/2888), [#2887](https://github.com/elizaos/eliza/pull/2887)).\n\n## CLOSED ISSUES\n\n### Resolved Bugs\n- Fixed the issue with the `SEND_TOKEN` action verification in the `plugin-solana`, ensuring proper functionality ([#2920](https://github.com/elizaos/eliza/issues/2920)).\n- Addressed the problem of the Eliza chatbot client not running on specific ports, improving accessibility ([#2726](https://github.com/elizaos/eliza/issues/2726)).\n- Resolved the issue with the plugin-asterai lacking test coverage, enhancing reliability ([#2859](https://github.com/elizaos/eliza/issues/2859)).\n\n## NEW ISSUES\n\n### Feature Requests and Bugs\n- A request to implement Reranked Contextual Embedding as the default RAG implementation, aiming for improved contextual retrieval ([#2919](https://github.com/elizaos/eliza/issues/2919)).\n- Identified a bug where the template tag `{{maxTweetLength}}` does not exist in the tweet post template, requiring attention ([#2927](https://github.com/elizaos/eliza/issues/2927)).\n- Reported issues with the `facts` functionality not working correctly due to message count limitations ([#2915](https://github.com/elizaos/eliza/issues/2915))." }, "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