{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-05-09",
  "date": 1746748800,
  "stats": {
    "totalMessages": 455,
    "totalUsers": 61
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, an AI agent framework. Key technical points include:\n- Mentions of an upcoming V2 release with a teaser shared\n- GitHub contribution tracking system and leaderboard functionality\n- A PR (#92) to fix pagination issues on the leaderboard website\n- Discussion about extending autodotfun functionality to Twitter for token launching\n- Conversation about connecting GitHub accounts to SOL wallets for contribution tracking\n- Reference to an AI news aggregator being improved by 2-3x\n- Discussion about the elizaOS.github.io repository which tracks contributions\n- Mention of a Doodles NFT drop for ElizaOS contributors\n\nThe community appears engaged with both the technical aspects of the project and token-related discussions, with several members inquiring about upcoming features and contribution recognition.\n\n## 2. FAQ\nQ: How did you determine % for decentralized 60-70? (asked by abhi_ironman) A: That's standard, 60-70 percent for top 100 token holders (answered by Osint (aka not_a_dev_ai))\nQ: Are we looking for binance spot listing through any way? (asked by abhi_ironman) A: That is something that we have no control of. When they decide it is in their best interest to list ai16z spot, then they'll do it (answered by Osint (aka not_a_dev_ai))\nQ: How can I connect my GH and sol wallet for future airdrops? (asked by Deniz) A: We don't have a fully deployed solution for doing that yet (answered by jin)\nQ: What's the link to the leaderboard? (asked by MonteCrypto) A: https://elizaos.github.io/ (answered by jin)\nQ: Why am I not on the leaderboard? (asked by MonteCrypto) A: Search should be top 1000 / no limit, considering that a bug (answered by jin)\nQ: Why am I not in leaderboard? (asked by sukrucildirr) A: The data are stored correctly it's just not visible on the website yet (answered by MonteCrypto)\nQ: When is v2 coming? (asked by xell0x) A: Unanswered\nQ: Is there any advantage for us that hold 10k or more ai16z? (asked by gaona6828) A: No info about that yet (answered by !Addison Casey!)\n\n## 3. Help Interactions\nHelper: jin | Helpee: MonteCrypto | Context: User couldn't find themselves on the leaderboard | Resolution: Jin provided a direct profile link and acknowledged search limitation as a bug\nHelper: MonteCrypto | Helpee: sukrucildirr | Context: User concerned about not being on leaderboard and impact on Doodle drop | Resolution: Explained data is stored correctly but not visible on website yet\nHelper: MonteCrypto | Helpee: Community | Context: Pagination issues on the leaderboard website | Resolution: Created PR #92 to fix pagination and make all contributors visible\n\n## 4. Action Items\nTechnical: Fix leaderboard search to include all contributors beyond top 100 | Description: Current search only allows searching within top 100 contributors | Mentioned By: jin\nTechnical: Add pagination to show all profiles on leaderboard | Description: Currently only shows top 100 contributors | Mentioned By: MonteCrypto\nTechnical: Develop solution for connecting GitHub and SOL wallet | Description: For tracking contributions and future airdrops | Mentioned By: jin\nTechnical: Extend autodotfun functionality to Twitter | Description: Enable launching tokens from Twitter with commands | Mentioned By: Osint (aka not_a_dev_ai)\nDocumentation: Add leaderboard link to contributing docs | Description: Link needs to be added to https://eliza.how/docs/contributing | Mentioned By: MonteCrypto\nDocumentation: Update frontpage of eliza.how with better quick actions | Description: Add partners, videos, leaderboard, plugins links | Mentioned By: jin\nFeature: Improve AI-news aggregator | Description: Jin discovered ways to make it 2-3x better | Mentioned By: jin\nFeature: ElizaOS V2 | Description: Upcoming major update teased in chat | Mentioned By: Multiple users",
      "messageCount": 168,
      "userCount": 30
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Analysis of 💻-coders Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS plugin development and configuration issues. BowTiedBlueFin encountered problems importing plugins from external GitHub repositories into ElizaOS, as the system appears to have hardcoded assumptions about repository locations. The issue stems from ElizaOS not correctly parsing GitHub URL formats in package.json files, particularly for plugins outside the official elizaos-plugins organization. Odilitime acknowledged this issue with 1.x plugins from the registry.\n\nSeveral users reported technical problems with ElizaOS, including LMStudio integration errors, Solana plugin import failures due to missing dependencies (@elizaos/plugin-tee and @elizaos/plugin-trustdb), database migration issues, and memory-related crashes with the Twitter plugin. Users also discussed configuration challenges with PostgreSQL databases, particularly when using Neon as a database provider.\n\n## 2. FAQ\nQ: Has anyone had success importing a plugin into eliza and seeing it in the UI on a local build? (asked by BowTiedBlueFin) A: Odilitime indicated they would publish instructions the following week.\nQ: How do I fix the error \"Failed to run database migrations (pglite)\" when running ElizaOS? (asked by scooter8992) A: Unanswered\nQ: How do I fix the Twitter plugin causing \"Maximum call stack size exceeded\" errors? (asked by scooter8992) A: Unanswered\nQ: How to get eliza agent to respond to messages on Discord with their @? (asked by scooter8992) A: Unanswered\nQ: Is eliza.gg down? (asked by scooter8992) A: Kenk suggested using Eliza.how instead.\nQ: How long are facts/provider knowledge cached in state? (asked by scooter8992) A: winded4752 mentioned persistence is in the databases.\nQ: When eliza agent is monitoring/responding in multiple servers do we want each server to be its own world? (asked by scooter8992) A: Kenk noted that in v2 it will be able to use the same memory across multiple client interfaces.\nQ: How to force migrate or scrap old PostgreSQL configuration for the new one with the added WorldID field? (asked by scooter8992) A: Unanswered\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: BowTiedBlueFin | Context: Issues with importing plugins from external GitHub repositories | Resolution: Acknowledged the issue with 1.x plugins and mentioned instructions would be published the following week.\nHelper: scooter8992 | Helpee: scooter8992 | Context: Database migration errors with Neon PostgreSQL | Resolution: Created a new project in Neon to get a fresh database, which resolved the issue.\nHelper: Kenk | Helpee: scooter8992 | Context: User asked if eliza.gg was down | Resolution: Suggested using Eliza.how as an alternative.\n\n## 4. Action Items\nType: Technical | Description: Fix plugin resolution logic in ElizaOS to properly handle GitHub URLs from package.json for plugins outside the elizaos-plugins organization | Mentioned By: BowTiedBlueFin\nType: Technical | Description: Address the fs4.exists error in ElizaOS configuration saving | Mentioned By: scooter8992\nType: Technical | Description: Fix memory leak in Twitter plugin causing \"Maximum call stack size exceeded\" errors | Mentioned By: scooter8992\nType: Technical | Description: Resolve missing dependencies (@elizaos/plugin-tee and @elizaos/plugin-trustdb) for the Solana plugin | Mentioned By: scooter8992\nType: Documentation | Description: Publish instructions for plugin development and integration with ElizaOS | Mentioned By: Odilitime\nType: Feature | Description: Implement time-based caching for facts/provider knowledge in state | Mentioned By: scooter8992\nType: Feature | Description: Support for agents to use the same memory across multiple client interfaces in v2 | Mentioned By: Kenk",
      "messageCount": 76,
      "userCount": 6
    },
    {
      "channelId": "1361442528813121556",
      "channelName": "fun",
      "summary": "# Analysis of \"fun\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around concerns about token launches on the auto.fun platform. Multiple users express frustration about recent token launches they perceive as \"rugs\" (projects that quickly lose value or where developers sell holdings). Specific focus is on ELI5 and CZAI tokens, with mixed sentiment about ELI5's potential as it's mentioned to be an official character in elizaOS v2 and \"AI16z's brother.\" Users complain about the verification process for tokens and transparency issues, particularly with the CZAI launch where users claim the team purchased most of the supply despite claiming 85% was for the community. Team member \"ben\" acknowledges feedback and mentions improvements are underway for the platform. The chat reveals tension between users who lost money and those who remain optimistic about certain tokens, particularly ELI5, which some users believe has strong potential due to its connection with Shaw and elizaOS v2.\n\n## 2. FAQ\nQ: What is the role of EDDY and what is the role of ELI5? (asked by Wagecuck) A: Unanswered\nQ: What changed? You were so bullish a few hours ago. (asked by MDMnvest) A: Dude, this isn't even a platform as popular as a pump lol. People are leaving on a platform where there is not a single success. (answered by Yuyi)\nQ: Will this be autofun launches this week END? (asked by noj) A: Unanswered\nQ: What do you mean by \"based off the Reddit Eli5 community with 15M members\"? (asked by Zolo) A: Look up r/explainlikeimfive on Reddit, 23.2 Million Followers. All of them will be onboarded to Eli5. (answered by ryanthelad)\nQ: Is CZAI launching today? (asked by W0100) A: We don't know. (answered by Xyness)\nQ: Does this still apply to the remaining projects? (asked by noj) A: It does - no launches on weekends. (answered by ben)\nQ: When v2? (asked by velja) A: Unanswered\n\n## 3. Help Interactions\nHelper: ryanthelad | Helpee: Channel members | Context: Declining sentiment about ELI5 token | Resolution: Shared positive information about ELI5 being AI16z's little brother and based on Reddit community with 15M members\nHelper: xell0x | Helpee: Channel members | Context: Confusion about ELI5's role and value | Resolution: Shared information about Shaw making ELI5 an official character in elizaOS v2 as Eliza's community manager\nHelper: ben | Helpee: frank_grimes_sr | Context: Questions about verification process for tokens | Resolution: Explained that verified means they know the team is building and have had previous interactions with them\n\n## 4. Action Items\nType: Technical | Description: Improve token verification process to prevent misleading information about token distribution | Mentioned By: frank_grimes_sr\nType: Technical | Description: Make migration speed consistent for all coins or wait for green checkmark before migration | Mentioned By: frank_grimes_sr\nType: Technical | Description: Analyze verified launches to improve the launch process | Mentioned By: ben\nType: Feature | Description: Allow more launches to apply for verified status after first round of launch partners | Mentioned By: ryanthelad\nType: Documentation | Description: Provide clearer information about token distribution before launches | Mentioned By: vas\nType: Documentation | Description: Create more transparency around the verification process | Mentioned By: frank_grimes_sr",
      "messageCount": 201,
      "userCount": 30
    },
    {
      "channelId": "1362864274862768450",
      "channelName": "fun-support",
      "summary": "# Analysis of \"fun-support\" Discord Channel\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. It includes a notice about channel deprecation, with support for auto.fun moving to Telegram via @AutoDotFunBot within 48 hours. There's a brief mention about the separation between the platform and teams launching on it. A representative from P2B exchange offered their services. One user expressed frustration about experiencing multiple unsuccessful launches (\"rugs\"). No significant technical discussions, problem-solving, or implementations were present in this limited chat segment.\n\n## 2. FAQ\nQ: When new launch (asked by Veki) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in the chat segment.\n\n## 4. Action Items\nType: Documentation | Description: Users need to migrate to Telegram (@AutoDotFunBot) for support as Discord channel will be deprecated within 48 hours | Mentioned By: Kenk",
      "messageCount": 10,
      "userCount": 4
    }
  ]
}