{
  "ai-news": {
    "elizaos": {
      "discord_md_last_3_days": [
        {
          "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)"
        },
        {
          "filename": "2025-04-19.md",
          "content": "# elizaOS Discord - 2025-04-19\n\n## Overall Discussion Highlights\n\n### Auto.fun Launch and Technical Issues\n- **Auto.fun Platform Launch**: Shaw and the ElizaOS team launched auto.fun, a token launchpad platform with AI integration features.\n- **Technical Difficulties**: The launch experienced significant issues due to overwhelming traffic, with multiple server overloads forcing temporary redirects to Twitter.\n- **Ongoing Fixes**: The team took the platform down several times for server upgrades and backend fixes, actively collecting affected token addresses for remediation.\n- **Platform Mechanics**: Auto.fun uses Raydium AMM with a new mechanism developed with the Raydium team that enables liquidity NFTs, allowing token deployers to claim fees from burned/graduated LP positions.\n- **Tokenomics**: The platform collects 10% of bonded LP fees, which are used to buy back $ai16z tokens from the open market and reinvest in ai16z LP to create deeper ecosystem liquidity.\n\n### Platform Features\n- **Custom Vanity Addresses**: Users can specify the last 3-4 characters of token contract addresses.\n- **Token-Gated Chat**: Chat rooms where only users with a specific amount of tokens can access.\n- **AI Integration**: Content creation tools and AI-enhanced features for token communities.\n- **Bonding Curve**: Uses a bonding curve with 28 SOL initial virtual reserves, with tokens automatically graduating to Raydium when they reach 113 SOL in reserves (85 SOL actual + 28 SOL virtual).\n- **Token Migration**: Tokens migrate to decentralized exchanges like Raydium or Meteora when they reach 100% bonding.\n- **Anti-Snipe/Bundle Features**: Protections against common token launch exploitation tactics.\n\n### ElizaOS Development\n- **Spartan Updates**: SpartanVersus (Twitter account) is back online with a blue checkmark and affiliate badge. The team is working on upgrading it to v2, fixing autonomous trading bugs, and preparing for Discord and Telegram integration.\n- **Plugin Architecture Issues**: Several users encountered problems with Telegram and Discord plugins, particularly regarding event handling and message processing.\n- **Event Handling**: Technical discussion about how events are emitted and subscribed to in the ElizaOS plugin architecture, with callbacks being triggered twice during message processing.\n\n## Key Questions & Answers\n\n### Auto.fun Platform\n- **Q**: What is auto.fun?  \n  **A**: A creator-friendly launchpad and no-code platform integrating multi-agent functionality, collaborative tokenomics, and AI-enhanced features.\n\n- **Q**: Will auto.fun have its own token?  \n  **A**: No new token, only $ai16z and $degenai are official tokens.\n\n- **Q**: How does auto.fun differ from pump.fun?  \n  **A**: More fair launch features, creator support, anti-snipe/bundle, different bonding curve, importable tokens.\n\n- **Q**: How does the bonding curve work?  \n  **A**: Auto.fun uses a bonding curve with 28 SOL initial virtual reserves.\n\n- **Q**: What happens when a coin reaches the bonding curve limit?  \n  **A**: It automatically graduates to Raydium with a 6 SOL flat fee.\n\n- **Q**: How much SOL is required for migration in Auto.fun?  \n  **A**: 85 SOL + 28 SOL virtual reserve = 113 SOL.\n\n- **Q**: Why doesn't auto.fun buyback DegenAI tokens?  \n  **A**: Multiple reasons: Spartan already gets exposure from buybacks, technical complexity of splitting fees, and potential confusion in ecosystem vs agent narrative.\n\n### ElizaOS Development\n- **Q**: When can automated trading be used with Spartan?  \n  **A**: No estimate available yet.\n\n- **Q**: Is Spartan now v2 or not yet?  \n  **A**: Not yet, having problems getting v2 to sound like Spartan without losing what works well.\n\n- **Q**: Are Discord plugin events being subscribed to at all?  \n  **A**: Yes, plugin-bootstrap has the event receiver.\n\n- **Q**: Why are callbacks in the Discord service getting hit twice?  \n  **A**: The first callback assumes text isn't in the response, but debugging shows it is present.\n\n## Community Help & Collaboration\n\n### Token Creation & Migration Issues\n- **Helper**: yikesawjeez | **Helpee**: noj  \n  **Context**: User had 6 SOL locked in a token they couldn't access, with token showing as \"locked\"  \n  **Resolution**: Suggested importing the token and posting details in the bug report channel for team assistance.\n\n- **Helper**: eskender.eth | **Helpee**: Redvoid  \n  **Context**: User wanted to connect their Eliza bot to a token on auto.fun  \n  **Resolution**: Explained that after creating a token, they can update metadata including social accounts if connected with the same wallet.\n\n- **Helper**: beeboop | **Helpee**: accelxr  \n  **Context**: User was getting \"Failed to create token on-chain\" error when trying to create a manual token  \n  **Resolution**: Identified the error in console as \"Symbol too long\" and suggested reducing ticker length from 12 characters.\n\n### ElizaOS Plugin Issues\n- **Helper**: k_carv | **Helpee**: k_carv  \n  **Context**: Understanding how events are emitted and subscribed to in ElizaOS plugins  \n  **Resolution**: Self-resolved by examining code and discovering plugin-bootstrap handles the event receiver.\n\n- **Helper**: martincontact101 | **Helpee**: k_carv  \n  **Context**: Error starting agents with \"Agent not found\" JSON error  \n  **Resolution**: Suggested the character JSON file was wrong and offered DM support.\n\n### Networking & Community\n- **Helper**: Zolo | **Helpee**: HoneyBadger  \n  **Context**: Looking for Eliza partners in Hong Kong  \n  **Resolution**: Zolo shared a Twitter contact (AIFlow_ML) who will host an event in Hong Kong.\n\n- **Helper**: Curtisdonthurtus | **Helpee**: Odilitime  \n  **Context**: Spartan giving poor responses when unable to provide requested content  \n  **Resolution**: Suggested making Spartan not answer when asked for content it can't make instead of giving a lame response.\n\n## Action Items\n\n### Technical\n- Fix server capacity issues to handle high traffic load on auto.fun (Redvoid)\n- Complete token migrations from testing phase (Multiple users)\n- Fix wallet connection issues (smithiio)\n- Resolve token creation failures (uloze)\n- Fix token price display issues (abhi_ironman)\n- Ensure created tokens appear in the interface (casper)\n- Fix double callback issue in message processing flow (k_carv)\n- Resolve embedding API 404 error when using Gemini with client-telegram (Abbas)\n- Fix installation issues with Telegram plugin (k_carv)\n- Fix autonomous trading bugs in Spartan (Odilitime)\n- Fix tokens stuck in \"migrating\" state (joeyseoul, FatalPie, will_11six)\n- Fix indexing issues causing \"Error Loading Token\" (zero, phetrusrodrigues, noj)\n- Fix liquidity pool creation for early tokens (João Pedro, YourDadsFriendSteve)\n- Implement batch update for affected tokens (eskender.eth)\n- Fix manual token creation errors (Quiche Lorraine, beeboop)\n- Fix token visibility in \"coins created\" section (phetrusrodrigues, noj)\n- Fix swap button functionality (thatjpeg, Curtisdonthurtus)\n- Fix transaction timeouts during token creation (yikesawjeez, CtrlAltElite)\n- Fix wallet connection issues after X login (yikesawjeez)\n- Fix token selling functionality (yikesawjeez)\n- Fix search filters and indexing (jin, Noname)\n- Add disconnect wallet button (yikesawjeez)\n- Fix holders display (yikesawjeez)\n- Update AutoFun's status on social media platforms (HoneyBadger)\n- Establish customer support via AutoFun's X account (HoneyBadger)\n\n### Documentation\n- Provide clear explanation of token migration process (Multiple users)\n- Create documentation for auto.fun features and differences from pump.fun (Multiple users)\n- Document proper event handling between plugins in ElizaOS architecture (k_carv)\n- Update dexscreener and public Telegram room information (Odilitime)\n- Create clear documentation about token migration process (Tocheee)\n- Improve error messaging for token creation failures (beeboop)\n- Release detailed tokenomics article (eskender.eth, Borko)\n\n### Features\n- Implement AI16z bridge to Solana (yikesawjeez)\n- Add agent functionality to compete with virtuals on Solana (beeboop)\n- Implement functionality for AI agents to attach random images from a folder when creating posts (TruffleSoul)\n- Create liquidity pool with $ai16z on Meteora (Avanc)\n- Prepare for post-launch promotion phase (Avanc)\n- Add ability to chat with bots directly on the auto.fun platform (Redvoid)\n- Turn token chat into an Eliza world with token creation capabilities (yikesawjeez)\n- Add community notes feature to identify unofficial tokens (jin)\n- Allow attaching newly generated images/videos to token gated chat (yardy)\n- Add more interactive filters (Lucid)\n- Improve navigation between pages (Curtisdonthurtus)\n- Add homepage navigation when clicking top-left icon (HoneyBadger)\n- Implement partnership with auto.fun for cross-promotion (Odilitime)\n- Add degenai and ai16z to pinned featured (Void)"
        }
      ],
      "dev_md_last_3_days": [
        {
          "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)"
        },
        {
          "filename": "2025-04-19.md",
          "content": "# elizaOS Development Discord - 2025-04-19\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform Issues\n- A significant Auto.fun launch occurred with multiple reported problems\n- Users experienced issues with token creation, indexing, and accessing tokens with SOL in bonding curves\n- Several users reported losing SOL and being unable to use the platform properly\n- Odilitime announced that the issue should be fixed\n- Support is being handled in a separate AI16z Discord, though some users reported permission issues when joining\n\n### Twitter Agent Development\n- Detailed discussion about configuring agents to reply to target account replies\n- Ruby provided comprehensive instructions for modifying Twitter listeners to track replies to specific accounts\n- Implementation involves adding 'in_reply_to_user_id' parameters and updating filter rules\n- Webhook event handling was explained for parsing 'referenced_tweets' field to track full reply threads\n\n### Project Announcements\n- R0am launched tip.md, a tool enabling developers to receive crypto tips through GitHub READMEs\n- The system works across Ethereum, Solana, and Bitcoin Lightning networks with no platform custody\n- Potential integration with retroactive public goods funding (RPGF) mechanisms was discussed\n- A PR (#4325) addressing GPU detection in Docker containers was shared\n\n### Security Concerns\n- One user reported gaining unexpected root access to a VM running an operator, representing a potential security vulnerability\n\n### Project Management\n- Jin mentioned merging a large documentation PR\n- Discussion about requirements for obtaining contributor roles in the project\n\n## Key Questions & Answers\n\n**Q: How would I make my Twitter agent always reply to the replies of a target account?**  \nA: You need to modify the agent's Twitter listener to include reply_to queries in the search criteria by adding 'in_reply_to_user_id' to your target filter and updating filter rules to include replies. Check GitHub repository settings like ENABLE_ACTION_PROCESSING or TWITTER_TARGET_USERS.\n\n**Q: Is there any support channel for auto fun?**  \nA: Yes, but we're monitoring this channel too.\n\n**Q: Is it safer now? Do I have to pay a subscription so she doesn't get booted?**  \nA: Giving them money helps. I'm not sure it's any safer just be careful and don't tweet too much.\n\n**Q: Have you considered alternative funding approaches like quadratic funding or retroactive public goods?**  \nA: I think of this as a tool to enable RPGF, as it's a GitHub/wallet record that can be leveraged via the incoming API.\n\n**Q: Are you planning to add any additional identity verification layers?**  \nA: Users are responsible for the wallet they input, we just need to verify GH ownership. Getting paid is the incentive to ensure they put a wallet they verify and own.\n\n**Q: Is it possible to get contributor role? Is there a minimum requirement or is 1 merged PR enough?**  \nA: Contributor roles are typically granted after showing consistent quality contributions over time - one merged PR is a great start but keep up the momentum!\n\n## Community Help & Collaboration\n\n1. **Twitter Agent Reply Functionality**\n   - Ruby provided detailed step-by-step instructions to Coinshome for implementing Twitter reply tracking\n   - Explained how to modify twitter_listener.py and handle webhook events to track reply threads\n   - Odilitime shared GitHub repository link with environment settings to check\n\n2. **Auto.fun Platform Issues**\n   - Jin acknowledged issues with Auto.fun platform taking SOL but not working\n   - Shaw recognized token import problems from meteora liquidity pool and indicated they would investigate\n   - Odilitime kept users updated on fix progress\n\n3. **tip.md Integration Discussion**\n   - R0am explained to Ruby how tip.md creates GitHub/wallet mappings that can be accessed via API for RPGF distribution\n   - Addressed concerns about Sybil resistance and verification mechanisms\n\n## Action Items\n\n### Technical\n- Fix Auto.fun platform issues with tokens that have SOL in bonding curve but are not indexed (Mentioned by Yemmii)\n- Investigate root access vulnerability to VM running operator (Mentioned by standard)\n- Fix token import from meteora liquidity pool (Mentioned by funboy)\n- Fix permissions in AI16z Discord for new joiners (Mentioned by Yemmii)\n- Modify twitter_listener.py to add 'in_reply_to_user_id' to search parameters (Mentioned by Ruby)\n- Implement webhook event handler to parse 'referenced_tweets' field (Mentioned by Ruby)\n- Fix GPU detection in Docker containers via PR #4325 (Mentioned by DeFine)\n- Consider implementing wallet ownership verification for tip.md (Mentioned by Ruby)\n- Develop anti-Sybil measures for tip.md (Mentioned by Ruby)\n\n### Documentation\n- Create or improve documentation about Twitter agent configuration options (Mentioned by Coinshome)\n- Create documentation about the organization structure (Mentioned by jin)\n\n### Feature\n- Implement functionality for Twitter agents to reply to target account replies (Mentioned by Coinshome)\n- Integrate tip.md with leaderboard projects to quantify contribution value (Mentioned by R0am)"
        }
      ]
    }
  },
  "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."
        }
      ]
    }
  }
}