{
"date_generated_for": "2025-01-16",
"ai_news_elizaos_discord_md_2025-01-15": {
"filename": "2025-01-15.md",
"content": "# elizaOS Discord - 2025-01-15\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **ElizaOS v2 Development**: Shaw mentioned pushing a basic v2 that is still \"bare bones\" but represents progress toward the next generation of the framework.\n- **Agent Development Challenges**: Users discussed various implementation issues including embedding errors, plugin integration problems, Twitter client configuration, and database management.\n- **Knowledge Management**: Significant discussion about RAG (Retrieval Augmented Generation) implementation, with users struggling to understand how knowledge is stored, retrieved, and utilized by agents.\n- **Docker Deployment**: Several users reported issues with Docker builds across different environments (Mac, Windows, Linux), particularly on ARM64 architecture.\n- **Installation Issues**: Multiple users experienced problems with the @discord/opus dependency during installation, requiring workarounds.\n\n### Plugins & Integrations\n- **Twitter Integration**: Extensive troubleshooting of Twitter client issues, particularly with authentication, reply functionality, and rate limiting.\n- **Blockchain Data**: Discussion of plugins for accessing on-chain data, including plugin-evm and the Chainbase plugin for natural language querying of blockchain data.\n- **GitHub Integration**: Proposals for creating a GitHub client plugin for ElizaOS.\n- **Multimodal Generation**: Integration of BEATS SDK for multimodal generation, starting with AI-generated music.\n- **Robot Integration**: A partnership was announced for ElizaOS to be integrated into physical robots, with preorders at $420k.\n\n### AI Music Generation\n- **Suno Experimentation**: Dr. Neuro and boom explored AI music generation using Suno, sharing prompts and techniques for creating multi-voice rap songs with different personas.\n- **Prompt Engineering**: Discussion of strategies like adding \"AI\" to artist names to bypass copyright restrictions and creating structured prompts with defined roles for each voice.\n- **Integration Possibilities**: Exploration of integration between Eleven Labs voice profiles and Suno for multi-voice AI music generation.\n\n### Tokenomics & Business Model\n- **Revenue Sharing Model**: Shaw proposed moving beyond just a launchpad model to focus on revenue sharing mechanisms where projects contribute 10% of revenue to buy ai16z tokens, creating buy pressure.\n- **Market Making**: Detailed discussion about Principal Market Makers (PMMs) and Designated Market Makers (DMMs) for token launches, including loan structures and engagement terms.\n- **Token Utility**: Debate about the relationship between ai16z and DegenAI tokens, with some arguing for equal benefits while others suggested prioritizing ai16z.\n- **DeFAI Ecosystem**: Interest in the growing Decentralized Finance AI ecosystem, with discussions about metrics for measuring adoption and market growth.\n\n### Community & Branding\n- **Rebranding Efforts**: Discussions about changing the ticker symbol and server name, with jin implementing some changes during the conversation.\n- **New Logo**: Jin initiated a bounty for community members to update stickers and emojis with the new \"taped hat\" logo.\n- **Newsletter Creation**: Proposals for establishing a community newsletter, with MicoM.ron sharing templates and offering to help organize this effort.\n- **Documentation**: Jin created a bounty for maintaining and updating the \"awesome-eliza\" GitHub repository, which serves as a curated list of Eliza framework resources.\n\n### Project Showcase\n- **Block Tank/Crypto Shark Tank**: SM Sith Lord is developing a Shark Tank-style show where AI judges evaluate pitches, using PlayCanvas with a fully automated pipeline that generates episodes within 10 seconds of submission.\n- **Trading Bots**: Several users discussed developing autonomous trading agents with wallet security features.\n- **Social Media Agents**: Multiple implementations of Twitter-integrated agents were shared and discussed.\n\n## Key Questions & Answers\n\n### Technical Questions\n- **Q**: Do you need a good PC to run more complex AI agents? \n **A**: Depends on what you're building but any decent laptop can handle most agents (BOSSU)\n\n- **Q**: How to integrate an agent into Twitter? \n **A**: Check out agent dev school on YouTube and hit the coders channel for Twitter integration help (BOSSU)\n\n- **Q**: Do I need to know how to code to create my own AI agent on Eliza OS? \n **A**: Yes and no. Depends what you want to do with it (Dragonbutt)\n\n- **Q**: Where can I host Eliza? \n **A**: For hosting Eliza check out AWS or DigitalOcean, head to coders channel for more tech details (BOSSU)\n\n- **Q**: How can I make my agent access onchain data? \n **A**: Use plugins like plugin-evm or GOAT plugin (adonisabril)\n\n- **Q**: How can I fix the \"Cannot generate embedding: Memory content is empty\" error? \n **A**: Clear your cache and database file, ensure OpenAI embeddings are configured (Simz)\n\n- **Q**: How do I structure knowledge for effective RAG implementation? \n **A**: Break knowledge into concise lines with specific keywords for embedding (MonteCrypto)\n\n### Tokenomics Questions\n- **Q**: What are the token thresholds for different roles? \n **A**: For ai16z: 100k for partner role, 10k for associate; For degenai: 1,000,000 for Partner role, 100,000 for hoplite role (liveinthemoment)\n\n- **Q**: Is there a benefit from holding 10,000 AI16Z? \n **A**: 10k ai16z tokens lets you see in some of the partner(100k ai16z tokens) chat but you can't type or react (Dragonbutt)\n\n- **Q**: How can we reward teams who already donated 10% to treasury? \n **A**: We can work something out to reward them as they buy-and-send-to-dao AI16Z tokens, creating steady buy pressure without dumping (shaw)\n\n- **Q**: Why is asking for 10% not really a lot? \n **A**: Because there are ongoing maintenance and support costs that big organizations understand (DorianD)\n\n- **Q**: Is aixvc (formerly pmairca) getting its own token? \n **A**: aixvc will use ai16z as its token (shakejr)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Helper**: MonteCrypto | **Helpee**: 0xLabsTheCoder \n **Context**: Understanding how knowledge and RAG work in Eliza \n **Resolution**: Explained that knowledge should be fragmented into short, concise lines with unique keywords for effective embedding and retrieval\n\n- **Helper**: Simz | **Helpee**: tony \n **Context**: Fixing \"Cannot generate embedding: Memory content is empty\" error \n **Resolution**: Suggested clearing cache and database files, and ensuring OpenAI embeddings are properly configured\n\n- **Helper**: zadkielm | **Helpee**: 0xChainBrain \n **Context**: Finding REST API endpoint for direct agent communication \n **Resolution**: Pointed to lib/api.ts where the endpoint is defined\n\n- **Helper**: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f | **Helpee**: Jessy | Unicake\ud83e\udd84 \n **Context**: EVM private key format \n **Resolution**: Suggested including 0x prefix in the private key\n\n- **Helper**: Neil Jones | **Helpee**: 0xLisanAlGaib \n **Context**: Fixing better-sqlite3 Node.js version mismatch \n **Resolution**: Provided commands to rebuild better-sqlite3 or reinstall requirements\n\n### Community Building\n- **Helper**: jin | **Helpee**: Smore \n **Context**: Creating a document to track ai16z lore and history \n **Resolution**: Jin provided a hackmd.io template and Smore added content about the project's history\n\n- **Helper**: jin | **Helpee**: zocktay \n **Context**: Explaining how to use the tip bot for tipping contributors \n **Resolution**: Jin demonstrated the command and zocktay successfully tipped jin\n\n- **Helper**: Burtiik | **Helpee**: multiple partners \n **Context**: Sharing the hat overlay tool for profile pictures \n **Resolution**: Shared the link to eliza.gg/hat for partners to add hats to their profile pictures\n\n- **Helper**: Dr. Neuro | **Helpee**: boom \n **Context**: Creating multi-voice AI rap songs in Suno \n **Resolution**: Shared technique of adding \"AI\" to artist names to bypass copyright restrictions and using structured prompts with defined roles\n\n## Action Items\n\n### Technical\n- Fix embedding errors when using different embedding models with Supabase (NoBody | SUIRISE)\n- Implement proper error handling for Twitter client (GOGOGO\u26d3\ud83d\udca5)\n- Fix evaluator validation logic - evaluators don't trigger unless alwaysRun is set to true (bifkn)\n- Fix Docker build issues on ARM64 architecture (Tobias | QDEV)\n- Fix installation issues with @discord/opus dependency (jeremyboise)\n- Create an AI bounty agent to scan approved PRs and attribute Discord roles based on coding effort (MonteCrypto)\n- Fix JSON structure in Howieduhzit tool to properly create arrays of strings (Dreygo)\n- Integrate Chainbase plugin for natural language querying of blockchain data (Lil Lowkey | Chainbase)\n- Integrate BEATS SDK for multimodal generation (starting with songs) (ryoh)\n- Implement revenue sharing mechanisms for projects building on ElizaOS (shaw)\n- Develop V2 of ElizaOS (shaw)\n- Fix Elizas.world data pipeline (timshel)\n- Integrate technical analysis module into Neuro runtime (anomalyagentic)\n- Combine sentiment analysis from Twitter with technical analysis for trading signals (anomalyagentic)\n- Explore integration between Eleven Labs voice profiles and Suno (boom)\n- Develop a system for providing market maker services to partner projects (yikesawjeez)\n- Create a mechanism for projects to buy-and-send-to-DAO AI16Z tokens (shaw)\n- Implement on-chain liquidity provision in exchange for call options (yikesawjeez)\n\n### Documentation\n- Create weekly newsletters to prevent announcements from getting lost (jin)\n- Document tokenomics and token utility mechanisms (Burtiik)\n- Add details about target users configuration (SMA)\n- Improve plugin development documentation (MonteCrypto)\n- Update EVM private key format requirements (Jessy | Unicake\ud83e\udd84)\n- Create guide for knowledge structuring (0xLabsTheCoder)\n- Create a document listing major lore events in ai16z history (jin)\n- Update tokenomics documentation with revenue sharing model (jin)\n- Create a clear standard operating procedure for potential partners (st4rgard3n)\n- Complete and release the Tokenomics document (\ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create a public webpage showing metrics about partners, associates, and token holders (MicoM.ron)\n- White Paper and Tokenomics documentation needed for DegenSpartan (NkT)\n\n### Features\n- Add ability for AI agents to search and post on Reddit (uniqueobject)\n- Create an agent for autonomous trading with wallet security (kobra)\n- Develop AI agent for improving and backtesting TradingView scripts (FutureStocks)\n- Implement local TTS option as alternative to ElevenLabs (Abderahman)\n- Create GitHub client plugin for ElizaOS (suso)\n- Implement multi-agent interaction system (0xLabsTheCoder)\n- Add API for direct agent communication (0xChainBrain)\n- Develop wallet protection mechanism (kobra)\n- Create global/shared memories system (matthias_ztlr)\n- Improve Twitter client reply functionality (PhyoPhyoLay)\n- Create a cloud-based test bed for AI agents (Hidden Forces)\n- Develop AI beatmaker assistant for real-time music production (boom)\n- Explore capability for Eliza to create 3D objects in Blender (judasz)\n- Implement NFT project for DegenAI (shaw)\n- Integrate ElizaOS with robots (anon)\n- Develop trust score system using ai16z tokens (DorianD)\n- Create a community website to display partner projects (MonteCrypto)\n- Create a curation system for the project listing website (MonteCrypto and 0xMatt)\n- Implement automated weekly updates from agents (jin)"
},
"ai_news_elizaos_discord_md_2025-01-14": {
"filename": "2025-01-14.md",
"content": "# elizaOS Discord - 2025-01-14\n\n## Overall Discussion Highlights\n\n### ElizaOS Rebranding and Ecosystem Development\n- **Rebranding from ai16z to ElizaOS**: The project is rebranding due to trademark concerns with a16z (Andreessen Horowitz). Shaw explained they need to change the name to avoid legal issues and to enable partnerships with a16z.\n- **Token Ticker Discussions**: Community debated various ticker options, with constraints like X's 6-character limit for cashtags. Shaw mentioned voting on the ticker will be enabled in 1-2 months.\n- **Partnership Strategy**: Shaw proposed a model where projects donate 10% of their tokens to the treasury in exchange for benefits, creating steady buy pressure without causing token dumps.\n- **Value Accrual Mechanisms**: The DAO will generate value through revenue sharing (10% of partner project revenue), trading fees, and potentially LP positions.\n- **Marketplace Development**: A marketplace/launchpad for ElizaOS projects is being developed with fee structures and support services.\n\n### Technical Development\n- **ElizaOS V2**: Shaw mentioned they're pushing basic V2 code, though it's still in early stages.\n- **One-Click Deployment**: Mike D. shared progress on a Terraform-based deployment solution for Eliza, targeting AWS t4g.small instances to leverage the free tier.\n- **Docker Image Builds**: The team is working on Docker images with a new architecture that required porting NPM modules.\n- **Sims 4 Integration**: The Oracle team is making progress on integrating Eliza into Sims 4.\n- **Neuro Runtime Enhancements**: The Neuro team announced plans to integrate technical analysis and Twitter fact extraction modules, enabling sentiment analysis and trading signals generation.\n\n### AI Agent Development\n- **Twitter Integration Issues**: Users discussed controlling agent responses, preventing spam replies, and handling authentication. Common problems included agents responding too frequently or inappropriately to mentions.\n- **Knowledge Management**: Extensive discussions about RAG (Retrieval-Augmented Generation) implementation, with users trying to understand how to structure knowledge for effective retrieval.\n- **Plugin Development**: Users asked about creating custom actions and using existing plugins like web-search, evm (Ethereum Virtual Machine), and Coinbase/Goat for cryptocurrency operations.\n- **DeFAI Agents**: Several members discussed Decentralized Finance AI agents, with Display Name noting market cap growth in this sector.\n\n### 3D AI Shows Development\n- **Three Main Projects**: (1) ai16z AI Podcast - GitHub/news updates summary show producing 1-minute daily videos, (2) Jedi Council Show - featuring Eliza characters discussing blockchain topics, and (3) Block Tank - a Shark Tank-style show with AI judges.\n- **Technical Implementation**: Using \"Derpy Show JSON Structure\" for content generation, with Unity and PlayCanvas for visualization. SM Sith Lord developed a PlayCanvas prototype for Block Tank that can generate episodes within seconds.\n- **Animation Format Debate**: Discussion about VRM vs. FBX formats, with fishai arguing that FBX is more practical despite VRM's popularity in VTubing.\n\n### Community Management\n- **Role Structure**: The community has different roles based on token holdings: Partners (100k+ ai16z tokens), Associates (10k+ tokens), with discussion about adding an \"Executive\" role for 50k+ holders.\n- **Tipping System**: Jin demonstrated how to use the tip.cc bot for distributing AI16Z tokens as rewards for contributions, including airdrops, trivia drops, and direct tipping.\n- **Communication Improvements**: Jin mentioned plans for automated weekly updates and newsletters to prevent announcements from getting lost.\n\n## Key Questions & Answers\n\n### ElizaOS Framework & Development\nQ: How do I fix the Discord/Opus dependency error during installation? \nA: Install Microsoft C++ Build Tools or remove Discord voice functionality if not needed.\n\nQ: How do I make my Twitter agent respond to 'gm' messages? \nA: The issue may be with the LLM model; try changing to a different model.\n\nQ: How do I control how often my Twitter agent posts? \nA: Set ENABLE_ACTION_PROCESSING=false and adjust POST_INTERVAL_MIN and POST_INTERVAL_MAX in your .env file.\n\nQ: How do I use the web-search plugin? \nA: Add the plugin to your character with \"plugins\": [\"<@1300745997625982977>os/plugin-web-search\"] and set the Tavily API key in .env.\n\nQ: How do I make my agent use RAG knowledge effectively? \nA: Break knowledge into concise, specific lines with unique keywords for better embedding and retrieval.\n\nQ: How do I prevent my agent from interacting with other AI agents on Twitter? \nA: Use TWITTER_TARGET_USERS to whitelist specific users and delete your database to reset interactions.\n\nQ: How do I fix \"Cannot generate embedding: Memory content is empty\"? \nA: Clear cache and database files, ensure OpenAI embeddings are configured correctly in .env.\n\nQ: How do I make my agent access onchain data? \nA: Use plugins like plugin-evm or plugin-goat.\n\nQ: How do I expose an API to message an Eliza agent directly? \nA: Use the API defined in client-direct/lib/api.ts.\n\n### Tokenomics & Community\nQ: Why is ai16z rebranding to ElizaOS? \nA: a16z trademark protection is having issues with the memetic content; their lawyers say there will be issues defending their trademark, and partnerships with a16z may be on hold until a name change.\n\nQ: Can we change the ticker name? \nA: Technically it's unclear if it's feasible on Solana; baoskee said end of Q1 we can vote on it when they add the voting module.\n\nQ: What's the revenue sharing model for projects built on ElizaOS? \nA: 10% of their revenue goes to buying ai16z tokens, and we OTC those ai16z for their tokens in our treasury.\n\nQ: How will the DAO generate value from projects using ElizaOS? \nA: Through revenue sharing, trading fees, and potentially LP positions.\n\nQ: What's the difference between ElizaOS and other frameworks? \nA: ElizaOS is TypeScript, heavy, with direct integrations; others like Virtual's are Python, lightweight, composition-oriented with less native web3 support.\n\nQ: How much is associates? \nA: 10k tokens.\n\nQ: Does someone have a list of the levels for these roles? \nA: 100k partner role, 10k associate for ai16z; 1,000,000 degen ai: Partner role, 100,000 degenai: hoplite role.\n\n## Community Help & Collaboration\n\n### Technical Support\n- **MonteCrypto helped 0xLabsTheCoder** with RAG knowledge implementation, explaining that knowledge should be concise with unique keywords for better embedding, and suggested breaking text into smaller fragments by subject.\n- **EcchiPen helped tony** resolve embedding errors with Eliza starter by suggesting a sequence of commands: pnpm clean, pnpm update, pnpm install, pnpm build.\n- **Neil Jones helped 0xLisanAlGaib** fix an error with better-sqlite3 module version mismatch by suggesting rebuilding the module with \"pnpm rebuild better-sqlite3\".\n- **adonisabril helped RaglioKen** make Twitter replies more varied and less bot-like by suggesting adding style hints in the bio and lore sections of the character file.\n- **n00b_SaUce helped the community** resolve a Huggingface dependency issue during build by sharing a solution to delete .pnp.cjs file at root level and run clean/install commands.\n\n### Knowledge Sharing\n- **yikesawjeez shared detailed information** about Principal Market Makers (PMMs) and Designated Market Makers (DMMs) business models, including loan+call option structures and engagement frameworks for token launches.\n- **st4rgard3n clarified the value proposition** of AI16z partnerships, explaining that distribution and attention are the primary values AI16z offers, which is why projects would donate tokens.\n- **SM Sith Lord provided a detailed breakdown** of three shows being developed (AI Podcast, Jedi Council, Block Tank) and links to documentation.\n- **jin demonstrated how to use tip.cc bot** for token distribution, showing airdrops, trivia drops, and direct tipping functionality.\n- **0xkamikaze shared a screenshot** from Shaw providing some update about DegenAI when official information was otherwise missing.\n\n## Action Items\n\n### Technical Tasks\n- Fix embedding.ts in core package to resolve EmbeddingProvider namespace conflict (mentioned by realcringo)\n- Implement proper environment variable support in character files (mentioned by brodnick)\n- Fix Twitter client to prevent responding to scam replies (mentioned by mm)\n- Fix Discord client message generation loop (mentioned by Dennis_VDM)\n- Test Docker image with new architecture on AWS t4g.small (mentioned by Mike D.)\n- Integrate technical analysis module into Neuro runtime (mentioned by anomalyagentic)\n- Combine sentiment analysis and technical analysis for tweet signals (mentioned by anomalyagentic)\n- Create \"talk while sitting\" animations for Block Tank judges (mentioned by SM Sith Lord)\n- Add morph target animation (visemes) to characters in PlayCanvas (mentioned by SM Sith Lord)\n- Create \"interview room\" and \"deliberation room\" environment as FBX or GLB (mentioned by SM Sith Lord)\n- Implement QA moderation and submission fee collection for Block Tank (mentioned by SM Sith Lord)\n- Update stickers and emojis with the new \"taped hat\" logo (mentioned by jin)\n- Create an AI bounty agent to scan approved PRs and attribute Discord roles (mentioned by MonteCrypto)\n- Fix and cleanup contributor leaderboard code (mentioned by jin)\n- Implement newsletters for announcements (mentioned by jin)\n- Restrict Agent Scarlett to specific channels (mentioned by CtrlAltElite)\n- Develop a mechanism for projects to buy-and-send-to-DAO AI16z tokens (mentioned by shaw)\n- Integrate DegenSpartanAI with elizaOS affiliate account (mentioned by cool.eth)\n- Connect Agent Scarlett to help DegenAI as part of a research team (mentioned by jin)\n\n### Documentation Needs\n- Improve RAG documentation (mentioned by 0xLabsTheCoder)\n- Document REST API endpoints (mentioned by 0xChainBrain)\n- Create guide for multi-agent deployment (mentioned by Carlos Rene | DEGA)\n- Update Twitter integration documentation (mentioned by SMA)\n- Create a list of tools used in Eliza development (mentioned by PabloFM | Numinia)\n- Create a clear standard operating procedure (SOP) for potential partners (mentioned by st4rgard3n)\n- Build a community website to display partner projects with disclaimers (mentioned by MonteCrypto)\n- Release the Tokenomics document to take control of the narrative (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create a collection of Shaw and Jin podcasts (mentioned by TheGrayMatters)\n- Create a clear roadmap for DegenAI with now/next/future sections (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Publish DegenSpartanAI White Paper and Tokenomics (mentioned by NkT)\n- Create central information source about DegenAI (mentioned by MrNomad_)\n- Connect DegenAI tokenomics with ai16z tokenomics whitepaper (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create design proposal for Block Tank implementation options (mentioned by SM Sith Lord)\n- Update the awesome-eliza GitHub repository with ecosystem information (mentioned by jin)\n- Create a public webpage showing statistics about token holders (mentioned by MicoM.ron)\n- Create a document listing all major lore events (mentioned by jin)\n\n### Feature Requests\n- Implement event-driven architecture for agents (mentioned by Kraus)\n- Add support for Facebook integration (mentioned by mm)\n- Implement ability to order from Amazon directly from Discord DM (mentioned by Denko)\n- Develop a platform for agent-to-agent communication (mentioned by Branch Manager)\n- Add Eliza plugin for NFT-AI integration (mentioned by Mfairy)\n- Create merchandise with ai16z logo (mentioned by uniqueobject)\n- Implement automated communication system for project updates (mentioned by jin)\n- Demonstrate DegenAI's trading capabilities with verifiable evidence (mentioned by ZeroLearn)\n- Develop Multi-Shot Writers' Room approach for Block Tank (mentioned by SM Sith Lord)\n- Add 2-3 hero animations and rolling jokes for each character (mentioned by boom)\n- Implement word-triggered events in the show (mentioned by boom)\n- Improve news aggregator to include full ecosystem news (mentioned by jin)\n- Add disclaimer to shows (mentioned by boom)\n- Create a newsletter for the AI16Z community (mentioned by jin)\n- Create an \"Executive\" role for holders with 50k+ tokens (mentioned by jin)\n- Create memes with the new stickered logo (mentioned by jin)\n- Implement a system for associates to earn tokens through bounties (mentioned by jin)\n- Gather news from X and Discord for the newsletter (mentioned by jin)\n- Develop NFT collection for DegenAI (mentioned by shaw)\n- Integrate ElizaOS into robots (mentioned by Ava)\n- Implement LP management bot (mentioned by shaw)\n- Create a plugin marketplace (mentioned by witch)\n- Explore setting up market maker services for Eliza token launches (mentioned by yikesawjeez)\n- Develop a system to facilitate capital raising, MM partnerships, and CEX listings for partners (mentioned by st4rgard3n)"
},
"ai_news_elizaos_discord_md_2025-01-13": {
"filename": "2025-01-13.md",
"content": "# elizaOS Discord - 2025-01-13\n\n## Overall Discussion Highlights\n\n### Rebranding from ai16z to ElizaOS\n- The project is planning to rebrand from \"ai16z\" to \"ElizaOS\" due to potential trademark issues with a16z (Andreessen Horowitz)\n- This rebranding aims to better align the project's name with its technical foundation while avoiding legal complications\n- The team is consulting with Solana Foundation about whether the token ticker can be changed, but any change would need to wait at least 2 months\n- Shaw explained that rebranding would enable partnerships and collaborations currently on hold\n\n### ElizaOS Framework Development\n- The team is working on V2 of the framework with improved autonomy features\n- GitHub repository shows significant development activity with daily updates and numerous contributors\n- The framework currently has 77 plugins and supports multimodality\n- Docker image optimization by Mike D reduced image size by removing image/audio/video processing components\n- Several users are building applications on top of the Eliza framework, including GOATAGI and Ninjapump\n\n### Tokenomics and Marketplace\n- Jin is finalizing a tokenomics paper that will include multiple flywheel strategies to be implemented in phases\n- A \"Marketplace of Trust\" is being developed as part of the tokenomics strategy\n- Projects built on ElizaOS will contribute 10% back to the treasury through a tribute model\n- DorianD suggested embedding this 10% tribute mechanism in the codebase to ensure revenue even from forked implementations\n- Discussion about reframing the \"launchpad\" concept as an \"agent marketplace\"\n\n### AI TV Show Development\n- Team is developing an AI-powered TV show system with three formats:\n - AI Podcast (daily GitHub updates)\n - Jedi Council (characters discussing blockchain topics)\n - Block Tank (a Shark Tank-style show for crypto pitches)\n- SM Sith Lord manages the backend show generation system while Boom handles the Unity frontend\n- Technical challenges include JSON data flow issues and debates about 3D model formats (VRM vs. FBX)\n\n### Community Structure\n- New \"associates\" channel created for users holding 10,000+ AI16Z tokens (compared to \"partners\" with 100,000+)\n- Jin proposed creating an intermediate \"executive\" role (50k tokens) between associates and partners\n- Tip.cc bot implemented for distributing tokens within the community through airdrops, triviadrops, and red envelopes\n\n### DegenAI Concerns\n- Community members expressed frustration about lack of clear information regarding DegenAI's roadmap and integration with the ai16z ecosystem\n- Uncertainty about whether DegenAI is actively trading, with conflicting claims\n- Jin and Odilitime acknowledged feedback about improving communications, mentioning a website is coming soon\n\n## Key Questions & Answers\n\n**Q: How can I reduce the Docker image size for Eliza?** \nA: Remove image processing, hugging face, audio processing, video processing, and local onnx components (answered by Mike D.)\n\n**Q: How do I run multiple agents at once?** \nA: Use `pnpm start --characters=\"characters/1.character.json,characters/2.character.json\"` (answered by elamore)\n\n**Q: Why is ai16z rebranding to ElizaOS?** \nA: To avoid potential trademark issues with a16z (Andreessen Horowitz) and to better align the name with the technical foundation of the project. (answered by Shaw)\n\n**Q: How does the news update system work for the AI Podcast?** \nA: The system checks a JSON file at \"https://elizaos.github.io/data/daily/summary.json\" which contains GitHub updates, then generates episode content based on this data (answered by SM Sith Lord)\n\n**Q: What is the risk with requiring AI16Z for agent launches?** \nA: It could create illiquidity in the primary pool post-bond, especially with full range. (answered by eskender.eth)\n\n**Q: How does pump.fun's model work?** \nA: They take 20% tribute when the bonding curve for 80% of coins sold hits 100%, and reward creators with 0.5 SOL. (answered by DorianD)\n\n**Q: What is the DegenAI DAO wallet address?** \nA: AM84n1iLdxgVTAyENBcLdjXoyvjentTbu5Q6EpKV1PeG (answered by SHADOW |Zer0)\n\n**Q: How can I find a comprehensive list of live agents that use the Eliza framework?** \nA: Check https://www.daos.fun/HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC under AUM and https://elizas.world/ (answered by DorianD)\n\n**Q: Any tips on tools to improve beat/vocals for generated songs?** \nA: Use compression and multiband compression, break into stems if possible, and map to tempo in Ableton (answered by boom)\n\n## Community Help & Collaboration\n\n- **WSL Setup Help**: adonisabril provided step-by-step instructions for setting up WSL, cloning the repo, and running Eliza to help bendermind\n- **Database Schema Fix**: custodian shared a working SQL schema that resolved room creation function issues for kingCuckDad\n- **Node-llama-cpp Installation**: n00b_SaUce shared a solution to delete .pnp.cjs file and rebuild to fix Huggingface dependency errors\n- **Music Generation**: boom provided detailed advice to Dr. Neuro on improving AI-generated music quality using compression techniques and shared an optimized prompt for song generation\n- **Deployment Solution**: Mike D. shared a GitHub repository for one-click deployment using terraform with AWS t4g instances for cost-efficient hosting\n- **Discord Error Fix**: Stealt\u210fyNinja.ADSC shared a workaround for Discord opus errors by removing Discord voice functionality\n\n## Action Items\n\n### Technical\n- Complete V2 of ElizaOS framework with improved autonomy features (Mentioned by Shaw)\n- Implement a staking system for AI16Z tokens with quarterly rewards (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Consider embedding 10% tribute code in the Solana plugin (Mentioned by DorianD)\n- Fix the Twitter client to prevent posting message format instead of just the text content (Mentioned by Snuggyverse_E)\n- Implement event-driven architecture to decouple content generation from posting (Mentioned by Kraus)\n- Fix embedding dimension mismatch issues (Mentioned by Vaas)\n- Add support for ARM64 architecture (Mentioned by Morning3tar)\n- Fix Discord client dependency issues (Mentioned by PiagaShihari)\n- Move JSON download to happen after show ends instead of during recording (Mentioned by SM Sith Lord)\n- Implement character controller system for easier character management (Mentioned by fishai)\n- Create an \"executive\" role for users with 50k AI16Z tokens (Mentioned by jin)\n- Implement 8% DegenAI buyback as promised in tokenomics (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n\n### Documentation\n- Create comprehensive guide for web search plugin (Mentioned by jomolopo)\n- Update documentation on embedding configuration for Heurist (Mentioned by LeonGamer)\n- Create guide for Twitter bot settings configuration (Mentioned by SEDANO_YGG)\n- Create better documentation for plugins and clients (Mentioned by pagameba)\n- Create up-to-date beginner tutorial videos for visual learners (Mentioned by Lint-Minux)\n- Complete FAQ document for rebranding (Mentioned by Jin)\n- Create a one-pager introducing ai16z/ElizaOS (Mentioned by 0xwitch)\n- Create a clear roadmap for DegenAI showing now/next/future plans (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Publish wallet address and trading activity of DegenAI (Mentioned by ZeroLearn)\n\n### Features\n- Implement agent-to-agent Twitter group chats (Mentioned by Stealt\u210fyNinja.ADSC)\n- Develop no-code platform for building AI agents (Mentioned by CBK)\n- Implement a Reddit client (Mentioned by Oleg O.)\n- Add confirmation flow for blockchain transactions (Mentioned by tankjadu)\n- Implement a Bitcoin plugin (Mentioned by MonteCrypto)\n- Add support for Twitter spaces (Mentioned by trenchio)\n- Create \"Gauntlet of the Gods\" for community curation of agents (Mentioned by Robin)\n- Develop an agent marketplace instead of a launchpad (Mentioned by jin)\n- Implement futures and options trading strategies with AI-managed hedging (Mentioned by Display Name)\n- Add Degen Spartan for crypto market updates in AI TV shows (Mentioned by Smedroc)\n- Add DegenSpartanai to elizaOS affiliate account (Mentioned by cool.eth)"
},
"ai_news_elizaos_daily_json_2025-01-15": {
"filename": "2025-01-15.json",
"content": {
"type": "elizaosDailySummary",
"title": "Daily Report - 2025-01-15",
"categories": [
{
"title": "Eliza Project Updates Summary",
"content": [
{
"text": "# New Features\n\nThe Eliza project has introduced several significant new features:\n\n- **Onchain Agent Transformer**: Transform Eliza agents into Solidity smart contracts deployable on 10+ blockchains (PR #2319)\n- **Character Loading Improvements**: Support for loading characters from URLs (PR #2281) and enabling multiple remote character URLs (PR #2328)\n- **Memory Management**: Added getMemoryByIds to database adapters (PR #2293)\n- **Echo Chambers**: Added dead room detection and conversation starter functionality (PR #2248)\n- **DexScreener Integration**: Added token price action functionality (PR #1865) and trending features (PR #2325)\n- **Image Generation**: Added safe_mode and cfg_scale for Venice image generation (PR #2354) and Groq image vision provider (PR #2342)\n- **RAG Knowledge**: Enhanced RAG knowledge handling capabilities (PR #2351)\n- **New Clients/Providers**: Added Instagram client (PR #1964) and Atoma provider (PR #2082)\n- **S3 Flexibility**: Improved S3 integration options (PR #2379)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2319",
"https://github.com/elizaOS/eliza/pull/2281",
"https://github.com/elizaOS/eliza/pull/2293",
"https://github.com/elizaOS/eliza/pull/2248",
"https://github.com/elizaOS/eliza/pull/1865",
"https://github.com/elizaOS/eliza/pull/2325",
"https://github.com/elizaOS/eliza/pull/2354",
"https://github.com/elizaOS/eliza/pull/2342",
"https://github.com/elizaOS/eliza/pull/2351",
"https://github.com/elizaOS/eliza/pull/1964",
"https://github.com/elizaOS/eliza/pull/2082",
"https://github.com/elizaOS/eliza/pull/2379",
"https://github.com/elizaOS/eliza/pull/2328"
],
"images": [],
"videos": []
},
{
"text": "# Bug Fixes\n\nSeveral important bug fixes have been implemented:\n\n- **Environment Variables**: Fixed OPENROUTER_API_KEY environment variable in config (PR #2324)\n- **Memory Issues**: Fixed Farcaster memory issues (PR #2307)\n- **Configuration Improvements**: \n - Fixed alignment of base URL in client when API runs on different port (PR #2353)\n - Prevented app crashes when REMOTE_CHARACTER_URLS is undefined (PR #2384, #2382)\n - Set default Squid Router plugin throttle to 1000 (PR #2386)\n- **Import Fixes**: Corrected typo in import statement for Solana AgentKit plugin (PR #2370)\n- **Docker Issues**: Fixed docker images, compose, and documentation (PR #2347)\n- **Package Updates**: Updated package.json of core package (PR #2301)\n- **Reply Hallucinations**: Ensured RA Action reply does not hallucinate (PR #2355)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2324",
"https://github.com/elizaOS/eliza/pull/2307",
"https://github.com/elizaOS/eliza/pull/2353",
"https://github.com/elizaOS/eliza/pull/2384",
"https://github.com/elizaOS/eliza/pull/2382",
"https://github.com/elizaOS/eliza/pull/2386",
"https://github.com/elizaOS/eliza/pull/2370",
"https://github.com/elizaOS/eliza/pull/2347",
"https://github.com/elizaOS/eliza/pull/2301",
"https://github.com/elizaOS/eliza/pull/2355"
],
"images": [],
"videos": []
},
{
"text": "# Testing and Code Quality\n\nSignificant improvements to testing and code quality have been made:\n\n- **New Tests**: Added tests for GitHub client (PR #2407), Slack client (PR #2404), and Solana plugin (PR #2345)\n- **Code Organization**: Moved existing tests to new __tests__ directory (PR #2404)\n- **Refactoring**: \n - Refactored websearch into a service (PR #2195)\n - Refactored Farcaster client environment configuration (PR #2087)\n- **Linting**: Fixed lint errors (PR #2400, #2368)\n- **Type Safety**: Implemented strict types to avoid errors (PR #2220)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2407",
"https://github.com/elizaOS/eliza/pull/2404",
"https://github.com/elizaOS/eliza/pull/2345",
"https://github.com/elizaOS/eliza/pull/2195",
"https://github.com/elizaOS/eliza/pull/2087",
"https://github.com/elizaOS/eliza/pull/2400",
"https://github.com/elizaOS/eliza/pull/2368",
"https://github.com/elizaOS/eliza/pull/2220"
],
"images": [],
"videos": []
},
{
"text": "# Documentation\n\nDocumentation has been enhanced across the project:\n\n- **README Updates**: Updated main README.md (PR #2309, #2280) and fixed formatting in Browser section (PR #2336)\n- **Translations**: Updated README_FR.md (PR #2356) and README_TR.md (PR #2334)\n- **Organization**: Reorganized README translations into a dedicated i18n directory structure (PR #2149)\n- **Client Documentation**: Fixed GitHub client README.md (PR #2346)\n- **Descriptions**: Improved descriptions throughout the project (PR #2394)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2309",
"https://github.com/elizaOS/eliza/pull/2280",
"https://github.com/elizaOS/eliza/pull/2336",
"https://github.com/elizaOS/eliza/pull/2356",
"https://github.com/elizaOS/eliza/pull/2334",
"https://github.com/elizaOS/eliza/pull/2149",
"https://github.com/elizaOS/eliza/pull/2346",
"https://github.com/elizaOS/eliza/pull/2394"
],
"images": [],
"videos": []
},
{
"text": "# Maintenance\n\nVarious maintenance tasks have been completed:\n\n- **Release Preparation**: Prepared for version 0.1.9-alpha.1 (PR #2359)\n- **Cleanup**: Improved exit code handling after positive cleanup (PR #2398)\n- **Error Handling**: Addressed startup errors from environment misconfiguration (PR #2378)\n- **Follow-up Work**: Completed sequel to PR #2275 (PR #2350)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2359",
"https://github.com/elizaOS/eliza/pull/2398",
"https://github.com/elizaOS/eliza/pull/2378",
"https://github.com/elizaOS/eliza/pull/2350"
],
"images": [],
"videos": []
}
],
"topic": "completed_items"
},
{
"title": "DankVR and ShawMakesMagic on AI, Crypto, and Open Source",
"content": [
{
"text": "DankVR expressed excitement about a new $3,000 device releasing in May that can run 405b AI models locally when two are chained together, showing enthusiasm for local-first open source AI.",
"sources": [
"https://twitter.com/dankvr/status/1879558859771220463"
],
"images": [],
"videos": []
},
{
"text": "DankVR shared a comprehensive analysis of crypto plugins in ElizaOS, identifying 23 distinct blockchain/crypto-focused plugins supporting various ecosystems including EVM-compatible chains. They used code2prompt to analyze the capabilities.",
"sources": [
"https://twitter.com/dankvr/status/1879545226928226587",
"https://twitter.com/dankvr/status/1879545534924611637",
"https://twitter.com/dankvr/status/1879546639230107871"
],
"images": [
"https://pbs.twimg.com/media/GhV8SD6WAAAi1me.jpg"
],
"videos": []
},
{
"text": "DankVR showcased a new preview of the Eliza contributor leaderboard with features like skill cards navigation, daily summaries, and URL-based filtering, describing it as making 'open source more like an MMORPG'.",
"sources": [
"https://twitter.com/dankvr/status/1879374351939817604"
],
"images": [],
"videos": [
"https://video.twimg.com/ext_tw_video/1879369318825148416/pu/vid/avc1/1280x720/IlKY_mR7l4o1soix.mp4?tag=12"
]
},
{
"text": "DankVR expressed desire for an 'AI intern' to scribe relevant information from group chats to help coordinate decisions and avoid the 'game of telephone' effect when people forget to take notes.",
"sources": [
"https://twitter.com/dankvr/status/1879553756435767719",
"https://twitter.com/dankvr/status/1879555566730957144"
],
"images": [],
"videos": []
},
{
"text": "ShawMakesMagic highlighted a new v2 core for building lightweight, production-ready agents, crediting @bmgalego as a 'seriously cracked dev' and noting it should feel familiar to beginners while offering advanced capabilities.",
"sources": [
"https://twitter.com/shawmakesmagic/status/1879335754670772569",
"https://twitter.com/shawmakesmagic/status/1879545807747289490"
],
"images": [],
"videos": []
},
{
"text": "ShawMakesMagic shared perspectives on AI development, suggesting that AGI won't come from one company or be one thing, comparing it to how 'humanity is not a brain.' They also discussed the concept of 'progressive automation' similar to 'progressive decentralization.'",
"sources": [
"https://twitter.com/shawmakesmagic/status/1879446605331619871",
"https://twitter.com/shawmakesmagic/status/1879383801593467070"
],
"images": [],
"videos": []
},
{
"text": "ShawMakesMagic questioned the notion of autonomous agents, suggesting that many so-called autonomous systems are actually event-driven, with LLMs primarily helping to process unstructured data into structured output.",
"sources": [
"https://twitter.com/shawmakesmagic/status/1879331992816566273",
"https://twitter.com/shawmakesmagic/status/1879325459844145183"
],
"images": [],
"videos": []
},
{
"text": "Both users showed interest in the intersection of AI, blockchain, and open source technologies, with a focus on practical applications and development frameworks.",
"sources": [
"https://twitter.com/dankvr/status/1879545226928226587",
"https://twitter.com/shawmakesmagic/status/1879335754670772569"
],
"images": [],
"videos": []
}
],
"topic": "tweet"
},
{
"title": "Recent Issues in the elizaOS/eliza GitHub Repository",
"content": [
{
"text": "The elizaOS/eliza GitHub repository has several open issues related to various bugs and feature requests. These issues span different aspects of the system including:\n\n1. User Interface Issues:\n - Issue #2316: Users experiencing duplicate responses to actions\n - Issue #2395: Difficulty executing multiple dependent actions in response to a single user message\n\n2. Deployment and Environment Problems:\n - Issue #2343: Bug when running in cloud from docker image\n - Issue #2360: Startup failures on macOS\n - Issue #2372: Twitter authentication failing on AWS EC2 instances with Error 399\n\n3. Performance Concerns:\n - Issue #2311: Low performance under parallel requests\n\n4. Plugin-specific Issues:\n - Issue #2320: Enhancement needed for query text extraction in the chainbase plugin\n - Issue #2373: Bugs related to image description service in the node plugin\n\n5. Schema and Configuration Problems:\n - Issue #2339: Error with invalid schema\n - Issue #2381: Bug in dev.sh script when loading characters with the --character parameter",
"sources": [
"https://github.com/elizaOS/eliza/issues/2316",
"https://github.com/elizaOS/eliza/issues/2343",
"https://github.com/elizaOS/eliza/issues/2339",
"https://github.com/elizaOS/eliza/issues/2320",
"https://github.com/elizaOS/eliza/issues/2311",
"https://github.com/elizaOS/eliza/issues/2360",
"https://github.com/elizaOS/eliza/issues/2372",
"https://github.com/elizaOS/eliza/issues/2395",
"https://github.com/elizaOS/eliza/issues/2373",
"https://github.com/elizaOS/eliza/issues/2381"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2316",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2343",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2339",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2320",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2311",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2360",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2372",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2395",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2373",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2381"
],
"videos": []
}
],
"topic": "issue"
},
{
"title": "Recent Pull Requests in the elizaOS/eliza Repository",
"content": [
{
"text": "The elizaOS/eliza repository has seen several significant pull requests recently, focusing on new features, enhancements, and version updates:\n\n- PR #2326 introduces a draft example feature for strace with pnpm integration\n- PR #2283 adds NFT functionality with ntf-starter and nft-generator components\n- PR #2314 contributes changes labeled as 'Ng/phill' by user 0xnogo\n- PR #2380 implements a plugin for the OriginTrail Decentralized Knowledge Graph\n- PR #2331 enhances RAG (Retrieval-Augmented Generation) knowledge handling and performance\n- PR #2107 adds a Code In Plugin that loads characters from blockchain with PDA (Program Derived Address)\n\nVersion management PRs include #2361 (merging dev to main for version 0.1.9) and #2359 (preparation for version 0.1.9-alpha.1).\n\nThese contributions demonstrate active development across various aspects of the eliza project, including blockchain integration, knowledge management, and developer tooling.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2326",
"https://github.com/elizaOS/eliza/pull/2283",
"https://github.com/elizaOS/eliza/pull/2314",
"https://github.com/elizaOS/eliza/pull/2361",
"https://github.com/elizaOS/eliza/pull/2380",
"https://github.com/elizaOS/eliza/pull/2331",
"https://github.com/elizaOS/eliza/pull/2107",
"https://github.com/elizaOS/eliza/pull/2359"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2326",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2283",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2380",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2331"
],
"videos": []
}
],
"topic": "pull_request"
},
{
"title": "ElizaOS GitHub Activity Update",
"content": [
{
"text": "The elizaos/eliza repository showed increased activity over a two-day period. From January 15-16, 2025, there were 30 new pull requests with 11 merged, 9 new issues, and 75 active contributors. Activity increased the following day (January 16-17, 2025) with 46 new pull requests (33 merged), 10 new issues, and 83 active contributors. This represents a 53% increase in new PRs, a 200% increase in merged PRs, and a 10.7% increase in active contributors day-over-day.",
"sources": [
"From 2025-01-15 to 2025-01-16, elizaos/eliza had 30 new PRs (11 merged), 9 new issues, and 75 active contributors.",
"From 2025-01-16 to 2025-01-17, elizaos/eliza had 46 new PRs (33 merged), 10 new issues, and 83 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": 1736899200
}
},
"ai_news_elizaos_daily_md_2025-01-15": {
"filename": "2025-01-15.md",
"content": "# Eliza Project Updates Summary\n\n## New Features\n- **Onchain Agent Transformer**: Transform Eliza agents into Solidity smart contracts deployable on 10+ blockchains\n- **Character Loading Improvements**: Support for loading characters from URLs and enabling multiple remote character URLs\n- **Memory Management**: Added getMemoryByIds to database adapters\n- **Echo Chambers**: Added dead room detection and conversation starter functionality\n- **DexScreener Integration**: Added token price action functionality and trending features\n- **Image Generation**: Added safe_mode and cfg_scale for Venice image generation and Groq image vision provider\n- **RAG Knowledge**: Enhanced RAG knowledge handling capabilities\n- **New Clients/Providers**: Added Instagram client and Atoma provider\n- **S3 Flexibility**: Improved S3 integration options\n\n## Bug Fixes\n- **Environment Variables**: Fixed OPENROUTER_API_KEY environment variable in config\n- **Memory Issues**: Fixed Farcaster memory issues\n- **Configuration Improvements**: \n - Fixed alignment of base URL in client when API runs on different port\n - Prevented app crashes when REMOTE_CHARACTER_URLS is undefined\n - Set default Squid Router plugin throttle to 1000\n- **Import Fixes**: Corrected typo in import statement for Solana AgentKit plugin\n- **Docker Issues**: Fixed docker images, compose, and documentation\n- **Package Updates**: Updated package.json of core package\n- **Reply Hallucinations**: Ensured RA Action reply does not hallucinate\n\n## Testing and Code Quality\n- **New Tests**: Added tests for GitHub client, Slack client, and Solana plugin\n- **Code Organization**: Moved existing tests to new __tests__ directory\n- **Refactoring**: \n - Refactored websearch into a service\n - Refactored Farcaster client environment configuration\n- **Linting**: Fixed lint errors\n- **Type Safety**: Implemented strict types to avoid errors\n\n## Documentation\n- **README Updates**: Updated main README.md and fixed formatting in Browser section\n- **Translations**: Updated README_FR.md and README_TR.md\n- **Organization**: Reorganized README translations into a dedicated i18n directory structure\n- **Client Documentation**: Fixed GitHub client README.md\n- **Descriptions**: Improved descriptions throughout the project\n\n## Maintenance\n- **Release Preparation**: Prepared for version 0.1.9-alpha.1\n- **Cleanup**: Improved exit code handling after positive cleanup\n- **Error Handling**: Addressed startup errors from environment misconfiguration\n- **Follow-up Work**: Completed sequel to PR #2275\n\n# DankVR and ShawMakesMagic on AI, Crypto, and Open Source\n\n- DankVR expressed excitement about a new $3,000 device releasing in May that can run 405b AI models locally when chained together\n- DankVR shared analysis of 23 distinct blockchain/crypto-focused plugins in ElizaOS supporting various ecosystems including EVM-compatible chains\n- DankVR showcased a preview of the Eliza contributor leaderboard with features like skill cards navigation and daily summaries\n- DankVR expressed desire for an 'AI intern' to scribe relevant information from group chats\n- ShawMakesMagic highlighted a new v2 core for building lightweight, production-ready agents\n- ShawMakesMagic shared perspectives on AI development, suggesting AGI won't come from one company\n- ShawMakesMagic discussed the concept of 'progressive automation' similar to 'progressive decentralization'\n- Both users showed interest in the intersection of AI, blockchain, and open source technologies\n\n# Recent Pull Requests\n\n- Draft example feature for strace with pnpm integration\n- NFT functionality with ntf-starter and nft-generator components\n- Changes labeled as 'Ng/phill' by user 0xnogo\n- Plugin for the OriginTrail Decentralized Knowledge Graph\n- Enhanced RAG knowledge handling and performance\n- Code In Plugin that loads characters from blockchain with PDA\n- Version management PRs for 0.1.9 and 0.1.9-alpha.1\n\n# GitHub Activity Update\n\n- From January 15-16, 2025: 30 new pull requests (11 merged), 9 new issues, and 75 active contributors\n- From January 16-17, 2025: 46 new pull requests (33 merged), 10 new issues, and 83 active contributors\n- Activity increased with 53% more new PRs, 200% more merged PRs, and 10.7% more active contributors day-over-day"
},
"ai_news_elizaos_daily_discord_json_2025-01-15": {
"filename": "2025-01-15.json",
"content": {
"server": "elizaOS",
"title": "elizaOS Discord - 2025-01-15",
"date": 1736899200,
"stats": {
"totalMessages": 5166,
"totalUsers": 564
},
"categories": [
{
"channelId": "1253563209462448241",
"channelName": "discussion",
"summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe discussion channel primarily focuses on ElizaOS, an AI agent framework. Technical conversations revolve around agent development, deployment, and integration. Users discuss installing and configuring ElizaOS agents, connecting them to platforms like Twitter, and troubleshooting common errors. There are questions about running agents locally versus on cloud services, with AWS and DigitalOcean mentioned as hosting options. Several developers share their projects built with ElizaOS, including trading bots, social media agents, and specialized AI tools. The community appears to be actively building and extending the framework with plugins, including a Chainbase plugin for blockchain data querying and a multimodal generation SDK for music. Technical issues discussed include installation problems with Discord's opus package, character file formatting in JSON generation tools, and deployment challenges on platforms like Render. The community also discusses security considerations for agent wallets and local versus cloud deployment options.\n\n## 2. FAQ\nQ: Do you need a good PC to run more complex AI agents? (asked by j.) A: Depends on what you're building but any decent laptop can handle most agents (answered by BOSSU)\nQ: Is it possible to run elizaos on radeon gpu? (asked by hub) A: Unanswered\nQ: How to integrate an agent into Twitter? (asked by docLJ | Solana ID) A: Check out agent dev school on YouTube and hit the coders channel for Twitter integration help (answered by BOSSU)\nQ: Do I need to know how to code to create my own AI agent on Eliza OS? (asked by WAGMI8604) A: Yes and no. Depends what you want to do with it (answered by Dragonbutt)\nQ: Is there a benefit from holding 10,000 AI16Z? (asked by johngalt3730) A: 10k ai16z tokens lets you see in some of the partner(100k ai16z tokens) chat but you can't type or react (answered by Dragonbutt)\nQ: How to verify for partner role? (asked by smileyyy face) A: Verification is paused right now (answered by BOSSU)\nQ: Is there a place to see a compilation of agents created using ElizaOS? (asked by slim) A: Head to elizaos dot ai to check the gallery (answered by BOSSU)\nQ: Does $tip actually give people real crypto? (asked by j.) A: Unanswered\nQ: How do I expose a PORT on Render? (asked by boja) A: Unanswered\nQ: How to connect my AI agent in N8N? (asked by 0xTheDot) A: Check the coders channel, that's where all the tech wizards hang out (answered by BOSSU)\nQ: Where can I host Eliza? (asked by Froggy Potter) A: For hosting Eliza check out AWS or DigitalOcean, head to coders channel for more tech details (answered by BOSSU)\n\n## 3. Help Interactions\nHelper: Dragonbutt | Helpee: WAGMI8604 | Context: Asking about learning resources for creating AI agents without coding knowledge | Resolution: Directed to the Agent Dev School channel and recommended a 12-hour JavaScript crash course on YouTube\nHelper: MicoM.ron | Helpee: WAGMI8604 | Context: Asking about programming languages needed for AI agents | Resolution: Explained that code is written in TypeScript and user needs to be familiar with that language\nHelper: BOSSU | Helpee: jeremyboise | Context: Experienced developer having trouble installing Eliza and Eliza-starter due to @discord/opus dependency failures | Resolution: Directed to coders channel for installation help\nHelper: MicoM.ron | Helpee: David | Context: New user asking how to start with ai16z | Resolution: Provided links to GitHub awesome-eliza repository and HackMD resource\nHelper: Kenk | Helpee: Roman V | Context: User considering switching from G.A.M.E to Eliza for agent development | Resolution: Provided links to documentation, eliza.gg website, and Shaw's YouTube videos\n\n## 4. Action Items\nType: Technical | Description: Fix JSON structure in Howieduhzit tool to properly create arrays of strings for Topic, Bio, Lore and Post Examples | Mentioned By: Dreygo\nType: Technical | Description: Implement local TTS option as alternative to ElevenLabs | Mentioned By: Abderahman\nType: Technical | Description: Create GitHub client plugin for ElizaOS | Mentioned By: suso\nType: Technical | Description: Integrate Chainbase plugin for natural language querying of blockchain data | Mentioned By: Lil Lowkey | Chainbase\nType: Technical | Description: Integrate BEATS SDK for multimodal generation (starting with songs) | Mentioned By: ryoh\nType: Technical | Description: Fix installation issues with @discord/opus dependency | Mentioned By: jeremyboise\nType: Technical | Description: Create an AI bounty agent to scan approved PRs and attribute Discord roles based on coding effort | Mentioned By: MonteCrypto\nType: Documentation | Description: Create weekly newsletters to prevent announcements from piling up and getting lost | Mentioned By: jin\nType: Documentation | Description: Document tokenomics and token utility mechanisms | Mentioned By: Burtiik\nType: Feature | Description: Add ability for AI agents to search and post on Reddit | Mentioned By: uniqueobject\nType: Feature | Description: Create an agent for autonomous trading with wallet security | Mentioned By: kobra\nType: Feature | Description: Develop AI agent for improving and backtesting TradingView scripts | Mentioned By: FutureStocks",
"messageCount": 763,
"userCount": 257
},
{
"channelId": "1300025221834739744",
"channelName": "\ud83d\udcbb-coders",
"summary": "# Analysis of \ud83d\udcbb-coders Discord Chat\n\n## 1. Summary\nThe conversation primarily revolves around technical issues with the Eliza AI agent framework. Users discuss various implementation challenges including embedding errors, plugin integration problems, Twitter client configuration, and database management. Key technical discussions include:\n\n- Knowledge management and RAG (Retrieval Augmented Generation) implementation, with users struggling to understand how knowledge is stored, retrieved, and utilized by agents\n- Twitter client integration issues, particularly with authentication, reply functionality, and rate limiting\n- Database configuration challenges, especially when transitioning between SQLite and Supabase\n- Plugin development and integration, with users creating custom plugins for cryptocurrency data and blockchain interactions\n- Docker deployment issues across different environments (Mac, Windows, Linux)\n- Character configuration problems, particularly with embedding models and knowledge representation\n- API endpoint discovery for direct agent communication without intermediary clients\n\nSeveral users shared solutions for common problems, including clearing database files to reset state, properly formatting private keys, and structuring knowledge for effective RAG implementation.\n\n## 2. FAQ\nQ: How can I make my agent access onchain data? (asked by RaglioKen) A: Use plugins like plugin-evm or GOAT plugin (answered by adonisabril)\nQ: How do I make the replies on Twitter more varied and less bot-like? (asked by RaglioKen) A: Give it hints in the bio and lore of your character file (answered by adonisabril)\nQ: Is there a way to encode message frequency so the agent only responds to interesting content? (asked by ChatGPT) A: Unanswered\nQ: How do I add target users? (asked by \ud83c\udf08\u20e4 \u2728\u2b52\u0e4b\u08ed\u2b51\u3010=\u035f\u035f\u035e\ud83c\udf08\u20e4 \u2b52\u0e4b\u08ed\u2b51.) A: Put the info in the .env file (answered by multiple users)\nQ: Is there a difference between client-twitter and plugin-twitter? (asked by HamsterdamCapital) A: Watch the video demonstration of plugin-twitter (answered by webthreeninja)\nQ: How can I fix the \"Cannot generate embedding: Memory content is empty\" error? (asked by tony) A: Clear your cache and database file, ensure OpenAI embeddings are configured (answered by Simz)\nQ: How do I make my agent analyze an image? (asked by \ud83c\udf08\u20e4 \u2728\u2b52\u0e4b\u08ed\u2b51\u3010=\u035f\u035f\u035e\ud83c\udf08\u20e4 \u2b52\u0e4b\u08ed\u2b51.) A: Use OpenAI or Anthropic models that support image analysis (answered by Jessy | Unicake\ud83e\udd84)\nQ: How do I get Sepolia ETH for testing? (asked by Jessy | Unicake\ud83e\udd84) A: Use Google Cloud Web3 or faucets (answered by \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f)\nQ: Where is the REST API for direct agent communication? (asked by 0xChainBrain) A: It's in lib/api.ts (answered by zadkielm)\nQ: How do I structure knowledge for effective RAG implementation? (asked by 0xLabsTheCoder) A: Break knowledge into concise lines with specific keywords for embedding (answered by MonteCrypto)\n\n## 3. Help Interactions\nHelper: MonteCrypto | Helpee: 0xLabsTheCoder | Context: Understanding how knowledge and RAG work in Eliza | Resolution: Explained that knowledge should be fragmented into short, concise lines with unique keywords for effective embedding and retrieval\nHelper: Simz | Helpee: tony | Context: Fixing \"Cannot generate embedding: Memory content is empty\" error | Resolution: Suggested clearing cache and database files, and ensuring OpenAI embeddings are properly configured\nHelper: zadkielm | Helpee: 0xChainBrain | Context: Finding REST API endpoint for direct agent communication | Resolution: Pointed to lib/api.ts where the endpoint is defined\nHelper: ! ! Dead | Helpee: HK | Context: Eliza installation and version checking | Resolution: Explained how to check Eliza version and verify installation\nHelper: MonteCrypto | Helpee: JimmyC15 | Context: How to structure knowledge for RAG | Resolution: Advised breaking knowledge into lines and having concise subjects\nHelper: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f | Helpee: Jessy | Unicake\ud83e\udd84 | Context: EVM private key format | Resolution: Suggested including 0x prefix in the private key\nHelper: Neil Jones | Helpee: 0xLisanAlGaib | Context: Fixing better-sqlite3 Node.js version mismatch | Resolution: Provided commands to rebuild better-sqlite3 or reinstall requirements\nHelper: Branch Manager | Helpee: tony | Context: Character loading issues | Resolution: Shared a pastebin link with a replacement file to fix the issue\n\n## 4. Action Items\nTechnical: Fix embedding errors when using different embedding models with Supabase | Description: Ensure compatibility between embedding dimensions (384 vs 1536) | Mentioned By: NoBody | SUIRISE\nTechnical: Implement proper error handling for Twitter client | Description: Add better error logging for Twitter interactions | Mentioned By: GOGOGO\u26d3\ud83d\udca5\nTechnical: Fix evaluator validation logic | Description: Evaluators don't trigger unless alwaysRun is set to true | Mentioned By: bifkn\nTechnical: Improve knowledge retrieval in RAG implementation | Description: Optimize how knowledge is structured and retrieved | Mentioned By: 0xLabsTheCoder\nTechnical: Fix Docker build issues on ARM64 architecture | Description: Resolve memory-related failures during build | Mentioned By: Tobias | QDEV\nDocumentation: Add details about target users configuration | Description: Explain how to properly configure and use target users list | Mentioned By: SMA\nDocumentation: Improve plugin development documentation | Description: Create better guides for building custom plugins | Mentioned By: MonteCrypto\nDocumentation: Update EVM private key format requirements | Description: Clarify that 0x prefix is needed | Mentioned By: Jessy | Unicake\ud83e\udd84\nDocumentation: Create guide for knowledge structuring | Description: Explain how to format knowledge for effective RAG | Mentioned By: 0xLabsTheCoder\nFeature: Implement multi-agent interaction system | Description: Allow agents to communicate with each other | Mentioned By: 0xLabsTheCoder\nFeature: Add API for direct agent communication | Description: Create REST endpoints for messaging agents | Mentioned By: 0xChainBrain\nFeature: Develop wallet protection mechanism | Description: Prevent unauthorized use of agent wallets | Mentioned By: kobra\nFeature: Create global/shared memories system | Description: Allow knowledge to be shared across agents | Mentioned By: matthias_ztlr\nFeature: Improve Twitter client reply functionality | Description: Fix issues with agents not responding to mentions | Mentioned By: PhyoPhyoLay\nFeature: Add support for local TTS instead of ElevenLabs | Description: Allow using local text-to-speech engines | Mentioned By: Abderahman",
"messageCount": 1431,
"userCount": 212
},
{
"channelId": "1300756641406521416",
"channelName": "ideas-feedback-rants",
"summary": "# Discord Chat Analysis: ideas-feedback-rants\n\n## 1. Summary\nThe chat primarily focused on AI agent development, DeFAI (Decentralized Finance AI) integration, and AI music generation. Several users discussed technical issues with building Eliza agents, particularly version compatibility problems. A significant portion of the conversation involved two users (Dr. Neuro and boom) exploring AI music generation using Suno, sharing prompts and techniques for creating multi-voice rap songs with different personas. They discussed prompt engineering strategies like adding \"AI\" to artist names to bypass copyright restrictions and creating structured prompts with defined roles for each voice. The chat also touched on the potential integration of technical analysis modules into the Neuro runtime, combining sentiment analysis from Twitter with technical indicators for cryptocurrency trading signals. Users expressed interest in the growing DeFAI ecosystem, discussing metrics for measuring adoption and the rapid market growth in this sector.\n\n## 2. FAQ\nQ: Does anyone have this same error while using v0.1.8? (asked by Danieldere) A: Close vscode. Delete ur nodemodule. Install and build back. You can open vscode after it is completed. vs code has some issue holding the folder which preventing from installing or building sometimes. (answered by sazilariel)\nQ: Will there be EthDenver Eliza meetup? (asked by Lil Lowkey | Chainbase) A: Unanswered\nQ: Who would be the best person to speak with for an AMA about the Eliza community and framework? (asked by Lil Lowkey | Chainbase) A: Unanswered\nQ: What tool is this [for viewing DeFAI market data]? (asked by nullfoxgiven) A: Coingecko (answered by Display Name)\nQ: Can I shoot you a couple of questions about AI trading agents? (asked by MrCitron) A: Unanswered\nQ: Could you please suggest what's a more beginner friendly set of tools to try out to build an AI educator support agent? (asked by dods) A: Unanswered\nQ: Where can we find v2 core? (asked by Mike D.) A: Unanswered\n\n## 3. Help Interactions\nHelper: sazilariel | Helpee: Deleted User | Context: User experiencing errors when building 1.0.18+build1 related to Tanstack, Lucid-react, NavLink | Resolution: Suggested closing VSCode, deleting node_modules, then reinstalling and rebuilding, as VSCode sometimes has issues with folder access.\nHelper: Display Name | Helpee: nullfoxgiven | Context: User asking about metrics for DeFAI adoption | Resolution: Explained that market cap is a reasonable proxy metric as it reflects overall agent quality, deployment frequency, and transaction volume.\nHelper: Dr. Neuro | Helpee: boom | Context: Creating multi-voice AI rap songs in Suno | Resolution: Shared technique of adding \"AI\" to artist names to bypass copyright restrictions and using structured prompts with defined roles.\nHelper: boom | Helpee: Dr. Neuro | Context: Improving AI-generated rap lyrics | Resolution: Shared prompt techniques for creating better flow and multi-rhyme schemes in AI-generated rap lyrics.\n\n## 4. Action Items\nType: Technical | Description: Integrate technical analysis module into Neuro runtime to generate insights using 20+ indicators based on token price data | Mentioned By: anomalyagentic\nType: Technical | Description: Combine sentiment analysis from Twitter timeline with technical analysis to generate trading signals | Mentioned By: anomalyagentic\nType: Technical | Description: Explore integration between Eleven Labs voice profiles and Suno for multi-voice AI music generation | Mentioned By: boom\nType: Feature | Description: Create a cloud-based test bed for AI agents | Mentioned By: Hidden Forces\nType: Feature | Description: Develop AI beatmaker assistant for real-time music production collaboration | Mentioned By: boom\nType: Feature | Description: Explore capability for Eliza to create 3D objects in Blender through API integration | Mentioned By: judasz\nType: Documentation | Description: Create basic troubleshooting guide for launching Eliza agents | Mentioned By: Hidden Forces\nType: Documentation | Description: Update hyperlink to the ai16z X page in the CMC page to point to correct URL | Mentioned By: JohnnyB",
"messageCount": 202,
"userCount": 21
},
{
"channelId": "1308149076893630555",
"channelName": "spartan_holders",
"summary": "# Analysis of \"spartan_holders\" Discord Channel\n\n## 1. Summary\nThe chat segment shows community members expressing frustration about the lack of updates and slow progress on DegenAI, which appears to be an AI agent project from ai16z. Users are requesting information about white papers, tokenomics, and development timelines. There's significant impatience in the community, with members comparing DegenAI unfavorably to other projects like ELIZA. A user named \"jin\" mentions they're talking to other research agent developers and suggests that \"agent scarlett\" could potentially help DegenAI as part of a research team. Overall, the conversation reflects community dissatisfaction with communication and development pace rather than containing substantial technical discussions or problem-solving.\n\n## 2. FAQ\nQ: When will Degenspartan's White Paper or Tokenomics be released? Is it in progress now? (asked by NkT) A: Unanswered\nQ: Who are you? (asked by xiaojiucai) A: Unanswered\nQ: Wen degenai (asked by Jesus) A: Unanswered\nQ: As the first AI agent of ai16z, degenai's progress is so slow. What's the problem? Were you involved in the development of degenai? (asked by cool.eth) A: Unanswered\nQ: Was Skely fired? (asked by cool.eth) A: Unanswered\nQ: Does scarlett have their own token? (asked by ZeroLearn) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: Community | Context: Lack of progress with DegenAI | Resolution: Mentioned talking to research agent developers and suggested agent scarlett could help DegenAI as part of a research team\n\n## 4. Action Items\nTechnical: Potential integration of agent scarlett with DegenAI research team | Description: Exploring collaboration with other AI agent developers | Mentioned By: jin\nDocumentation: White Paper and Tokenomics documentation needed | Description: Community requesting official documentation for DegenSpartan | Mentioned By: NkT\nFeature: Improve DegenAI beyond current chatbot functionality | Description: Community expressing that current implementation is too basic | Mentioned By: NkT",
"messageCount": 44,
"userCount": 16
},
{
"channelId": "1328592959444095038",
"channelName": "associates",
"summary": "# Analysis of \"associates\" Discord Channel\n\n## 1. Summary\nThe channel primarily focuses on community engagement around the Eliza ecosystem, particularly AI16z. Key technical discussions centered on creating and updating branded assets with the new \"taped hat\" logo. Jin initiated a bounty for community members to update stickers and emojis with this new branding element, providing URLs to access Discord sticker files. There was also discussion about establishing a newsletter for the community, with MicoM.ron sharing templates and offering to help organize this effort. Jin created another bounty for maintaining and updating the \"awesome-eliza\" GitHub repository, which serves as a curated list of Eliza framework resources. The channel also touched on governance structure, with discussions about token holder metrics and the relationship between token ownership and contribution to the ecosystem. Several community members shared their professional backgrounds and skills they could contribute to the project.\n\n## 2. FAQ\nQ: How can we update stickers with the new hat logo? (asked by Patt) A: Use the sticker URLs provided by Jin and the assets from the brandkit repository (answered by jin)\nQ: What are the token thresholds for different roles? (asked by Kiwiana) A: For ai16z: 100k for partner role, 10k for associate; For degenai: 1,000,000 for Partner role, 100,000 for hoplite role (answered by liveinthemoment)\nQ: Is Eliza Studios an official core project? (asked by Smedroc - Street urchin @ ai16z) A: Yes, it's getting set up and is owned by Eliza Labs (answered by Elijah Madonia)\nQ: Where can we find metrics about the DAO? (asked by MicoM.ron) A: There's a Dune chart available (answered by jin)\nQ: What's the best way to swap BTC/SOL? (asked by Odilitime) A: sideshift.ai or changenow.io (answered by 1337pingu and Supertramp)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Patt | Context: Needed sticker files for updating with new hat logo | Resolution: Jin provided URLs to Discord sticker files and brandkit repository\nHelper: liveinthemoment | Helpee: Kiwiana | Context: Needed information about token thresholds for different roles | Resolution: Provided specific token amounts required for each role level\nHelper: MicoM.ron | Helpee: jin | Context: Newsletter creation | Resolution: Shared a newsletter template via DM to help kickstart the project\nHelper: Patt | Helpee: Community | Context: Updating emojis and stickers with new hat design | Resolution: Successfully updated and submitted them to the designated channel\n\n## 4. Action Items\nType: Technical | Description: Update all Discord emojis and stickers with the new taped hat logo | Mentioned By: jin\nType: Technical | Description: Create memes using the new stickered logo | Mentioned By: jin\nType: Documentation | Description: Update the awesome-eliza GitHub repository with new ecosystem projects | Mentioned By: jin\nType: Documentation | Description: Create a newsletter for the community | Mentioned By: jin\nType: Documentation | Description: Create a public webpage showing metrics about partners, associates, and token holders | Mentioned By: MicoM.ron\nType: Feature | Description: Establish a team to execute the newsletter | Mentioned By: MicoM.ron",
"messageCount": 205,
"userCount": 44
},
{
"channelId": "1318770424632311930",
"channelName": "tokenomics",
"summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion focused on partnership strategies and tokenomics for AI16Z. Shaw shared a document outlining a partnership approach emphasizing value accrual, suggesting projects that donated 10% to the treasury could be rewarded as they buy-and-send-to-DAO AI16Z tokens, creating steady buy pressure without dumping. The community debated how to structure these partnerships, with st4rgard3n highlighting that distribution and attention are the primary values AI16Z offers to partners. Several members discussed the need for a clear standard operating procedure for potential partners.\n\nTechnical discussions included market-making strategies for token launches, with yikesawjeez sharing detailed information about Principal Market Makers (PMMs) and Designated Market Makers (DMMs), suggesting that providing liquidity in exchange for call options could be mutually beneficial if implemented on-chain. There were concerns about keeping tokenomics discussions private to prevent competitors from copying ideas before implementation. Members emphasized the need for advanced game theory and mathematical approaches to tokenomics, with suggestions to involve PhD-level experts.\n\nThe community also discussed the challenges partners face when donating 10% of tokens, including difficulties raising capital and securing market-making deals, which presents an opportunity for AI16Z to facilitate these processes for partners.\n\n## 2. FAQ\nQ: How can we reward teams who already donated 10% to treasury? (asked by shaw) A: We can work something out to reward them as they buy-and-send-to-dao AI16Z tokens, creating steady buy pressure without dumping (answered by shaw)\nQ: Should we have a community website that displays all the projects? (asked by MonteCrypto) A: Yes, but there's debate about whether it should have standards/curation or just disclaimers (answered by DorianD and 0xMatt)\nQ: Why is asking for 10% not really a lot? (asked by DorianD) A: Because there are ongoing maintenance and support costs that big organizations understand (answered by DorianD)\nQ: How can we make partnerships more mutually beneficial? (asked by yikesawjeez) A: By setting up market maker services for liquidity to help reduce negative price impact on token launches (answered by yikesawjeez)\nQ: What's the status of the tokenomics document? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: Unanswered\n\n## 3. Help Interactions\nHelper: yikesawjeez | Helpee: Community | Context: Lack of understanding about market maker structures for token launches | Resolution: Shared detailed information about Principal Market Makers (PMMs) and Designated Market Makers (DMMs) business models, including loan structures and engagement terms\nHelper: st4rgard3n | Helpee: Community | Context: Unclear partnership strategy | Resolution: Explained that distribution and attention are AI16Z's primary currencies and the main incentives for partners\nHelper: jin | Helpee: Community | Context: Need for filtering quality contributors | Resolution: Shared M3 community gatekeeping approach using a quest system that filters people based on their ability to document work\n\n## 4. Action Items\nType: Technical | Description: Develop a system for providing market maker services to partner projects to help with token launches | Mentioned By: yikesawjeez\nType: Technical | Description: Create a mechanism for projects to buy-and-send-to-DAO AI16Z tokens as a way to receive rewards | Mentioned By: shaw\nType: Technical | Description: Implement on-chain liquidity provision in exchange for call options | Mentioned By: yikesawjeez\nType: Documentation | Description: Create a clear standard operating procedure for potential partners | Mentioned By: st4rgard3n\nType: Documentation | Description: Complete and release the Tokenomics document | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nType: Feature | Description: Develop a community website to display partner projects with appropriate disclaimers | Mentioned By: MonteCrypto\nType: Feature | Description: Create a curation system or community notes feature for the project listing website | Mentioned By: MonteCrypto and 0xMatt\nType: Technical | Description: Establish a private group for advanced tokenomics discussions to prevent copying | Mentioned By: DorianD and yardy",
"messageCount": 109,
"userCount": 16
},
{
"channelId": "1301363808421543988",
"channelName": "\ud83e\udd47-partners",
"summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary:\nThe discussion primarily revolves around tokenomics, revenue sharing models, and ecosystem development for the ai16z project. Shaw expresses dissatisfaction with the current tokenomics model that relies heavily on a launchpad approach, arguing that \"there are 20 launchpads using eliza already\" and that a more sustainable model is needed. He advocates for revenue sharing mechanisms that create buy pressure for the token. There's significant discussion about how to align incentives between the DAO and projects building on the ElizaOS framework, with proposals for projects to contribute a percentage of their revenue to buy ai16z tokens. The team is also working on rebranding efforts, with discussions about changing the ticker symbol and server name. DegenAI development is mentioned, with Shaw noting that he had to replace the team with \"aligned PM and devs who are on full time payroll.\" The partners also discuss the relationship between ai16z and DegenAI tokens, debating how benefits should be distributed between holders of each. Technical updates include the release of an ElizaOS whitepaper, integration with robots, and various partnerships with projects like Story Protocol and Polygon.\n\n## 2. FAQ:\nQ: What is the current tokenomics plan for ai16z? (asked by shaw) A: Shaw proposes moving beyond just a launchpad model to focus on revenue sharing mechanisms that create buy pressure for the token.\nQ: Are associates allowed to read-only this chat? (asked by crac) A: hildi and Dragonbutt confirmed it requires 10k tokens to be an associate.\nQ: Is there an explainer or FAQ on hand for DAO sales/model? (asked by Smore) A: jin mentioned tokenomics docs will have it when completed.\nQ: What's the requirement for being an associate? (asked by crac) A: 10k tokens according to hildi and Dragonbutt.\nQ: What's happening with DegenAI development? (asked by NkT) A: Shaw mentioned replacing the team with aligned PM and devs on full payroll, and they're working on a website and trading functionality.\nQ: How will projects in the ecosystem contribute value back to ai16z? (asked by shaw) A: Shaw proposed a model where 10% of project revenue goes to buying ai16z tokens.\nQ: What is the relationship between ai16z and DegenAI tokens? (asked by yikesawjeez) A: Ongoing discussion with some arguing for equal benefits for holders of both tokens, while others suggest prioritizing ai16z.\nQ: Is aixvc (formerly pmairca) getting its own token? (asked by Burtiik) A: shakejr clarified that aixvc will use ai16z as its token.\nQ: Who is currently leading the DegenSpartan project? (asked by Red40) A: Skely appears to be leading it, though there was some confusion about team changes.\nQ: What is the plan for ElizaOS robots? (asked by anon) A: A partnership was announced for ElizaOS to be integrated into physical robots, with preorders at $420k.\n\n## 3. Help Interactions:\nHelper: jin | Helpee: zocktay | Context: Explaining how to use the tip bot for tipping contributors | Resolution: Jin demonstrated the command and zocktay successfully tipped jin.\nHelper: jin | Helpee: Smore | Context: Creating a document to track ai16z lore and history | Resolution: Jin provided a hackmd.io template and Smore added content about the project's history.\nHelper: witch | Helpee: namaissur | Context: Discussion about LP positions for treasury tokens | Resolution: Witch directed namaissur to previous discussions in the tokenomics channel about LP arrangements.\nHelper: . | Helpee: Saori | Context: Access to the eliza.gg GitHub repository for documentation | Resolution: Provided GitHub access and offered assistance.\nHelper: jin | Helpee: multiple partners | Context: Explaining the rebrand and server name change | Resolution: Jin changed the server name and provided context about the rebranding efforts.\nHelper: Burtiik | Helpee: multiple partners | Context: Sharing the hat overlay tool for profile pictures | Resolution: Shared the link to eliza.gg/hat for partners to add hats to their profile pictures.\n\n## 4. Action Items:\nTechnical: Implement revenue sharing mechanisms for projects building on ElizaOS | Description: Create a system where projects contribute a percentage of revenue to buy ai16z tokens | Mentioned By: shaw\nTechnical: Develop V2 of ElizaOS | Description: Shaw mentioned pushing a basic V2 that is still \"bare bones\" | Mentioned By: shaw\nTechnical: Fix Elizas.world data pipeline | Description: Data pipeline was fixed and running smoothly | Mentioned By: timshel\nDocumentation: Create a document listing major lore events in ai16z history | Description: Compile significant events and milestones for the project | Mentioned By: jin\nDocumentation: Update tokenomics documentation | Description: Complete comprehensive tokenomics docs including revenue sharing model | Mentioned By: jin\nDocumentation: Create weekly newsletters to aggregate updates | Description: Develop automated news pipelines to keep community informed | Mentioned By: jin\nFeature: Implement automated weekly updates from agents | Description: Create system for agents to provide regular updates | Mentioned By: jin\nFeature: Develop NFT project for DegenAI | Description: Create waifus NFT as free mint for DegenAI holders | Mentioned By: shaw\nFeature: Integrate ElizaOS with robots | Description: Partnership to put ElizaOS in physical robot bodies | Mentioned By: anon\nFeature: Develop trust score system using ai16z tokens | Description: Create decentralized trust data market using trustDB scores | Mentioned By: DorianD",
"messageCount": 2010,
"userCount": 93
},
{
"channelId": "1313222089271939102",
"channelName": "3d-ai-tv",
"summary": "**Block Tank/Crypto Shark Tank** - A Shark Tank-style show where AI judges evaluate pitches. SM Sith Lord is developing this in PlayCanvas with a fully automated pipeline that generates episodes within 10 seconds of submission. The system uses AI to simulate both judges and pitcher interactions based on submitted pitch content.",
"messageCount": 402,
"userCount": 7
}
]
}
},
"ai_news_elizaos_daily_discord_md_2025-01-15": {
"filename": "2025-01-15.md",
"content": "# elizaOS Discord - 2025-01-15\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **ElizaOS v2 Development**: Shaw mentioned pushing a basic v2 that is still \"bare bones\" but represents progress toward the next generation of the framework.\n- **Agent Development Challenges**: Users discussed various implementation issues including embedding errors, plugin integration problems, Twitter client configuration, and database management.\n- **Knowledge Management**: Significant discussion about RAG (Retrieval Augmented Generation) implementation, with users struggling to understand how knowledge is stored, retrieved, and utilized by agents.\n- **Docker Deployment**: Several users reported issues with Docker builds across different environments (Mac, Windows, Linux), particularly on ARM64 architecture.\n- **Installation Issues**: Multiple users experienced problems with the @discord/opus dependency during installation, requiring workarounds.\n\n### Plugins & Integrations\n- **Twitter Integration**: Extensive troubleshooting of Twitter client issues, particularly with authentication, reply functionality, and rate limiting.\n- **Blockchain Data**: Discussion of plugins for accessing on-chain data, including plugin-evm and the Chainbase plugin for natural language querying of blockchain data.\n- **GitHub Integration**: Proposals for creating a GitHub client plugin for ElizaOS.\n- **Multimodal Generation**: Integration of BEATS SDK for multimodal generation, starting with AI-generated music.\n- **Robot Integration**: A partnership was announced for ElizaOS to be integrated into physical robots, with preorders at $420k.\n\n### AI Music Generation\n- **Suno Experimentation**: Dr. Neuro and boom explored AI music generation using Suno, sharing prompts and techniques for creating multi-voice rap songs with different personas.\n- **Prompt Engineering**: Discussion of strategies like adding \"AI\" to artist names to bypass copyright restrictions and creating structured prompts with defined roles for each voice.\n- **Integration Possibilities**: Exploration of integration between Eleven Labs voice profiles and Suno for multi-voice AI music generation.\n\n### Tokenomics & Business Model\n- **Revenue Sharing Model**: Shaw proposed moving beyond just a launchpad model to focus on revenue sharing mechanisms where projects contribute 10% of revenue to buy ai16z tokens, creating buy pressure.\n- **Market Making**: Detailed discussion about Principal Market Makers (PMMs) and Designated Market Makers (DMMs) for token launches, including loan structures and engagement terms.\n- **Token Utility**: Debate about the relationship between ai16z and DegenAI tokens, with some arguing for equal benefits while others suggested prioritizing ai16z.\n- **DeFAI Ecosystem**: Interest in the growing Decentralized Finance AI ecosystem, with discussions about metrics for measuring adoption and market growth.\n\n### Community & Branding\n- **Rebranding Efforts**: Discussions about changing the ticker symbol and server name, with jin implementing some changes during the conversation.\n- **New Logo**: Jin initiated a bounty for community members to update stickers and emojis with the new \"taped hat\" logo.\n- **Newsletter Creation**: Proposals for establishing a community newsletter, with MicoM.ron sharing templates and offering to help organize this effort.\n- **Documentation**: Jin created a bounty for maintaining and updating the \"awesome-eliza\" GitHub repository, which serves as a curated list of Eliza framework resources.\n\n### Project Showcase\n- **Block Tank/Crypto Shark Tank**: SM Sith Lord is developing a Shark Tank-style show where AI judges evaluate pitches, using PlayCanvas with a fully automated pipeline that generates episodes within 10 seconds of submission.\n- **Trading Bots**: Several users discussed developing autonomous trading agents with wallet security features.\n- **Social Media Agents**: Multiple implementations of Twitter-integrated agents were shared and discussed.\n\n## Key Questions & Answers\n\n### Technical Questions\n- **Q**: Do you need a good PC to run more complex AI agents? \n **A**: Depends on what you're building but any decent laptop can handle most agents (BOSSU)\n\n- **Q**: How to integrate an agent into Twitter? \n **A**: Check out agent dev school on YouTube and hit the coders channel for Twitter integration help (BOSSU)\n\n- **Q**: Do I need to know how to code to create my own AI agent on Eliza OS? \n **A**: Yes and no. Depends what you want to do with it (Dragonbutt)\n\n- **Q**: Where can I host Eliza? \n **A**: For hosting Eliza check out AWS or DigitalOcean, head to coders channel for more tech details (BOSSU)\n\n- **Q**: How can I make my agent access onchain data? \n **A**: Use plugins like plugin-evm or GOAT plugin (adonisabril)\n\n- **Q**: How can I fix the \"Cannot generate embedding: Memory content is empty\" error? \n **A**: Clear your cache and database file, ensure OpenAI embeddings are configured (Simz)\n\n- **Q**: How do I structure knowledge for effective RAG implementation? \n **A**: Break knowledge into concise lines with specific keywords for embedding (MonteCrypto)\n\n### Tokenomics Questions\n- **Q**: What are the token thresholds for different roles? \n **A**: For ai16z: 100k for partner role, 10k for associate; For degenai: 1,000,000 for Partner role, 100,000 for hoplite role (liveinthemoment)\n\n- **Q**: Is there a benefit from holding 10,000 AI16Z? \n **A**: 10k ai16z tokens lets you see in some of the partner(100k ai16z tokens) chat but you can't type or react (Dragonbutt)\n\n- **Q**: How can we reward teams who already donated 10% to treasury? \n **A**: We can work something out to reward them as they buy-and-send-to-dao AI16Z tokens, creating steady buy pressure without dumping (shaw)\n\n- **Q**: Why is asking for 10% not really a lot? \n **A**: Because there are ongoing maintenance and support costs that big organizations understand (DorianD)\n\n- **Q**: Is aixvc (formerly pmairca) getting its own token? \n **A**: aixvc will use ai16z as its token (shakejr)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Helper**: MonteCrypto | **Helpee**: 0xLabsTheCoder \n **Context**: Understanding how knowledge and RAG work in Eliza \n **Resolution**: Explained that knowledge should be fragmented into short, concise lines with unique keywords for effective embedding and retrieval\n\n- **Helper**: Simz | **Helpee**: tony \n **Context**: Fixing \"Cannot generate embedding: Memory content is empty\" error \n **Resolution**: Suggested clearing cache and database files, and ensuring OpenAI embeddings are properly configured\n\n- **Helper**: zadkielm | **Helpee**: 0xChainBrain \n **Context**: Finding REST API endpoint for direct agent communication \n **Resolution**: Pointed to lib/api.ts where the endpoint is defined\n\n- **Helper**: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f | **Helpee**: Jessy | Unicake\ud83e\udd84 \n **Context**: EVM private key format \n **Resolution**: Suggested including 0x prefix in the private key\n\n- **Helper**: Neil Jones | **Helpee**: 0xLisanAlGaib \n **Context**: Fixing better-sqlite3 Node.js version mismatch \n **Resolution**: Provided commands to rebuild better-sqlite3 or reinstall requirements\n\n### Community Building\n- **Helper**: jin | **Helpee**: Smore \n **Context**: Creating a document to track ai16z lore and history \n **Resolution**: Jin provided a hackmd.io template and Smore added content about the project's history\n\n- **Helper**: jin | **Helpee**: zocktay \n **Context**: Explaining how to use the tip bot for tipping contributors \n **Resolution**: Jin demonstrated the command and zocktay successfully tipped jin\n\n- **Helper**: Burtiik | **Helpee**: multiple partners \n **Context**: Sharing the hat overlay tool for profile pictures \n **Resolution**: Shared the link to eliza.gg/hat for partners to add hats to their profile pictures\n\n- **Helper**: Dr. Neuro | **Helpee**: boom \n **Context**: Creating multi-voice AI rap songs in Suno \n **Resolution**: Shared technique of adding \"AI\" to artist names to bypass copyright restrictions and using structured prompts with defined roles\n\n## Action Items\n\n### Technical\n- Fix embedding errors when using different embedding models with Supabase (NoBody | SUIRISE)\n- Implement proper error handling for Twitter client (GOGOGO\u26d3\ud83d\udca5)\n- Fix evaluator validation logic - evaluators don't trigger unless alwaysRun is set to true (bifkn)\n- Fix Docker build issues on ARM64 architecture (Tobias | QDEV)\n- Fix installation issues with @discord/opus dependency (jeremyboise)\n- Create an AI bounty agent to scan approved PRs and attribute Discord roles based on coding effort (MonteCrypto)\n- Fix JSON structure in Howieduhzit tool to properly create arrays of strings (Dreygo)\n- Integrate Chainbase plugin for natural language querying of blockchain data (Lil Lowkey | Chainbase)\n- Integrate BEATS SDK for multimodal generation (starting with songs) (ryoh)\n- Implement revenue sharing mechanisms for projects building on ElizaOS (shaw)\n- Develop V2 of ElizaOS (shaw)\n- Fix Elizas.world data pipeline (timshel)\n- Integrate technical analysis module into Neuro runtime (anomalyagentic)\n- Combine sentiment analysis from Twitter with technical analysis for trading signals (anomalyagentic)\n- Explore integration between Eleven Labs voice profiles and Suno (boom)\n- Develop a system for providing market maker services to partner projects (yikesawjeez)\n- Create a mechanism for projects to buy-and-send-to-DAO AI16Z tokens (shaw)\n- Implement on-chain liquidity provision in exchange for call options (yikesawjeez)\n\n### Documentation\n- Create weekly newsletters to prevent announcements from getting lost (jin)\n- Document tokenomics and token utility mechanisms (Burtiik)\n- Add details about target users configuration (SMA)\n- Improve plugin development documentation (MonteCrypto)\n- Update EVM private key format requirements (Jessy | Unicake\ud83e\udd84)\n- Create guide for knowledge structuring (0xLabsTheCoder)\n- Create a document listing major lore events in ai16z history (jin)\n- Update tokenomics documentation with revenue sharing model (jin)\n- Create a clear standard operating procedure for potential partners (st4rgard3n)\n- Complete and release the Tokenomics document (\ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create a public webpage showing metrics about partners, associates, and token holders (MicoM.ron)\n- White Paper and Tokenomics documentation needed for DegenSpartan (NkT)\n\n### Features\n- Add ability for AI agents to search and post on Reddit (uniqueobject)\n- Create an agent for autonomous trading with wallet security (kobra)\n- Develop AI agent for improving and backtesting TradingView scripts (FutureStocks)\n- Implement local TTS option as alternative to ElevenLabs (Abderahman)\n- Create GitHub client plugin for ElizaOS (suso)\n- Implement multi-agent interaction system (0xLabsTheCoder)\n- Add API for direct agent communication (0xChainBrain)\n- Develop wallet protection mechanism (kobra)\n- Create global/shared memories system (matthias_ztlr)\n- Improve Twitter client reply functionality (PhyoPhyoLay)\n- Create a cloud-based test bed for AI agents (Hidden Forces)\n- Develop AI beatmaker assistant for real-time music production (boom)\n- Explore capability for Eliza to create 3D objects in Blender (judasz)\n- Implement NFT project for DegenAI (shaw)\n- Integrate ElizaOS with robots (anon)\n- Develop trust score system using ai16z tokens (DorianD)\n- Create a community website to display partner projects (MonteCrypto)\n- Create a curation system for the project listing website (MonteCrypto and 0xMatt)\n- Implement automated weekly updates from agents (jin)"
},
"github_summaries_daily_2025-01-16": {
"filename": "2025-01-16.md",
"content": "# ElizaOS Daily Update (Jan 16, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the testing framework and improving client functionalities. Significant progress was made in adding tests for various clients, enhancing S3 flexibility, and refining knowledge handling. Additionally, several bug fixes were implemented to improve stability and performance.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Testing Enhancements\n- Added tests for the GitHub client to ensure functionality and reliability ([#2407](https://github.com/elizaOS/eliza/pull/2407)).\n- Implemented tests for the Slack client and reorganized existing tests into a new `__tests__` directory ([#2404](https://github.com/elizaOS/eliza/pull/2404)).\n- Introduced tests for the Solana plugin to enhance coverage ([#2345](https://github.com/elizaOS/eliza/pull/2345)).\n\n### Feature Improvements\n- Enhanced S3 configuration flexibility, allowing integration with providers like DigitalOcean Spaces and Cloudflare R2 ([#2379](https://github.com/elizaOS/eliza/pull/2379)).\n- Improved RAG knowledge handling by supporting double-byte characters and simplifying knowledge loading ([#2351](https://github.com/elizaOS/eliza/pull/2351)).\n- Added a new Instagram client to facilitate media posting and session management ([#1964](https://github.com/elizaOS/eliza/pull/1964)).\n\n### Bug Fixes\n- Resolved lint errors and improved code quality ([#2400](https://github.com/elizaOS/eliza/pull/2400)).\n- Fixed issues causing app crashes when the `REMOTE_CHARACTER_URLS` environment variable was undefined ([#2384](https://github.com/elizaOS/eliza/pull/2384)).\n- Corrected a typo in the import statement for the Solana AgentKit plugin ([#2370](https://github.com/elizaOS/eliza/pull/2370)).\n\n## CLOSED ISSUES\n\n### Testing and Structure Improvements\n- Closed issues related to adding tests for the GitHub client and Slack client, ensuring better test coverage as part of the project restructuring ([#2406](https://github.com/elizaOS/eliza/issues/2406), [#2403](https://github.com/elizaOS/eliza/issues/2403)).\n\n### Bug Resolutions\n- Resolved issues regarding unset variables in Docker Compose and related bugs, enhancing the stability of the application ([#2387](https://github.com/elizaOS/eliza/issues/2387)).\n\n## NEW ISSUES\n\n### Testing Gaps\n- Identified the need for additional tests for the Solana plugin to ensure its reliability and performance ([#2344](https://github.com/elizaOS/eliza/issues/2344)).\n\n### Functionality Challenges\n- Reported issues with Twitter authentication on AWS EC2 instances, indicating potential deployment challenges ([#2372](https://github.com/elizaOS/eliza/issues/2372)).\n- Highlighted a bug in the development script that prevents character loading, which requires urgent attention ([#2381](https://github.com/elizaOS/eliza/issues/2381))."
},
"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\\\"](\\\"https://github.com/user-attachments/assets/03b9b7fe-85fe-407f-a0ff-dbeeea73f1e1\\\")
\\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\\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\\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\\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\\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