{
  "ai-news": {
    "elizaos": {
      "discord_md_last_3_days": [
        {
          "filename": "2025-04-22.md",
          "content": "# elizaOS Discord - 2025-04-22\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform Status\n- **Maintenance Mode**: The auto.fun website is currently down for maintenance and upgrades\n- **Database Improvements**: The team is upgrading the database and implementing scaling solutions to handle increased load\n- **New Features**: Several new features are being added during this downtime\n- **Timeline**: No specific ETA provided, but Kenk mentioned \"the team has completed the bulk of the upgrades\"\n- **Testing Issues**: During brief testing periods, users reported multiple bugs including missing chart data, transaction information, and holder data for certain tokens\n\n### ElizaOS V2 Development\n- **Release Timeline**: Users are anticipating the V2 release which was expected this week\n- **Migration Challenges**: Developers are struggling with migration from older versions to v2-develop branch\n- **Documentation Gaps**: Current documentation doesn't fully align with code in v2-develop branch\n- **Plugin Compatibility**: Issues reported with plugin installation and compatibility between v1 and v2\n- **Local Models**: Some users experiencing errors when trying to use local models instead of OpenAI\n\n### Token Economics & Verification\n- **Token Gating**: Jin acknowledged issues with token verification and added fixing it to their todo list\n- **Verification Alternatives**: Matrica was suggested as a potential alternative to Collab.land despite cost concerns\n- **Partner Requirements**: Discussion about potentially raising the 1 million Spartan threshold for partners\n- **AI Compute Funding**: Proposals for token economics on auto.fun that could fund AI compute resources by allocating a percentage of fees\n\n### Technical Innovations\n- **Discord Summarization**: Jin shared progress on a Discord summarization pipeline creating structured data for LLM ingestion\n- **Dynamic LLM Switching**: Discussion about dynamically swapping LLM models based on evaluation criteria\n- **Multi-Agent Setup**: Questions about running multiple agent characters on the same machine\n- **Social Media Integration**: Developers seeking solutions for configuring agents to handle Twitter replies and retweets\n\n## Key Questions & Answers\n\n**Q: Will the eliza V2 be delayed or still this week?**  \nA: No direct answer provided, though Odilitime mentioned \"launch is waiting on some plugins work I'm doing\"\n\n**Q: Is the auto.fun site being fixed for bugs or new upgrades?**  \nA: \"It's for an upgrade but whilst it is maintenance mode some of the UI bugs have been amended\" (Kenk)\n\n**Q: Is there a way to view the builder demos recording?**  \nA: \"They'll be added onto https://www.youtube.com/@ElizaOSDeveloper soon\" (Kenk)\n\n**Q: Is the PDF plugin currently working?**  \nA: \"Yes, it's available at github.com/elizaos-plugins/plugin-pdf and was updated 2 weeks ago\" (Kenk)\n\n**Q: Does the auto.fun site actually create Eliza agents for people?**  \nA: \"It links out to fleek, but there may be things in the works from the labs team and community partners\" (yikesawjeez)\n\n**Q: How long will the auto.fun maintenance take?**  \nA: No specific timeframe provided, but Kenk mentioned \"team has completed the bulk of the upgrades, we'll update shortly\"\n\n**Q: Is it possible to create a screen with statistical indicators on auto.fun?**  \nA: \"I don't see why not but not sure if this will be something the team does short term\" (Kenk)\n\n## Community Help & Collaboration\n\n1. **Token Migration Assistance**\n   - Helper: Kenk | Helpee: Vaunted\n   - Context: User needed token migration from auto to raydium\n   - Resolution: Kenk noted the request and confirmed team would manually migrate it\n\n2. **Channel Access Resolution**\n   - Helper: Kenk | Helpee: Multiple users (kimbo, zocktay)\n   - Context: Users lost access to certain channels including announcements\n   - Resolution: Kenk manually added verified tags to restore access\n\n3. **PDF Plugin Guidance**\n   - Helper: Kenk | Helpee: Beja\n   - Context: Looking for PDF plugin availability\n   - Resolution: Provided GitHub link to the plugin and confirmed it was recently updated\n\n4. **Token Import Clarification**\n   - Helper: accelxr | Helpee: kakali8377\n   - Context: Token created on April 22 couldn't be queried and traded on the website\n   - Resolution: accelxr added it to the import list, will be visible when site is up\n\n5. **Development Environment Setup**\n   - Helper: Kenk | Helpee: lantianlaoli\n   - Context: Looking for quickstart guide\n   - Resolution: Provided link to eliza.how/docs/quickstart and mentioned need to use v2-develop branch\n\n## Action Items\n\n### Technical\n1. **Fix token gating for community verification** (Mentioned by jin)\n2. **Complete plugins work required for V2 launch** (Mentioned by Odilitime)\n3. **Fix image processing in v2-develop branch** (Mentioned by odilitime)\n4. **Fix SQL and bootstrap plugin setup in v2 quickstart** (Mentioned by odilitime)\n5. **Fix \"failed to claim fees\" functionality on auto.fun** (Mentioned by Xyness)\n6. **Fix list view interface bug on auto.fun** (Mentioned by HoneyBadger)\n7. **Fix sort by highest volume functionality** (Mentioned by HoneyBadger)\n8. **Migrate specific token to Raydium** (Mentioned by Vaunted)\n9. **Fix token data display issues** (Mentioned by YourDadsFriendSteve)\n10. **Remove testnet tokens from production** (Mentioned by Pyroman)\n11. **Review and merge Zilliqa plugin PR** (Mentioned by mtbc)\n12. **Database upgrade and scaling issues resolution** (Mentioned by Kenk, eskender.eth)\n\n### Documentation\n1. **Update documentation to match current code in v2-develop branch** (Mentioned by lantianlaoli)\n2. **Create tutorial for new project creation and first steps using v2** (Mentioned by odilitime)\n3. **Document how to load \"Eddy the ElizaOS Wizard Boy\" character** (Mentioned by odilitime)\n4. **Review and provide feedback on Town Hall outline document** (Mentioned by vincentpaul)\n5. **Review and provide feedback on pre-Town Hall survey** (Mentioned by vincentpaul)\n6. **Update X account link in Binance alpha** (Mentioned by human_nalejzpa)\n7. **Communicate site status updates** (Mentioned by eskender.eth)\n\n### Feature\n1. **Add support for agent to reply to Twitter replies of target accounts** (Mentioned by odilitime)\n2. **Implement prevention of agent selecting \"None\" action on repeated questions** (Mentioned by happylol123)\n3. **Implement another holder verification round to identify FUD spreaders** (Mentioned by Zolo)\n4. **Consider raising partner minimum requirements from 1M Spartan** (Mentioned by HoneyBadger)\n5. **Add statistical indicators screen to auto.fun** (Mentioned by Moliza)\n6. **Implement token economics on auto.fun to fund AI compute resources** (Mentioned by DorianD)\n7. **Add dynamic LLM model switching** (Mentioned by DorianD)\n8. **Integrate RAG/AI agent with Discord summarization** (Mentioned by jin)\n9. **Implement anti-snipe mechanism for auto.fun** (Mentioned by Zolo)\n10. **Improve partner benefits** (Mentioned by vincentpaul)\n11. **Implement wallet connect functionality for agents** (Mentioned by odilitime)\n12. **Support for OpenAI in plugin development** (Mentioned by lantianlaoli)"
        },
        {
          "filename": "2025-04-21.md",
          "content": "# elizaOS Discord - 2025-04-21\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform Status and Issues\n- **Maintenance Mode**: Auto.fun is currently in maintenance mode for upgrades and UI bug fixes\n- **Launch Performance**: The team reported that auto.fun's initial release was successful by internal metrics despite technical challenges\n- **Technical Issues**: Several users reported problems with token creation where tokens were created but liquidity pools weren't properly established\n- **Indexing Problems**: Early tokens created during or shortly after launch experienced indexing issues requiring manual migration by the team\n- **Security Incident**: Shaw's Twitter account was compromised, with the attacker creating a fraudulent token called \"COO\" on Pump.fun\n\n### Token Economics and Platform Features\n- **Fee Structure**: Auto.fun implements a 90/10 split for token creators and the platform respectively\n- **Bonding Curve Mechanism**: Tokens migrate to Raydium after reaching 85 SOL in the curve (approximately 60k market cap)\n- **AI16z Token**: Discussions about the relationship between auto.fun and the AI16z token, with some users expressing concern about token price impact\n- **Tokenomics**: Team member Kenk mentioned upcoming communications about expanded tokenomics beyond buyback & DAO functions\n\n### ElizaOS Development\n- **ElizaV2 Anticipation**: Users are looking forward to ElizaV2's release, hoping it will generate market optimism\n- **Technical Challenges**: Developers discussed plugin development, database integration, and deployment problems\n- **CSP Errors**: Several users encountered Content Security Policy errors when running ElizaOS v2 on Windows machines\n- **LLM Support**: Questions about DeepSeek compatibility and custom OpenAI-compatible providers\n- **Multiple Characters**: Developers inquired about running multiple AI characters on a single machine\n\n### Community Projects and Partnerships\n- **Weekly Builder Demos**: The team hosts weekly builder demos for ElizaOS projects, with recordings available on YouTube\n- **Project Diversity**: Kenk shared a list of projects using ElizaOS across gaming, DeFi, marketplaces, and social applications\n- **Launch Partners**: Auto.fun launch partners are ready to deploy but waiting for platform stability before marketing begins\n- **Custom Plugins**: Developers shared their custom plugins, including a MIDI communication plugin\n\n## Key Questions & Answers\n\n**Q: Is auto.fun website down?** (asked by GIgor_021)  \nA: The site is in maintenance mode for upgrades and UI bug fixes (answered by Kenk)\n\n**Q: How can I view the weekly builder demos recording?** (asked by CoinPapi)  \nA: They'll be added to https://www.youtube.com/@ElizaOSDeveloper (answered by Kenk)\n\n**Q: Why can't I see or trade my token after creation?** (asked by multiple users)  \nA: There was an indexing issue with tokens created early during launch. The team is working on fixing these tokens by manually importing them. (answered by accelxr)\n\n**Q: When does a token migrate from the bonding curve?** (asked by Pyroman)  \nA: When it reaches 85 SOL in the bonding curve, approximately 60k market cap. (answered by accelxr)\n\n**Q: What is the fee split for token creators?** (asked by Xyness)  \nA: It's a 90/10 split for the token owner and the platform respectively. (answered by Borko)\n\n**Q: Is the PDF plugin currently working?** (asked by Beja)  \nA: Yes, it's available at github.com/elizaos-plugins/plugin-pdf and was updated 2 weeks ago (answered by Kenk)\n\n**Q: What happens to tokens created using the leaked developer link?** (asked by multiple users)  \nA: These tokens cannot be recovered as they were created on a different contract than the official one. (answered by accelxr)\n\n**Q: Are there any agentic features in the current auto.fun release?** (asked by 0xFastly)  \nA: This is the core of it at the moment, the platform will be used as part of the DX for agent creation of V2 (answered by Kenk)\n\n**Q: Why is the Jupiter error happening on percentage-based sells?** (asked by accelxr)  \nA: It appears to be related to too many decimals in the calculations. (answered by accelxr)\n\n## Community Help & Collaboration\n\n### Token Migration and Recovery\n- **Helper**: accelxr | **Helpee**: NotYourBudi  \n  *Context*: User created a token but no LP was created  \n  *Resolution*: Identified as an indexing error that would be resolved\n\n- **Helper**: accelxr | **Helpee**: FatalPie  \n  *Context*: Token \"eddy\" was stuck in migration for 2 days  \n  *Resolution*: Successfully migrated the token\n\n- **Helper**: accelxr | **Helpee**: uloze  \n  *Context*: User had multiple failed token creation attempts  \n  *Resolution*: Identified which tokens were recoverable and added them to import list\n\n### Technical Support\n- **Helper**: Kenk | **Helpee**: BowTiedBlueFin  \n  *Context*: Needed to use custom OpenAI API compatible provider  \n  *Resolution*: Suggested creating a new plugin and provided documentation links\n\n- **Helper**: Zarathustra | **Helpee**: FlipWhale  \n  *Context*: Issues with plugin-image-generation  \n  *Resolution*: Suggested attending ElizaOS office hours for Q&A with Shaw\n\n- **Helper**: accelxr | **Helpee**: yikesawjeez  \n  *Context*: Jupiter errors on percentage-based sells (25%, 50%, 75%)  \n  *Resolution*: Identified the issue as too many decimals in calculations, suggested removing the last number to fix and fetch properly\n\n### Community Engagement\n- **Helper**: Kenk | **Helpee**: [elizaos] <santgr>  \n  *Context*: User unable to see auto.fun channels history  \n  *Resolution*: Added verified tag to user's profile to grant access\n\n- **Helper**: yikesawjeez | **Helpee**: iprintmoney  \n  *Context*: Helping navigate a hidden puzzle/game on tournament.x-ware.online  \n  *Resolution*: Successfully guided user through accessing a hidden AI character interaction\n\n## Action Items\n\n### Technical Tasks\n- Fix UI bugs in auto.fun during maintenance mode (Mentioned by Kenk)\n- Resolve indexing issue impacting token migrations (Mentioned by eskender.eth)\n- Fix liquidity pool creation for affected tokens (Mentioned by noj)\n- Complete database upgrade for platform stability (Mentioned by Kenk)\n- Fix claim fees button that's currently broken (Mentioned by yikesawjeez)\n- Fix Jupiter error on price detection for percentage-based sells (Mentioned by yikesawjeez)\n- Fix CSP issues with V2 on Windows machines (Mentioned by [elizaos] <santgr>)\n- Fix build issues in v2-develop branch (Mentioned by lantianlaoli)\n- Add DeepSeek support to V2 (Mentioned by [elizaos] <santgr>)\n- Fix agent creation REST endpoint issue (Mentioned by [elizaos] <santgr>)\n- Fix sorting filters (bonding, age) not working correctly (Mentioned by Curtisdonthurtus)\n- Fix list view UI where left tab selection disappears (Mentioned by HoneyBadger)\n- Fix volume and holder data sometimes showing as zero (Mentioned by HoneyBadger)\n- Review and merge pull request for plugin-zilliqa (Mentioned by mtbc)\n\n### Feature Requests\n- Implement bounty rewards for fun token (Mentioned by Rick)\n- Support for custom OpenAI-compatible LLM providers (Mentioned by BowTiedBlueFin)\n- Configure agents to reply to replies of target accounts (Mentioned by [elizaos] <santgr>)\n- Prevent agent selecting \"None\" action on repeated questions (Mentioned by happylol123)\n- Implement agentic features in future platform versions (Mentioned by eskender.eth)\n- Add ability to include website information on token pages (Mentioned by 🧧ThanosDaSith24🧧)\n- Add two parameters for sorting (bonding and time, or bonding and MC) (Mentioned by Curtisdonthurtus)\n- Add bonding curve percentage to Telegram bot data (Mentioned by MONO)\n- Create statistical dashboard with platform metrics (Mentioned by Moliza)\n- Create mechanism for tokens to fund their own AI agents through fee allocation (Mentioned by DorianD)\n- Implement model switching capability for agents to dynamically swap LLMs (Mentioned by DorianD)\n\n### Documentation Needs\n- Upload builder demos to YouTube (Mentioned by Kenk)\n- Create tutorial for new project setup and first steps using v2 (Mentioned by [elizaos] <santgr>)\n- Provide clear explanation of token creation costs and calculations (Mentioned by 0xConsole)\n- Update messaging around \"locked\" status for tokens (Mentioned by shaw)\n- Share communications around tokenomics (Mentioned by Kenk)\n- Update language to clarify token mechanics to prevent confusion (Mentioned by yikesawjeez)"
        },
        {
          "filename": "2025-04-20.md",
          "content": "# elizaOS Discord - 2025-04-20\n\n## Overall Discussion Highlights\n\n### Auto.fun Launch and Technical Issues\n- **Platform Launch**: Auto.fun, a token launchpad platform developed by Shaw and team, was launched but experienced significant backend issues\n- **Technical Challenges**: The site went down multiple times due to high load, with users reporting tokens not showing up, migration delays, and price display problems\n- **Continuous Development**: The team has been on a 40+ hour dev call working to fix the issues\n- **Maintenance Mode**: The site was temporarily put into maintenance mode for updates\n- **First Successful Migration**: KRSK was identified as the first token that successfully migrated with 79 SOL added to LP\n- **Security Incident**: Shaw's Twitter account was compromised and used to promote a suspicious token called \"COO\"\n\n### Auto.fun Technical Details\n- **Bonding Curve Mechanism**: Uses 28 SOL initial virtual reserves; tokens graduate to Raydium at 113 SOL (85 SOL + 28 SOL virtual)\n- **LP Token Distribution**: 90/10 split between creators and Auto.fun\n- **Fee Structure**: 10% of bonded LP fees collected by the platform will be used to buyback $ai16z from the open market\n- **Token Verification**: Currently reserved for vetted companies with prior relationships; formal process coming when platform is more stable\n\n### ElizaOS Plugin Development\n- **Plugin Issues**: Users encountered problems with Discord and Telegram plugins, particularly around event handling and callbacks\n- **Database Errors**: Several users faced PostgreSQL relation errors when starting ElizaOS projects\n- **Custom LLM Integration**: Discussions about using custom LLM providers like Deepseek with ElizaOS\n- **CSP Issues**: Content Security Policy problems reported on Windows machines\n- **MIDI Plugin**: A user mentioned developing a MIDI plugin for agent communication\n\n### Future Developments\n- **V2 Launch**: Discussions about a potential V2 launch in the coming week\n- **Agentic Features**: Current Auto.fun release focuses on token and content creation, with agent features planned for V2\n- **Launch Partners**: Team mentioned they would be sharing information about launch partners in the coming days/weeks\n- **Marketing Push**: Planned to start after platform upgrades are completed\n\n## Key Questions & Answers\n\n**Q: How does the bonding curve work?**  \nA: Auto.fun uses a bonding curve with 28 SOL initial virtual reserves. When a coin reaches 113 SOL in reserves (85 SOL + 28 SOL virtual), it automatically graduates to Raydium with a 6 SOL flat fee.\n\n**Q: What is the fee structure for Auto.fun?**  \nA: The platform collects 10% of the bonded LPs fees, then will buyback $ai16z from the open market, to finally reinvest in ai16z LP to create deeper ecosystem liquidity.\n\n**Q: What happens to tokens created before the official launch?**  \nA: Tokens created using the leaked developer link (autoUm program) cannot be supported, while tokens created on the official platform with indexing issues will be fixed.\n\n**Q: What does \"locked\" status mean for tokens?**  \nA: The \"locked\" status indicates that the token's liquidity pool tokens have been successfully locked as part of a migration process.\n\n**Q: How do you get a verified tick on Auto.fun?**  \nA: Currently reserved for companies with prior relationships that have been vetted. A formal process will be released when the platform is more stable.\n\n**Q: What was causing the Jupiter integration errors?**  \nA: Too many decimals in calculations, which the team is working to fix.\n\n**Q: Why isn't Degenai included in the buyback mechanism?**  \nA: 1) Spartan already gets carry, 2) technical complexity of splitting fees across numerous buyback mechanisms, 3) it would confuse the ecosystem vs agent narrative.\n\n**Q: Is AI16z the native token for auto.fun?**  \nA: Some users speculated it might be, though others disagreed since anyone can access auto.fun without having AI16z token.\n\n**Q: Does eliza-v2 work with deepseek?**  \nA: You may need to create your own plugin.\n\n**Q: How do I fix the \"relation 'logs' does not exist\" error when starting the project?**  \nA: Drop pg instance -> drop volume.\n\n## Community Help & Collaboration\n\n1. **Token Migration Assistance**:\n   - Helper: accelxr | Helpee: joeyseoul | Context: Token stuck in migration for over 16 hours | Resolution: Manually migrated the token\n   - Helper: accelxr | Helpee: FatalPie | Context: Token \"Eddy\" stuck in migration for over 20 hours | Resolution: Successfully migrated the token\n\n2. **Technical Troubleshooting**:\n   - Helper: accelxr | Helpee: yikesawjeez | Context: Sell button not working for $WWF token | Resolution: Team identified the issue was related to decimal handling in Jupiter integration\n   - Helper: mortenssen | Helpee: mortenssen | Context: Database relation errors on startup | Resolution: Suggested dropping PostgreSQL instance and volume if running in Docker\n\n3. **Custom Integration Support**:\n   - Helper: Kenk | Helpee: BowTiedBlueFin | Context: Needed to use custom OpenAI API compatible base URL | Resolution: Suggested creating a new plugin or adding a new instance provider in env file\n   - Helper: Kenk | Helpee: mortenssen | Context: Using Deepseek LLM with ElizaOS | Resolution: Suggested creating a custom plugin and shared relevant documentation links\n\n4. **User Guidance**:\n   - Helper: jin | Helpee: Multiple users | Context: Users reporting tokens not showing up after creation | Resolution: Advised users to post in #support-auto-fun channel with details/contract address\n   - Helper: Mr G | Helpee: Pyroman | Context: User had questions about token migration and platform functionality | Resolution: Explained differences between importing and migrating tokens and how the platform works\n\n## Action Items\n\n### Technical\n- Fix backend issues causing auto.fun to go down under load (Mentioned by: shaw)\n- Fix token migration process for early tokens (Mentioned by: Multiple users)\n- Fix price display issues for tokens (Mentioned by: abhi_ironman)\n- Fix issue with created tokens not showing up (Mentioned by: casper, phetrusrodrigues)\n- Fix \"locked\" status for tokens where users can't sell (Mentioned by: noj)\n- Fix claim fees functionality and \"failed to claim fees\" error (Mentioned by: Xyness)\n- Fix Jupiter integration errors with decimal handling (Mentioned by: accelxr)\n- Fix how Discord plugin events are being subscribed to (Mentioned by: mortenssen)\n- Fix double callback issue in plugin-bootstrap (Mentioned by: mortenssen)\n- Fix database relation errors on startup (Mentioned by: mortenssen)\n- Fix CSP issues with V2 on Windows machines (Mentioned by: mortenssen)\n- Fix bonding filter accuracy (Mentioned by: Pyroman)\n- Fix the \"Install MyWebsite\" text when installing the site on mobile (Mentioned by: Patt)\n- Address security issues with team accounts after Shaw's Twitter was compromised (Mentioned by: eskender.eth)\n\n### Features\n- Implement bounty rewards for FUN token (Mentioned by: Rick)\n- Create a potential \"hit coin\" to generate interest in auto.fun (Mentioned by: Moliza)\n- Add ability to sort tokens by \"most filled\" to see which are close to bonding (Mentioned by: thatjpeg)\n- Create a community memecoin as a mascot for auto.fun (Mentioned by: wire)\n- Enable attaching newly generated images/videos directly to token-gated chat (Mentioned by: yardy)\n- Add support for posting random images from a folder (Mentioned by: TruffleSoul)\n- Add support for custom OpenAI API compatible providers (Mentioned by: BowTiedBlueFin)\n- Add Deepseek LLM support (Mentioned by: mortenssen)\n- Implement a technofeudalist DAO with token value backed by land (Mentioned by: Mr. Nucleus)\n- Add bonding curve percentage to Telegram bot data (Mentioned by: MONO)\n- Implement footer accessibility with infinite scroll (Mentioned by: Pyroman)\n- Add multiple parameter sorting (Mentioned by: Curtisdonthurtus)\n- Add more interactive filters (volume, age, verified, holders, etc.) (Mentioned by: Lucid)\n- Add disconnect wallet button (Mentioned by: yikesawjeez)\n\n### Documentation\n- Provide information on launch partners (Mentioned by: Kenk)\n- Provide status updates on AutoFun's X account (Mentioned by: HoneyBadger)\n- Establish customer support via AutoFun's X account (Mentioned by: HoneyBadger)\n- Clarify the token migration process and expected timeframes (Mentioned by: Multiple users)\n- Update messaging around \"locked\" status for tokens (Mentioned by: shaw)\n- Create clearer UI for fee claiming process (Mentioned by: accelxr)\n- Add website link option for token pages (Mentioned by: 🧧ThanosDaSith24🧧)\n- Release formal tokenomics article (Mentioned by: accelxr)\n- Create success stories of token launches for marketing (Mentioned by: hubert)\n- Establish formal verification process for tokens (Mentioned by: eskender.eth)"
        }
      ],
      "dev_md_last_3_days": [
        {
          "filename": "2025-04-22.md",
          "content": "# elizaOS Development Discord - 2025-04-22\n\n## Overall Discussion Highlights\n\n### Plugin Development\n- **Action Naming Conventions**: Plugin actions must have distinct names to avoid conflicts in the system\n- **UI Hosting**: Developers can host UIs within plugins, with the investment manager plugin (degen-intel) serving as an example\n- **Plugin Customization**: Multiple bootstrap plugins can be created by forking the plugin-bootstrap repository, allowing for customized message handling\n\n### Storage & Infrastructure\n- **Storacha MCP**: A decentralized storage solution for AI applications was discussed in detail, offering up to 5GB of free storage\n- **Storage Architecture**: Storacha implements a tiered approach with:\n  - Hot storage (Cloudflare R2) with 200-500ms TTFB SLA\n  - Warm storage (distributed node network with 3x replication) with 1-10s TTFB SLA\n  - Cold storage (Filecoin) for long-term archiving\n- **Encryption**: Storacha is implementing client-side encryption using LIT Protocol\n\n### Agent Development\n- **O3 Implementation**: Positive feedback about using o3 (likely OpenAI's o1-preview) for creating organization-specific agents\n- **Agent Structure**: Guidance provided on implementing agent configurations in CLI projects by translating YAML configs to CLI flags or environment variables\n- **Avatar Setup**: O3 avatars should be placed in the `/agents/your-agent-name/config.yaml` directory structure\n\n### Auto.fun Platform\n- **Vanity CAs**: Proposal to add a paid compute option to auto.fun for finding vanity CAs with a markup\n- **Social Media Integration**: Discussion about configuring Twitter agents to respond to replies of target accounts\n\n### Character.AI V2\n- **Platform Transition**: Users are encouraged to learn V2 despite its steeper learning curve, as it offers greater flexibility and control than V1\n- **Launch Status**: Clarification that V2 hasn't officially launched yet\n\n## Key Questions & Answers\n\n**Q: What if there are several actions from plugins with the same action name?**  \nA: Plugin actions need to have distinct names to avoid conflicts in the system.\n\n**Q: Is it possible to fork the plugin-bootstrap and trim down the messageReceivedHandler?**  \nA: Yes, multiple bootstrap plugins can be created now, allowing for customization.\n\n**Q: How are you handling encryption and access controls in Storacha?**  \nA: Encryption is in development using LIT Protocol with client-side encryption.\n\n**Q: How are you handling hot/cold storage transitions in Storacha?**  \nA: Detailed tiered approach with hot storage (R2), upcoming warm storage (distributed nodes), and cold storage (Filecoin) with specific performance targets.\n\n**Q: What's the latency like on retrieval from the hot nodes?**  \nA: Hot storage targets 200-500ms TTFB SLA, warm storage will have 1-10 second TTFB SLA.\n\n**Q: Is the agent structure for YAML configs usable with CLI projects?**  \nA: Yes, the agent structure works with CLI projects by translating YAML configs into appropriate CLI flags or environment variables.\n\n**Q: Where should O3 avatars be placed?**  \nA: O3 avatars should be placed in the `/agents/your-agent-name/config.yaml` directory structure.\n\n**Q: Should I keep working with V1 or switch to V2?**  \nA: V2 is worth learning despite being a bigger shift in agent development thinking. It offers more flexibility and control once you understand it.\n\n## Community Help & Collaboration\n\n- **Shaw helped amlord** with hosting UIs in plugins, sharing a GitHub link to the degen-intel example\n- **Shaw and jasyn_bjorn assisted Wolfy** with transferring social media handles for auto.fun\n- **inthiseconomy provided Ruby** with detailed explanations of Storacha's storage architecture and performance metrics\n- **Ruby guided mindxploit** on implementing agent structures in CLI projects and setting up O3 avatars\n- **Ruby helped rchak007** understand the benefits of V2 despite its learning curve, offering troubleshooting assistance\n\n## Action Items\n\n### Technical\n- Ensure plugin actions have distinct names to avoid conflicts (mentioned by shaw)\n- Abstract knowledge/memory system to an MCP server for better modularity (mentioned by DeFine)\n- Support forking plugin-bootstrap to modify messageReceivedHandler for multiple smaller texts (mentioned by standard)\n- Configure Twitter agent to reply to replies of target accounts (mentioned by Coinshome)\n- Implement encryption using LIT Protocol for Storacha storage (mentioned by fforbeck)\n- Develop warm storage with distributed node network for Storacha (mentioned by inthiseconomy)\n- Stress test replication under failure scenarios for Storacha (mentioned by Ruby)\n- Implement consensus mechanism between storage nodes (mentioned by Ruby)\n- Implement proper directory structure for O3 avatars (mentioned by Ruby)\n\n### Documentation\n- Document how to run multiple character configurations on the same machine (mentioned by artzy)\n- Create sample directory layout for O3 avatars (mentioned by Ruby)\n\n### Feature Requests\n- Add option to pay to increase compute speed for finding vanity CAs on auto.fun (mentioned by DorianD)\n- Develop ElizaOS Plugin for Storacha integration (mentioned by fforbeck)"
        },
        {
          "filename": "2025-04-21.md",
          "content": "# elizaOS Development Discord - 2025-04-21\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **Plugin Architecture**: Discussions about naming conflicts in plugin actions, with confirmation that action names need to be distinct across plugins\n- **UI Capabilities**: Information shared about hosting UIs in plugins, with reference to the investment manager example in the GitHub repository\n- **Docker Improvements**: A PR (#4330) was submitted with Docker improvements, though concerns were raised about TypeScript validation scripts potentially becoming too strict\n\n### Auto.fun Platform\n- **Platform Clarification**: Auto.fun functions more as a token launchpad rather than an agent creator\n- **Feature Suggestions**: Proposal for a paid feature to increase compute speed when finding vanity Contract Addresses\n\n### Agent Development\n- **V2 Transition**: Users are experiencing a learning curve with V2, but it was emphasized that V2 offers more flexibility and control than V1 once mastered\n- **Agent Dev School**: Confirmation of an Agent Dev School event running from 8am-10pm UTC\n- **Configuration Parameters**: Discussion about research-style response configurations, including increasing max_tokens and temperature\n\n## Key Questions & Answers\n\n**Q: Does auto.fun create agents?**  \nA: It's more of a token launchpad than an agent creator (answered by Odilitime)\n\n**Q: What if there are several actions from plugins with the same action name?**  \nA: Actions need to have distinct names to avoid conflicts (answered by shaw and Odilitime)\n\n**Q: Is there a way to render OAuth authentication links better in ElizaOS plugins?**  \nA: ElizaOS has the ability to host UIs in plugins; the investmentManager example in the GitHub repository demonstrates this (answered by shaw)\n\n**Q: Is the Agent Dev School happening today and will it be recorded?**  \nA: Yes, it's running from 8am-10pm UTC in the elizaOS discord server. No confirmation on recording (answered by Ruby)\n\n**Q: Should I keep working with V1 instead of struggling with V2?**  \nA: No, V2 is worth learning despite being a bigger shift in thinking. It offers more flexibility and control once you understand it (answered by Ruby)\n\n## Community Help & Collaboration\n\n- **Plugin Action Naming**: Shaw helped guigs understand that plugin actions need unique names and shared a GitHub repository example of UI hosting in plugins\n- **Auto.fun Team Contacts**: Shaw and jasyn_bjorn assisted Wolfy with contacting the auto.fun team regarding social media handles\n- **V2 Transition Support**: Ruby encouraged rchak007 to persist with learning V2 despite difficulties, offering to help troubleshoot specific issues\n\n## Action Items\n\n### Technical\n- Ensure plugin actions have distinct names to avoid conflicts (mentioned by shaw and Odilitime)\n- Implement support for running multiple character configurations on the same machine (mentioned by artzy)\n- Review strictness of TypeScript validation scripts in PR #4330 to ensure they don't reject valid code (mentioned by Ruby)\n- Learn and adapt to V2 despite its steeper learning curve (mentioned by Ruby)\n\n### Documentation\n- Need clarification on V2 launch status (mentioned by Nisita)\n\n### Feature\n- Implement paid option in auto.fun to increase compute speed for finding vanity Contract Addresses (mentioned by DorianD)\n- Improve rendering of OAuth authentication links in ElizaOS plugins (mentioned by amlord)"
        },
        {
          "filename": "2025-04-20.md",
          "content": "# elizaOS Development Discord - 2025-04-20\n\n**Date: April 20, 2025**\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform & Token Launchpad\n- Auto.fun is functioning primarily as a token launchpad rather than an agent platform\n- Users reported issues with token indexing for tokens with SOL in bonding curve\n- Token import from Meteora liquidity pool was identified as unsupported, with developers acknowledging the need for a fix\n- The auto.fun support channel was reported as blank/inaccessible by some users\n\n### Twitter Integration & Bot Safety\n- Discussions around Twitter client configuration settings and safety concerns\n- Odilitime shared GitHub links with configurable settings including ENABLE_ACTION_PROCESSING and TWITTER_TARGET_USERS\n- Users expressed concerns about Twitter bot suspensions, with advice to be careful with tweet frequency\n- Paying for Twitter subscriptions was suggested to reduce the risk of bot accounts being suspended\n\n### Agent Development Challenges\n- Johannes Weniger is developing an AI agent impersonating Aubrey de Grey (longevity researcher) on ElizaOS v2/Phala\n- Two main challenges identified: making the agent respond like a researcher with scientific references, and enabling file/image processing\n- Current limitations in ElizaOS v2's shouldRespondHandler are preventing assistant-like responses, with fixes planned\n- Detailed guidance provided on parameter tuning for academic-style responses and implementing custom data sources\n\n### GitHub/Wallet Mapping System\n- R0am discussed developing a system (tipdotmd) to map GitHub accounts to crypto wallets\n- The system aims to support Retroactive Public Goods Funding (RPGF) distribution\n- Debate around the balance between security (wallet verification) and usability (reducing friction)\n- R0am argued that payment incentives naturally ensure users provide wallets they control\n\n### Technical Pull Requests\n- PR #4325 addressing GPU detection in Docker containers\n- PR #4330 implementing Docker improvements and TypeScript validation scripts\n- Humorous banter about interdimensional GPU usage rather than substantive technical discussion\n\n## Key Questions & Answers\n\n**Q: How can I make an agent answer like a researcher and reference studies?**  \nA: Increase max_tokens and temperature, add academic writing examples to knowledge base, tune personality traits for detail over brevity, and consider overriding shouldRespondHandler restrictions. (Ruby, Shaw)\n\n**Q: What are the steps to enable an agent to process files and images?**  \nA: File/image processing should work natively in Discord, and UI uploads go into retrieval. For custom data sources, add a service, provider, and action. For S3 plugin, ensure proper AWS credentials and IAM permissions. (Ruby, Shaw)\n\n**Q: Is it safer now to use Twitter bots? Do I need a subscription to prevent suspension?**  \nA: Giving Twitter money helps. It's not necessarily safer, just be careful and don't tweet too much. (Odilitime)\n\n**Q: Should I use another version for Twitter integration?**  \nA: No, 0.x is the best for Twitter right now. (Odilitime)\n\n**Q: Does auto.fun create agents?**  \nA: It's more of a token launchpad than an agent platform. (Odilitime)\n\n**Q: How would wallet ownership be verified in the GitHub/wallet mapping system?**  \nA: Users are responsible for the wallet they input; the system only needs to verify GitHub ownership. Payment incentives ensure users provide wallets they control. (R0am)\n\n## Community Help & Collaboration\n\n### Twitter Integration Support\n- **Helper:** Odilitime | **Helpee:** Coinshome  \n  Provided guidance on Twitter client configuration with GitHub links to adjustable settings\n\n### Agent Development Guidance\n- **Helper:** Ruby | **Helpee:** Johannes Weniger  \n  Offered detailed suggestions for making an agent respond like a researcher, including parameter adjustments and knowledge base enhancements\n\n- **Helper:** Shaw | **Helpee:** Johannes Weniger  \n  Explained architectural approaches for implementing custom data sources and clarified current limitations in the platform\n\n### Token Platform Issues\n- **Helper:** shaw | **Helpee:** funboy  \n  Acknowledged the issue with unsupported token import from Meteora liquidity pool and indicated they would look into fixing it\n\n### GitHub/Wallet System Design\n- **Helper:** R0am | **Helpee:** Ruby  \n  Explained the design philosophy behind a GitHub/wallet mapping system, focusing on reducing friction while maintaining security through incentive alignment\n\n## Action Items\n\n### Technical\n- Fix indexing for tokens with SOL in bonding curve created after platform launch (Yemmii)\n- Fix permissions in public channels for new Discord server (Yemmii)\n- Investigate and address root access vulnerability to VM running operator (standard)\n- Fix token import support from Meteora liquidity pool (funboy)\n- Fix blank/inaccessible autofun support channel (CheddarQueso 🧀)\n- Fix shouldRespondHandler to allow more assistant-like responses (Shaw)\n- Debug S3 plugin configuration for file handling (Johannes Weniger)\n- Fix GPU detection in Docker containers (PR #4325) (DeFine)\n- Implement Docker improvements and TypeScript validation scripts (PR #4330) (DeFine)\n- Create a repository for GitHub/wallet pairs with API access for RPGF distribution (R0am)\n\n### Feature\n- Consider launching ai16play at auto.fun (ElizaBAO🌟)\n- Implement GitHub account verification for wallet mapping system (R0am)\n- Consider adding wallet verification through signed messages (Ruby)\n- Implement custom data source architecture for research agents (Shaw)\n- Improve academic response capabilities for research-oriented agents (Johannes Weniger)\n\n### Documentation\n- Document parameter tuning for academic agents (Ruby)"
        }
      ]
    }
  },
  "github": {
    "summaries": {
      "week": [
        {
          "filename": "2025-04-27.md",
          "content": "# ElizaOS Weekly Update (Week of Apr 27, 2025)\n\n## OVERVIEW\nThis week saw significant improvements to the ElizaOS framework with a focus on enhancing developer experience, fixing critical bugs, and improving plugin functionality. Key achievements include scopable knowledge implementation, Discord plugin enhancements, and comprehensive CLI command updates.\n\n## PROJECT METRICS\n- PRs: 29 merged PR's, 31 new PRs\n- Issues: 0 new issues, 0 closed issues\n- Unique Contributors: 23\n- Code Changes: +6059/-21763 lines across 140 files\n- Total Commits: 92\n- Most Active Contributors: wtfsayo, lalalune, 0xbbjoker, tcm390, samarth30\n\n## TOP ISSUES\n\n### Plugin Integration Challenges\n- Several issues related to plugin functionality were addressed, particularly with Discord, Anthropic, and Twitter integrations\n- Error handling improvements were needed for various edge cases, including disk space limitations\n\n### Developer Experience Friction\n- CLI command instructions required updates to improve clarity and usability\n- Documentation links and image paths needed fixing to ensure proper resource accessibility\n- Environment setup and configuration issues in Docker containers needed resolution\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced Plugin Functionality\n- Added typing indicator support in Discord plugin [#4364](https://github.com/elizaos/eliza/pull/4364)\n- Implemented API key validation for Anthropic plugin model calls [#4383](https://github.com/elizaos/eliza/pull/4383)\n- Fixed Discord plugin error handling when services are missing [#4375](https://github.com/elizaos/eliza/pull/4375)\n- Added model/plugin name logging when models are used [#4394](https://github.com/elizaos/eliza/pull/4394)\n\n### Improved Developer Experience\n- Implemented scopable knowledge functionality [#4390](https://github.com/elizaos/eliza/pull/4390)\n- Updated ElizaOS create command instructions [#4381](https://github.com/elizaos/eliza/pull/4381)\n- Added automatic rebuild of core and plugin-bootstrap in monorepo context [#4388](https://github.com/elizaos/eliza/pull/4388)\n- Added .env.example in project-starter for easier configuration [#4387](https://github.com/elizaos/eliza/pull/4387)\n- Fixed ESM type declarations in Core [#4341](https://github.com/elizaos/eliza/pull/4341)\n- Updated documentation with improved quick start and CLI commands [#4379](https://github.com/elizaos/eliza/pull/4379)\n\n### Infrastructure and Maintenance\n- Fixed Postgres database issues in Docker containers [#4363](https://github.com/elizaos/eliza/pull/4363)\n- Improved error handling for disk space limitations [#4389](https://github.com/elizaos/eliza/pull/4389)\n- Fixed agent deletion functionality [#4395](https://github.com/elizaos/eliza/pull/4395)\n- Removed plugin-evm from monorepo [#4386](https://github.com/elizaos/eliza/pull/4386), [#4399](https://github.com/elizaos/eliza/pull/4399)\n- Enhanced UI with cleaner design and minor improvements [#4393](https://github.com/elizaos/eliza/pull/4393)"
        }
      ],
      "month": [
        {
          "filename": "2025-04-01.md",
          "content": "# ElizaOS Monthly Update (April 2025)\n\n## OVERVIEW\nApril saw significant enhancements to ElizaOS with major improvements to the CLI, GUI, and plugin ecosystem. Key achievements include expanded AI model provider integrations, enhanced messaging capabilities, improved TTS functionality, and substantial fixes to core components and plugins.\n\n## PROJECT METRICS\n- PRs: 195 merged PR's, 232 new PRs\n- Issues: 43 new issues, 35 closed issues\n- Unique Contributors: 88\n- Code Changes: +55467/-37251 lines across 489 files\n- Total Commits: 828\n- Most Active Contributors: wtfsayo, tcm390, 0xbbjoker, Samarthsinghal28, HarshModi2005\n\n## TOP ISSUES\n\n### CLI Usability and Consistency\n- Command inconsistencies between v1 and v2\n- Installation and update workflow issues\n- Project creation and agent management challenges\n\n### Plugin Management\n- Plugin installation priority ordering issues\n- Dynamic loading and versioning problems\n- Plugin dependency conflicts\n\n### AI Model Integration\n- JSON parsing errors with Anthropic and OpenAI responses\n- Model validation and authentication issues\n- Embedding model selection and configuration\n\n### Database and Transaction Handling\n- Transaction deadlocks in database operations\n- Migration issues with PgLite\n- Entity relationship inconsistencies\n\n### Messaging and Communication\n- Duplicate message creation\n- Twitter interaction failures\n- Telegram data synchronization problems\n\n### User Interface\n- Knowledge manager scroll issues\n- Missing UI components after merge conflicts\n- Inconsistent character creation workflow\n\n### Performance and Resource Management\n- Disk space management and error handling\n- Memory leaks and caching issues\n- Runtime initialization sequence problems\n\n### Documentation and Onboarding\n- Inconsistent or outdated CLI documentation\n- Missing environment configuration examples\n- Broken documentation links\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced AI Model Provider Ecosystem\n- Added Kluster AI as a model provider [#3938](https://github.com/elizaos/eliza/pull/3938)\n- Added Mem0 as AI SDK Provider [#3927](https://github.com/elizaos/eliza/pull/3927)\n- Improved OpenAI plugin with ability to choose embedding models [#4140](https://github.com/elizaos/eliza/pull/4140)\n- Added model/plugin name logging when model is used [#4394](https://github.com/elizaos/eliza/pull/4394)\n\n### Voice and Speech Capabilities\n- Implemented OpenAI TTS functionality [#4255](https://github.com/elizaos/eliza/pull/4255)\n- Added testing for OpenAI TTS [#4259](https://github.com/elizaos/eliza/pull/4259)\n- Fixed speech-to-text transcription issues [#4236](https://github.com/elizaos/eliza/pull/4236)\n- Fixed OpenAI STT functionality [#4329](https://github.com/elizaos/eliza/pull/4329)\n\n### CLI Improvements\n- Added update-cli command for easier updates [#4170](https://github.com/elizaos/eliza/pull/4170)\n- Enhanced CLI update and plugin installation with package manager [#4176](https://github.com/elizaos/eliza/pull/4176)\n- Implemented CLI test suite [#4301](https://github.com/elizaos/eliza/pull/4301)\n- Updated ElizaOS create command instructions [#4381](https://github.com/elizaos/eliza/pull/4381)\n\n### Messaging and Interaction Enhancements\n- Added message API for improved communication [#4247](https://github.com/elizaos/eliza/pull/4247)\n- Added message buttons for interactive responses [#4187](https://github.com/elizaos/eliza/pull/4187)\n- Improved Reply Action to use pre-generated responses [#4213](https://github.com/elizaos/eliza/pull/4213)\n- Added typing indicators to Telegram [#4280](https://github.com/elizaos/eliza/pull/4280) and Discord [#4364](https://github.com/elizaos/eliza/pull/4364)\n\n### Plugin System Improvements\n- Better plugin installation management [#4177](https://github.com/elizaos/eliza/pull/4177)\n- Added test coverage for plugin-bootstrap [#4173](https://github.com/elizaos/eliza/pull/4173)\n- Enabled path params routes for plugins [#4335](https://github.com/elizaos/eliza/pull/4335)\n- Fixed plugin install priority order [#4256](https://github.com/elizaos/eliza/pull/4256)\n\n### GUI Enhancements\n- Added support for importing JSON to create or update agents [#4270](https://github.com/elizaos/eliza/pull/4270)\n- Enhanced GUI with various improvements [#4300](https://github.com/elizaos/eliza/pull/4300)\n- Added confirmation dialog for delete group [#4310](https://github.com/elizaos/eliza/pull/4310)\n- Implemented onboarding tour [#4293](https://github.com/elizaos/eliza/pull/4293)\n\n### Social Media Integration\n- Enhanced Telegram logic with middlewares [#4125](https://github.com/elizaos/eliza/pull/4125)\n- Added Telegram community manager [#4134](https://github.com/elizaos/eliza/pull/4134)\n- Improved Twitter plugin with support for long tweets [#4291](https://github.com/elizaos/eliza/pull/4291)\n- Added deleteTweet() functionality [#4320](https://github.com/elizaos/eliza/pull/4320)\n\n### Knowledge and Memory Management\n- Implemented scopable knowledge [#4390](https://github.com/elizaos/eliza/pull/4390)\n- Fixed knowledge types [#4243](https://github.com/elizaos/eliza/pull/4243)\n- Replaced fastembed with local embedding model [#4205](https://github.com/elizaos/eliza/pull/4205)\n- Fixed cache interaction cursor and duplicate memory creation [#4155](https://github.com/elizaos/eliza/pull/4155)\n\n### Logging and Monitoring\n- Added OpenAI model usage events [#4230](https://github.com/elizaos/eliza/pull/4230)\n- Restored support for Cloudflare LLM logging/tracking [#4354](https://github.com/elizaos/eliza/pull/4354)\n- Added docstrings to cloudflare-logging [#4355](https://github.com/elizaos/eliza/pull/4355)\n- Improved logging for transcription models [#4283](https://github.com/elizaos/eliza/pull/4283)\n\n## SUMMARY\nApril 2025 was a productive month for ElizaOS with significant improvements across the platform. The team expanded AI model provider integrations, enhanced messaging capabilities, improved voice and speech features, and fixed numerous issues in the core system and plugins. The CLI and GUI received substantial upgrades, making the platform more user-friendly and robust. These developments have strengthened ElizaOS's position as a versatile, modular AI agent framework capable of operating across diverse ecosystems."
        }
      ]
    }
  }
}