{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-05-14",
  "date": 1747180800,
  "stats": {
    "totalMessages": 372,
    "totalUsers": 42
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, auto.fun, and AI16z development. Key technical points include discussions about creating mobile applications for ElizaOS, with participants noting that mobile presence is crucial for user adoption. There were specific mentions of API limitations in the auto.fun repository, with users examining the code and identifying that while some API endpoints exist (for swaps, token retrieval, search, and charts), they lack functionality for creating new coins or executing swaps. Users shared GitHub links to the API code and brand kit. \n\nThe community also discussed market making for the project tokens, with team members clarifying they have reputable market makers for both CEX and DEX. There were questions about the progress of \"v2\" development, with team members indicating it's in beta testing. A team member shared a glimpse of the v2 development, describing it as \"looking at a pizza before it goes into the oven\" with GPT-4o image generation being the final step.\n\nSeveral participants compared ElizaOS to competitors like Virtuals, expressing concerns about development pace. The discussion also touched on token permissions, specifically the \"mint\" permission on the AI16z token, with a team member explaining this is standard for daos.fun coins and will be addressed at the appropriate time.\n\n## 2. FAQ\nQ: Can ElizaOS run on iPhone? (asked by DorianD) A: It's dependent on NodeJS and only some very old versions run on iOS; Android might be possible (answered by DorianD)\nQ: Where is the auto.fun API? (asked by DorianD) A: https://github.com/elizaOS/auto.fun/blob/6877fd1955a2d73577399eabb2b722d4b2806257/packages/client/src/utils/api.ts (answered by Osint (aka not_a_dev_ai))\nQ: Can you replace Wintermute as a market maker? Do you have an agreement with Wintermute? (asked by abchaker) A: We don't have an agreement with WM, we can't restrict them from trading either. We have very reputable MM's for both CEX & DEX (answered by jasyn_bjorn)\nQ: What is the direction and target of ElizaOS and AI16Z? (asked by Johny) A: Unanswered\nQ: What is the roadmap to disable the \"mint\" permission on ai16z token? (asked by Kenshiro) A: All daos.fun coins have this by default; when we get the right opportunity to change, the team will take a hard look at it (answered by Osint (aka not_a_dev_ai))\nQ: What's the difference between Eliza and Elizav2? (asked by CULTVESTING) A: Yes like day and night (answered by xell0x)\nQ: Who did the epic agent Bazar vid? (asked by Spyros) A: My team did it (answered by jin)\n\n## 3. Help Interactions\nHelper: Osint (aka not_a_dev_ai) | Helpee: DorianD | Context: Looking for auto.fun API | Resolution: Provided GitHub link to the API code\nHelper: Osint (aka not_a_dev_ai) | Helpee: DorianD | Context: Looking for ElizaOS logo files | Resolution: Provided link to the brand kit repository\nHelper: xell0x | Helpee: Dive or Die | Context: Question about v2 progress | Resolution: Explained that v2 is being beta tested\nHelper: jasyn_bjorn | Helpee: abchaker | Context: Questions about market makers | Resolution: Clarified the project's relationship with market makers\nHelper: jin | Helpee: xell0x | Context: Sharing v2 development progress | Resolution: Provided a visual and explanation of the current state of development\n\n## 4. Action Items\nTechnical: Develop mobile apps (iOS/Android) for ElizaOS/auto.fun | Description: Mobile presence is crucial for user adoption | Mentioned By: DorianD, Osint (aka not_a_dev_ai)\nTechnical: Expand auto.fun API to support coin creation and swapping | Description: Current API only supports getting swaps, tokens, search, and charts | Mentioned By: DorianD\nTechnical: Fix getToken API endpoint | Description: Function is broken with a TODO comment | Mentioned By: DorianD\nTechnical: Complete v2 development | Description: Currently in beta testing phase | Mentioned By: jin, xell0x\nTechnical: Address the \"mint\" permission on AI16z token | Description: Consider removing or upgrading token to v2 | Mentioned By: Kenshiro\nFeature: Create an AI agent to answer project-related questions | Description: Agent would store and retrieve project knowledge | Mentioned By: DorianD\nFeature: Consider including ICM meta bumper functionality in auto.fun | Description: Similar to what Virtuals is doing to drive token demand | Mentioned By: abhi_ironman",
      "messageCount": 208,
      "userCount": 27
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around users setting up and troubleshooting ElizaOS v2 (beta) and v1 (0.x) implementations. Key technical discussions include:\n\n- Setting up Supabase databases for agents, with users sharing SQL commands for creating tables\n- Custom plugin development and integration challenges, particularly importing local plugins versus using NPM packages\n- Configuration issues with character settings not updating properly in the UI\n- Twitter/X integration problems, including configuring environment variables for replying to specific users\n- Differences between ElizaOS v1 (main branch, 0.x) and v2 (v2-develop branch, 1.x)\n- Plugin installation failures and import errors\n- Static page routing in v2\n- Model loading and initialization issues\n\nUsers shared code snippets for SQL table creation, character configuration, and plugin imports. Several users encountered similar issues with plugins not loading properly or character configurations not being recognized. The discussions highlight the transition challenges between v1 and v2 of ElizaOS.\n\n## 2. FAQ\nQ: How to set up Supabase tables for ElizaOS? (asked by cjft) A: Use SQL commands to create tables with proper references and constraints (answered by cjft)\nQ: Is the OpenRouter plugin working? (asked by cjft) A: Unanswered\nQ: How can you import a custom plugin from a project directory instead of a core plugin? (asked by cjft) A: Use the --plugin flag at start (answered by cjft)\nQ: Is Google Generative AI usable with the beta ElizaOS? (asked by cjft) A: Works in 0.25 but not in beta, and there's no available plugin (answered by cjft)\nQ: Does routing to a static page work in v2? (asked by cjft) A: Unanswered\nQ: Is it better to install all of Eliza instead of using CLI when extending plugins? (asked by cjft) A: Unanswered\nQ: Is the ElizaOS/eliza repo on GitHub V2 or is only the CLI using V2? (asked by cjft) A: Main branch is 0.x (v1) and v2-develop is 1.x (v2) (answered by cjft)\nQ: Do you need to create a Twitter room for the agent? (asked by cjft) A: You don't need to create any Twitter room (answered by cjft)\n\n## 3. Help Interactions\nHelper: cjft | Helpee: cjft | Context: Setting up Supabase database tables | Resolution: Shared SQL commands for creating agent and room tables with proper references\nHelper: cjft | Helpee: starlord | Context: Understanding model loading output | Resolution: Confirmed that no more output after model loading is correct behavior\nHelper: cjft | Helpee: cjft | Context: Twitter integration not registering activity | Resolution: Suggested checking ENABLE_ACTION_PROCESSING setting and TWITTER_TARGET_USERS configuration\nHelper: cjft | Helpee: cjft | Context: Character configuration not updating in UI | Resolution: Suggested pulling latest beta.51 version\n\n## 4. Action Items\nType: Technical | Description: Fix plugin import errors for custom plugins | Mentioned By: cjft\nType: Technical | Description: Resolve character configuration not updating in UI | Mentioned By: cjft\nType: Technical | Description: Fix Twitter/X integration to properly respond to targeted users | Mentioned By: cjft\nType: Technical | Description: Resolve client build errors in Windows environment | Mentioned By: Bills_43\nType: Documentation | Description: Create guide for extending core plugins in v2 | Mentioned By: cjft\nType: Documentation | Description: Document differences between v1 and v2 plugin systems | Mentioned By: cjft\nType: Feature | Description: Improve plugin-bootstrap customization options | Mentioned By: cjft\nType: Feature | Description: Add Google Generative AI support to ElizaOS beta | Mentioned By: cjft",
      "messageCount": 74,
      "userCount": 7
    },
    {
      "channelId": "1361442528813121556",
      "channelName": "fun",
      "summary": "# Discord Chat Analysis - Channel \"fun\"\n\n## 1. Summary\nThe chat primarily revolves around discussions about auto.fun, a platform for launching tokens on Solana, and the ELI5 token associated with ElizaOS. DorianD inquires about auto.fun's API and how it tracks tokens on-chain, with vas explaining that auto.fun tracks tokens that interact with its specific program address (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5). DorianD eventually understands that tokens are tracked through their interaction with this program address, as seen in the getalltokens.ts file. \n\nThere's also significant discussion about ELI5, which xell0x claims will be the community manager AI agent for ElizaOS v2, referencing an interview with Shaw confirming this. This leads to debate about the token's legitimacy and potential value, with xell0x arguing that ELI5's official status in the upcoming v2 launch should justify a higher market cap than its current 500k valuation.\n\n## 2. FAQ\nQ: Does auto.fun have an API so that an ElizaOS agent can interface with it to create a coin? (asked by DorianD) A: You need to build the transaction to launch through their program; they track their program, not every coin on-chain (answered by vas)\nQ: How does autofun track tokens? (asked by DorianD) A: It processes tokens that interact with the program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5 (answered by DorianD after investigation)\nQ: What are the features of Eli5? (asked by Sio) A: Unanswered\nQ: Is there a plan for Eli5? (asked by Sio) A: Shaw confirmed eli5 to be the community manager ai agent of elizaOS v2 (answered by xell0x)\nQ: How many launches upcoming this week? (asked by Void) A: Unanswered\nQ: No launches for next 2 weeks then launches resume, right team? (asked by frank_grimes_sr) A: Unanswered\n\n## 3. Help Interactions\nHelper: vas | Helpee: DorianD | Context: Understanding how auto.fun tracks tokens on Solana | Resolution: Explained that tokens are tracked through interaction with auto.fun's program, not all on-chain tokens\nHelper: xell0x | Helpee: Sio | Context: Looking for information about ELI5's role | Resolution: Shared an interview clip in another channel where Shaw confirmed ELI5 as community manager for ElizaOS v2\nHelper: DorianD | Helpee: Self | Context: Understanding auto.fun's token tracking mechanism | Resolution: Found in getalltokens.ts that it processes tokens interacting with program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5\n\n## 4. Action Items\nTechnical: Recreate launch or launchandswap instruction to interact with auto.fun program | Description: Required for ElizaOS agent to create coins on auto.fun | Mentioned By: vas\nFeature: Develop a phone app for auto.fun | Description: Current platform lacks mobile accessibility | Mentioned By: DorianD\nDocumentation: Document steps for creating tokens through auto.fun | Description: Needed to explain the process to others | Mentioned By: DorianD",
      "messageCount": 88,
      "userCount": 12
    },
    {
      "channelId": "1362864274862768450",
      "channelName": "fun-support",
      "summary": "The chat segment is extremely brief, containing only a single user's request. Nyotengu6900 asked if their project could be verified and displayed on the main page, sharing a link to what appears to be a token on auto.fun with the identifier \"69veVD4oo3QbJzXrAH7Rans8sue68AsgYyirWUrxSQUy\". No technical discussions, problem-solving, or implementations were present in this limited exchange.",
      "messageCount": 2,
      "userCount": 1
    }
  ]
}