{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-05-08",
  "date": 1746662400,
  "stats": {
    "totalMessages": 569,
    "totalUsers": 66
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around Shaw (a key team member) temporarily suspending his Twitter account, causing community concern and FUD (Fear, Uncertainty, Doubt). Jin and other team members attempt to reassure the community that Shaw is taking a break and still working on development. The conversation touches on contributor recognition for the ElizaOS project, particularly regarding eligibility for a potential DOOD airdrop. There's discussion about how GitHub contributors were identified for rewards, with Jin mentioning challenges in collecting Solana wallet addresses from contributors. The chat reveals that the ElizaOS team provided contributor data to the Doodles team for their airdrop, but submission deadlines may have passed for some. Community members express interest in ElizaOS v2 development and discuss token distribution statistics, noting that AI16Z has more decentralized token distribution (69% held by top 100) compared to another token called VIRTUAL (93% held by top 100).\n\n## 2. FAQ\nQ: Why did Shaw's account get suspended? (asked by mars) A: He's taking a Twitter detox break (answered by jin)\nQ: Why doesn't he just let people know he's going on a break? (asked by waterisgood123) A: Unanswered\nQ: Is elizaOS v2 coming soon? (asked by xell0x) A: Unanswered\nQ: How's degenai going? Updates were supposed to come since February (asked by Dive or Die) A: Unanswered\nQ: Is this the discord of ai16z? (asked by Blow) A: Unanswered\nQ: Is there any airdrop for those who hold 10k eliza or more? (asked by gaona6828) A: Sorry, no (answered by Osint)\nQ: I read that ElizaOS contributors could be eligible for DOOD airdrop? (asked by gaona6828) A: Contributors to codebase (answered by Osint)\nQ: I had a PR merged into Eliza GH, how does that link to my wallet for dood? (asked by Cubs | WILL NOT DM) A: Send your SOL address to kenk (answered by jin)\nQ: Where can you view the AUM for ai16z? (asked by rap7ure) A: I think it's on DAOs.fun (answered by Kenk)\nQ: Is the hoplite role for holding 100k degenai gone? (asked by Adii) A: Yes, I believe so (answered by Osint)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Contributors | Context: Collecting Solana wallet addresses for contributor rewards | Resolution: Jin instructed contributors to send their addresses to kenk\nHelper: eskender.eth | Helpee: Deniz | Context: Confirming eligibility for DOOD airdrop | Resolution: Offered to check wallet addresses with the team\nHelper: Osint | Helpee: jin | Context: Offered to help collect Solana addresses | Resolution: Offered to process a list to get addresses for jin\nHelper: Osint | Helpee: Community | Context: Explaining Shaw's Twitter absence | Resolution: Clarified that Shaw is taking a break and still coding\nHelper: Kenk | Helpee: rap7ure | Context: Finding AI16Z AUM information | Resolution: Directed user to DAOs.fun\n\n## 4. Action Items\nTechnical: ElizaOS v2 development | Description: Continue development of the next version | Mentioned By: xell0x\nTechnical: Discord contributor analysis | Description: Complete analysis of Discord contributors for rewards | Mentioned By: jin\nTechnical: Collect Solana wallet addresses | Description: Gather addresses from contributors for rewards | Mentioned By: jin\nDocumentation: Create Pope AI X agent | Description: Develop an AI agent for the new Pope announcement | Mentioned By: groggs\nFeature: Feature Eli5 more prominently | Description: Use Eli5 as mascot on auto.fun, Shaw's and elizaOS' Twitter | Mentioned By: xell0x\nFeature: Create crypto dev GitHub graph | Description: Tool to plot relationships and influence among crypto developers | Mentioned By: Osint",
      "messageCount": 206,
      "userCount": 34
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around ElizaOS development and troubleshooting. Users discussed Twitter agent integration, Docker image building issues, and configuration problems with local AI models. A key technical issue involved ElizaOS defaulting to local AI models despite configuration settings specifying external providers like Groq. The solution involved properly setting environment variables in the .env file at the root folder and configuring characters for specific plugins. There was also discussion about a database error (\"duplicate key value violates unique constraint\") occurring specifically with the Discord plugin. Other topics included Vercel's MCP server support for Next.js, Twitter plugin integration, and model selection for agents.\n\n## 2. FAQ:\nQ: Does anyone know which version of Eliza is currently working best? (asked by keygray_mm) A: Unanswered\nQ: How do I add plugin twitter to character? (asked by keygray_mm) A: Documentation is available at https://docs.eliza.how/blog/twitter-agent-guide (answered by odilitime)\nQ: Why am I getting \"duplicate key value violates unique constraint 'memories_pkey'\" error while interacting in Discord? (asked by odilitime) A: It appears to be a Discord plugin-specific issue that resolves temporarily after using the Eliza web interface (answered by odilitime)\nQ: How do I fix ElizaOS falling back to local AI despite configuration? (asked by odilitime) A: Configure the .env file at the root with your API keys and configure characters for plugin-groq (answered by odilitime)\n\n## 3. Help Interactions:\nHelper: odilitime | Helpee: odilitime | Context: ElizaOS Docker image falling back to local AI despite configuration | Resolution: Suggested configuring characters for plugin-groq and setting up .env file with API keys at the root folder\nHelper: odilitime | Helpee: mahee | Context: Twitter AI agent API quota issues | Resolution: Suggested using Heurist as a free alternative\nHelper: keygray_mm | Helpee: mahee | Context: Twitter API quota exceeded error | Resolution: Suggested using Heurist as it's free\n\n## 4. Action Items:\nType: Technical | Description: Fix Discord plugin issue causing \"duplicate key value violates unique constraint 'memories_pkey'\" error | Mentioned By: odilitime\nType: Technical | Description: Test interactive 24/7 unreal engine elizaOS metahuman | Mentioned By: odilitime\nType: Technical | Description: Update/push multistream-client and air3market-plugin for V2 | Mentioned By: odilitime\nType: Documentation | Description: Create clearer instructions for configuring external AI providers like Groq | Mentioned By: odilitime",
      "messageCount": 34,
      "userCount": 7
    },
    {
      "channelId": "1361442528813121556",
      "channelName": "fun",
      "summary": "# Analysis of Discord Chat in \"fun\" Channel\n\n## 1. Summary\nThe chat primarily revolves around a problematic token launch called \"PrinceSCRT\" by Secret Network on the auto.fun platform. Users reported that shortly after launch, the developer wallet sold a significant portion of tokens, causing the price to crash from a peak of approximately $800k to around $60-80k market cap. This triggered accusations of a \"rug pull\" and demands for refunds. The auto.fun team, represented by jasyn_bjorn, stated they wouldn't issue refunds as they have \"no control over what the team does post launch.\" This incident follows other problematic launches mentioned by users, including issues with \"doglifeai\" and a mistaken token verification the previous day (which did result in refunds). Throughout the controversy, some users continued to promote ELI5 token as a safer alternative. The chat also briefly touched on potential improvements to the platform, including a subscription model for early access to partner projects.\n\n## 2. FAQ\nQ: So will the refund be automatic? We just have to wait? (asked by Kudo Ω) A: ya. will be sorted in < 24hrs (answered by jasyn_bjorn)\nQ: Do I just need to wait after submitting information to the bot (asked by Kudo Ω) A: ya. will be sorted in < 24hrs (answered by jasyn_bjorn)\nQ: can you tell me why i should invest into eli5? (asked by shad) A: Unanswered\nQ: when will it migrate (asked by vas) A: its migrated (answered by eskender.eth)\nQ: will there be a refund? (asked by mhd) A: we unfortunately have no control over what the team does post launch even after we vet them thoroughly beforehand. sorry, but we wont be issuing refunds for this launch. (answered by jasyn_bjorn)\n\n## 3. Help Interactions\nHelper: jasyn_bjorn | Helpee: Kudo Ω | Context: User asking about refund process | Resolution: Confirmed refund would be processed within 24 hours\nHelper: eskender.eth | Helpee: vas | Context: Explaining why partners don't always share contract addresses before launch | Resolution: Clarified it's about control and limiting people at point of launch\nHelper: ryanthelad | Helpee: Multiple users | Context: Providing information about Secret Network still holding supply | Resolution: Attempted to reassure users during price crash\n\n## 4. Action Items\nType: Technical | Description: Partners should be required to share contract address before launching to prevent wrong addresses | Mentioned By: vas\nType: Technical | Description: Implement a subscription model allowing OG members early investment in partner projects with allocation limits and locks | Mentioned By: MDMnvest\nType: Technical | Description: Fix bugs in the platform as it \"needs bug fixes and to mature\" | Mentioned By: nasdaq.ai\nType: Technical | Description: Establish stricter criteria for partner verification to prevent problematic launches | Mentioned By: vas\nType: Feature | Description: Lock up ELI5 tokens to get early allocation to partner projects, similar to Virtual | Mentioned By: ryanthelad\nType: Documentation | Description: Clearer communication about risks involved with new token launches | Mentioned By: jasyn_bjorn",
      "messageCount": 315,
      "userCount": 28
    },
    {
      "channelId": "1362864274862768450",
      "channelName": "fun-support",
      "summary": "# Analysis of \"fun-support\" Discord Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily revolves around an upcoming token generation event (TGE) for a project called \"Doodles\" (DOOD), with users seeking information about token distribution amounts. A user named Kenk shared a link to an article about the Doodles new Blood Fund TGE. Additionally, there was a concern raised about fake coins existing on a platform before the official token launch, with a suggestion to remove them to prevent confusion. Finally, a user complained about losing money in a project called \"pscrt\" that was allegedly promoted by \"auto fun\" and then abandoned by the developer.\n\n## 2. FAQ\nQ: Any news about tomorrow's event? (asked by sukrucildirr) A: Kenk shared an article link about Doodles DOOD new Blood Fund TGE (answered by Kenk)\nQ: Will we get 200k per contribution? (asked by sukrucildirr) A: I have no insight into how they're distributing (answered by Kenk)\nQ: Can you give me a hint about the distribution? (asked by sukrucildirr) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: sukrucildirr | Context: User seeking information about upcoming token event | Resolution: Shared an article link about the Doodles DOOD new Blood Fund TGE\nHelper: velja | Helpee: Community | Context: Fake coins existing on site before real token launch | Resolution: Suggested removing fake coins to prevent confusion when the real one launches\n\n## 4. Action Items\nTechnical: Remove fake coins from the platform before the real token launches | Description: Prevent confusion and mistakes by ensuring only the legitimate token is listed | Mentioned By: velja\nTechnical: Investigate the pscrt token situation | Description: Look into claims that a developer abandoned the pscrt project after promotion by \"auto fun\" | Mentioned By: hxf",
      "messageCount": 14,
      "userCount": 4
    }
  ]
}