{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-05-06",
  "date": 1746489600,
  "stats": {
    "totalMessages": 652,
    "totalUsers": 59
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around issues with the Eliza platform, token roles, and upcoming developments. A significant issue emerged when verification thresholds for token holders were changed without notice, causing frustration among community members who lost their roles. Kenk acknowledged this communication failure, explaining it was done by an individual without proper notification. The chat also touched on ElizaOS V2 development, with community members expressing interest in its features and potential. There were discussions about auto.fun integration, with one user offering payment for setup assistance. Several users expressed concerns about the project's direction, token value, and lack of communication from the team. The conversation also included comparisons between Eliza and Virtuals platforms, with debates about their different approaches (Eliza focusing on framework development versus Virtuals' token-centric approach). Technical discussions included deployment options for Eliza and the need for successful AI agents on the platform.\n\n## 2. FAQ\nQ: Are there any trading terminals that support auto.fun? (asked by dway) A: Solsniper (answered by Osint (aka not_a_dev_ai))\nQ: Is eli5 dead? What's wrong with the auto fun only producing garbage? (asked by cloudAI) A: Unanswered\nQ: Is degenAI dead too? (asked by cloudAI) A: Unanswered\nQ: Did anyone create a middle ground solution for deploying Eliza? (asked by Ouranos) A: Unanswered\nQ: Is there a beta for the new Eliza OS? (asked by Interval) A: Yeah www.eliza.how (answered by Kenk)\nQ: How much of a gamechanger will be elizaOS v2? (asked by xell0x) A: ElizaOS V2 is gonna be 💯 (answered by Osint (aka not_a_dev_ai))\nQ: Do the agents' token have a specific usecase in v2? (asked by xell0x) A: That I do not know (answered by Osint (aka not_a_dev_ai))\nQ: Are you still hiring only in upwork? (asked by 0xCryptoCooker) A: Unanswered\n\n## 3. Help Interactions\nHelper: Osint (aka not_a_dev_ai) | Helpee: hachem | Context: User asking for the support channel | Resolution: Directed to the appropriate channel (#1300025221834739744)\nHelper: Kenk | Helpee: Nicasso | Context: User needed help setting up auto.fun and was willing to pay | Resolution: Kenk offered to match the payment for devs who could help\nHelper: Osint (aka not_a_dev_ai) | Helpee: xell0x | Context: Discussion about ElizaOS V2 features and capabilities | Resolution: Provided information about the focus on building vertical AI agents with actual use cases\nHelper: Kenk | Helpee: Multiple users | Context: Issues with verification thresholds being changed without notice | Resolution: Explained the situation and apologized for the communication failure\n\n## 4. Action Items\nType: Technical | Description: Set up auto.fun for user willing to pay 500 for assistance | Mentioned By: Nicasso\nType: Technical | Description: Containerize Eliza and deploy on remote server | Mentioned By: yikesawjeez\nType: Feature | Description: Give Eliza a voice on X (Twitter) to help price stabilize | Mentioned By: nasdaq.ai\nType: Feature | Description: Create community-only AI agents rather than generic AI agents | Mentioned By: xell0x\nType: Feature | Description: Develop an AI agent for auto.fun that can achieve viral growth like aixbt did for Virtuals | Mentioned By: xell0x\nType: Documentation | Description: Provide clear communication about token verification thresholds | Mentioned By: Kenk\nType: Technical | Description: Create a middle-ground solution for deploying Eliza (between simple but limited options and complex ones) | Mentioned By: Ouranos\nType: Feature | Description: Integrate auto.fun AI agents with ElizaOS v2 | Mentioned By: xell0x",
      "messageCount": 216,
      "userCount": 25
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS agent development issues, focusing on installation problems, plugin configuration, and deployment challenges. Users encountered various technical difficulties including plugin loading failures, database constraints, and environment configuration issues. Key discussions included:\n\n- Installation problems with ElizaOS CLI on Ubuntu (permission errors) and MacOS (plugin loading failures)\n- Database configuration issues, particularly with SQL plugins and PostgreSQL constraints\n- Character configuration syntax for plugins in both v1 and v2 formats\n- Twitter agent setup and configuration challenges\n- Environment variable handling and configuration file management\n- Plugin loading and verification errors across different installation methods\n- Workarounds for CLI installation using npx instead of global installation\n\nSeveral users shared error logs and received troubleshooting advice from community members, with solutions ranging from using alternative installation methods to modifying database workflows.\n\n## 2. FAQ\nQ: Is there a proxy plugin that would allow each Twitter client to use a different IP address locally? (asked by some) A: Unanswered\nQ: Is it possible to build a custom, lightweight set of plugins instead of installing the full Eliza client? (asked by some) A: Unanswered\nQ: Is this correct if using the defaultCharacter.ts? (asked by boyaloxer) A: Unanswered\nQ: Why do I call these API that don't get response? (asked by kandizzy) A: Unanswered\nQ: How can I make sure that nothing gets added to the memory by default when an action is triggered? (asked by kandizzy) A: Unanswered\nQ: How do I make a character use the packages/core/... config files that I have set? (asked by kandizzy) A: Unanswered\nQ: Is Eliza V2 working with Twitter and custom plugins? (asked by nasdaq.ai) A: Unanswered\nQ: Is there an official guide on best practice to add custom plugin retrieved data to memory? (asked by nasdaq.ai) A: Unanswered\nQ: If we want all messages stored to PostgreSQL how to get around duplicate key constraint? (asked by kandizzy) A: Unanswered\nQ: Is there any way to bypass the first db prompt (pglite or db) when you initially run bun run dev? (asked by kandizzy) A: Self-answered using echo -e '\\n' to simulate pressing enter\nQ: Has someone been able to run Eliza with lmstudio or ollama? (asked by kandizzy) A: Yes, with 1.x version by setting the right .env and telling the character which model to use (answered by mtbc)\n\n## 3. Help Interactions\nHelper: kandizzy | Helpee: Kgood | Context: Installation errors with plugin-sql and plugin-openai | Resolution: Suggested installing bun with npm install -g bun and letting it automatically install the plugins\nHelper: kandizzy | Helpee: kandizzy | Context: Bypassing initial DB prompt when running bun run dev | Resolution: Self-solved using echo -e '\\n' to simulate pressing enter, noting it's useful for docker compose initialization\nHelper: kandizzy | Helpee: kandizzy | Context: Plugins not accessible after installation on Ubuntu | Resolution: Suggested using npx elizaos start instead of elizaos start after CLI installation\nHelper: kandizzy | Helpee: kandizzy | Context: Finding ElizaOS database location | Resolution: Provided path \"/home/alerios/.eliza/db\"\nHelper: mtbc | Helpee: kandizzy | Context: Running Eliza with ollama | Resolution: Confirmed it works with 1.x by setting correct .env and model configuration\n\n## 4. Action Items\nTechnical: Fix plugin loading issues when installing via npm global installation | Description: Plugins fail to load with elizaos start but work with npx elizaos start | Mentioned By: kandizzy\nTechnical: Address PostgreSQL duplicate key constraint for message storage | Description: Current SQL plugin setup prevents storing duplicate messages which blocks full comment logs | Mentioned By: kandizzy\nTechnical: Resolve Twitter agent posting functionality | Description: Agent initializes and logs in but doesn't post despite correct configuration | Mentioned By: kandizzy\nTechnical: Fix plugin installation and verification process | Description: Plugins install but fail verification with \"Failed to load plugin module\" errors | Mentioned By: kandizzy\nDocumentation: Create guide for running Eliza with local LLM solutions | Description: Document setup process for lmstudio and ollama integration | Mentioned By: kandizzy\nDocumentation: Provide clear examples of character configuration in v2 format | Description: Current examples don't match defaultCharacter.ts structure | Mentioned By: kandizzy\nFeature: Implement proxy plugin for Twitter clients | Description: Allow each Twitter client to use different IP addresses locally | Mentioned By: some\nFeature: Support for lightweight custom plugin combinations | Description: Enable building minimal plugin sets instead of full client installation | Mentioned By: some",
      "messageCount": 55,
      "userCount": 9
    },
    {
      "channelId": "1361442528813121556",
      "channelName": "fun",
      "summary": "# Analysis of Discord Channel \"fun\"\n\n## 1. Summary\nThe chat primarily revolves around token launches on the Auto.fun platform, with particular focus on the Comput3 (COM) token launch. Users discussed issues with fake tokens, sniping bots, and verification processes. The community expressed frustration with the launch mechanics, particularly how some wallets were able to execute multiple transactions within seconds of launch, suggesting potential manipulation. The Auto.fun team representatives (ben, jasyn_bjorn) responded to concerns, explaining verification processes and defending against accusations of insider trading. They mentioned implementing improvements to the verification system to combat fake tokens. Other discussions included interest in ELI5 token and its upcoming v2 release, as well as concerns about previous launches like Doglifeai that lost community trust. The chat demonstrates tension between users wanting fair launches and the platform's current limitations in preventing sniping and fake tokens.\n\n## 2. FAQ\nQ: Is autofun integrated with any bot like Axiom, Photon etc? (asked by Rishu) A: Zapier (answered by !Addison Casey!)\nQ: How do we know which token is real vs fake during migrations? (asked by Rishu) A: Wait for the verified badge and check the spotlight thread posted after launch (answered by ben)\nQ: What bots work with Auto.fun? (asked by Rishu) A: Solsniper works pre-migration, Axiom post-migration (answered by hxf)\nQ: Will the fake tokens be deleted before the real one launches? (asked by velja) A: Working on a long-term solution for fakes to improve discoverability of verified tokens (answered by ben)\nQ: When is elizaOS v2 coming out? (asked by xell0x) A: Soon, Shaw teased it on Twitter (answered by xell0x)\nQ: How many ELI5 tokens are there? (asked by Marc30) A: 1 billion, 700k cap currently (answered by xell0x)\nQ: What will Eli5 be used for? (asked by Marc30) A: elizaOS v2 AI agent (answered by xell0x)\n\n## 3. Help Interactions\nHelper: hxf | Helpee: Rishu | Context: Needed to know which bots work with Auto.fun | Resolution: Recommended Solsniper for pre-migration and Axiom for post-migration\nHelper: ben | Helpee: Multiple users | Context: Concerns about fake tokens and verification process | Resolution: Explained they're working on solutions and improved the verification time to 1 minute\nHelper: Simon | Helpee: Multiple users | Context: Warning about fake tokens | Resolution: Advised users to be careful with fake tokens appearing frequently\nHelper: hxf | Helpee: Rishu | Context: Needed link to Solsniper | Resolution: Provided Twitter link to Solsniper\nHelper: Xyness | Helpee: Rishu | Context: Warning about a fake token that just rugged | Resolution: Alerted user before they could invest\n\n## 4. Action Items\nType: Technical | Description: Implement a system with partner codes for instant token verification | Mentioned By: Xyness\nType: Technical | Description: Ban all names of upcoming token launches unless from agreed wallet | Mentioned By: TMO\nType: Technical | Description: Whitelist developer wallets before launch to prevent fake tokens | Mentioned By: velja\nType: Technical | Description: Fix migration process that takes too long (over an hour in some cases) | Mentioned By: Rishu\nType: Technical | Description: Prevent bundled transactions that allow some users to buy multiple times in seconds | Mentioned By: Pyroman\nType: Technical | Description: Announce CA before partner to ensure fair launch | Mentioned By: MDMnvest\nType: Feature | Description: Improve discoverability of verified tokens | Mentioned By: ben\nType: Feature | Description: Add MEV protection for pre-migrate on Auto.fun | Mentioned By: noj\nType: Feature | Description: Boost ELI5 to revive trust in the platform | Mentioned By: Yuyi",
      "messageCount": 355,
      "userCount": 32
    },
    {
      "channelId": "1362864274862768450",
      "channelName": "fun-support",
      "summary": "# Analysis of \"fun-support\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around issues with the Auto.fun platform, focusing on token migration problems and concerns about fake/scam tokens. Users report having funds stuck during migration processes and being victims of scams from fake token contracts. There appears to be a system for migrating tokens that takes time to complete, as confirmed by moderator \"Kenk.\" Users are requesting the removal of fake tokens from the site to prevent further scams. The community also briefly discusses trading tools compatible with Auto.fun, with \"solsniperxyz\" mentioned as a supported platform. There's a suggestion to pin important information in the channel to help users avoid scams, with recommendations to follow official Auto.fun social media for legitimate contract addresses.\n\n## 2. FAQ\nQ: Can you remove the fake ones from the site? (asked by velja) A: Unanswered\nQ: Why does my slippage keep resetting to 50% even after I change it? (asked by who) A: Unanswered\nQ: What bot or trading platform supports buying and selling on auto.fun? (asked by lutter9) A: solsniperxyz as of now (answered by Rishu)\nQ: Is this going to take time? (asked by Rishu) A: it takes time to migrate yes (answered by Kenk)\nQ: Can you have MEV off for pre-migrate on Auto fun? (asked by noj) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: Rishu | Context: User had funds stuck in token migration (contract HhTQuq71vQTDKZJ44YwGVPSjRXQQPVUNs6zLoMDLMFUN) | Resolution: Kenk confirmed team is aware of the issue\nHelper: Rishu | Helpee: lutter9 | Context: User asked about trading platforms supporting Auto.fun | Resolution: Rishu identified solsniperxyz as a currently supported platform\nHelper: MDMnvest | Helpee: Veki | Context: User complained about being rugged by fake tokens | Resolution: MDMnvest advised following official Auto.fun socials for correct contract addresses\n\n## 4. Action Items\nTechnical Tasks: Remove fake/scam tokens from the platform | Description: Multiple users reported scam tokens causing financial losses | Mentioned By: velja, Veki\nDocumentation Needs: Create and pin an information post | Description: Pin essential information to help users avoid scams and understand platform features | Mentioned By: yikesawjeez\nTechnical Tasks: Fix slippage reset issue | Description: Slippage setting resets to 50% after user changes it | Mentioned By: who\nTechnical Tasks: Investigate stuck migration | Description: Token with contract HhTQuq71vQTDKZJ44YwGVPSjRXQQPVUNs6zLoMDLMFUN is stuck in migration | Mentioned By: Rishu\nTechnical Tasks: Investigate $DOOD airdrop claims | Description: Token claims to have given airdrops to ElizaOS contributors without GitHub connection | Mentioned By: sukrucildirr\nFeature Requests: MEV protection for pre-migration | Description: Option to disable MEV for pre-migration transactions | Mentioned By: noj",
      "messageCount": 26,
      "userCount": 12
    }
  ]
}