{ "server": "elizaOS", "title": "elizaOS Discord - 2025-04-21", "date": 1745193600, "stats": { "totalMessages": 917, "totalUsers": 116 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around auto.fun and ElizaOS developments. Auto.fun was recently released and is currently in maintenance mode for upgrades and bug fixes. There are discussions about the relationship between auto.fun and the AI16z token, with some users expressing concern that the auto.fun launch hasn't positively impacted the AI16z token price. Users are anticipating ElizaV2's release, hoping it will generate market optimism. Kenk, a team member, confirmed that auto.fun's initial release was successful by internal metrics and mentioned upcoming information about launch partners. The chat also references weekly builder demos for ElizaOS projects and mentions bounty rewards for a \"fun token.\" Some developers offered their services in the chat. Technical questions included running multiple AI characters on a single machine and concerns about bugs in the current version.\n\n## 2. FAQ\nQ: Is auto.fun website down? (asked by GIgor_021) A: The site is in maintenance mode for upgrades and UI bug fixes (answered by Kenk)\nQ: Will ElizaV2 be delayed due to bugs in autofun? (asked by abhi_ironman) A: Unanswered\nQ: Is AI16z the native token for auto.fun? (asked by abhi_ironman) A: Unanswered\nQ: When will the auto.fun site be back up? (asked by abhi_ironman) A: Unanswered\nQ: How can I view the weekly builder demos recording? (asked by CoinPapi) A: They'll be added to https://www.youtube.com/@ElizaOSDeveloper (answered by Kenk)\nQ: Is it possible to run 2 different characters in the same machine? (asked by artzy) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: GIgor_021 | Context: User noticed auto.fun website redirecting to X account | Resolution: Kenk confirmed site is in maintenance mode\nHelper: Kenk | Helpee: CoinPapi | Context: User wanted to know how to view builder demo recordings | Resolution: Kenk directed them to the YouTube channel and suggested subscribing\nHelper: Kenk | Helpee: D. Ratta | Context: User complained about v_025_09 not working properly | Resolution: Kenk mentioned hundreds of agents operating on v0.XX and directed to support channel\n\n## 4. Action Items\nTechnical: Fix UI bugs in auto.fun during maintenance mode | Description: Several UI bugs are being addressed during the current maintenance | Mentioned By: Kenk\nTechnical: Release ElizaV2 | Description: Users anticipating the release of ElizaV2, potentially this week | Mentioned By: abhi_ironman\nTechnical: Implement functionality to run multiple AI characters on same machine | Description: Running different character configurations for different platforms simultaneously | Mentioned By: artzy\nFeature: Implement bounty rewards for fun token | Description: Mentioned as upcoming feature for community engagement | Mentioned By: Rick\nDocumentation: Upload builder demos to YouTube | Description: Weekly builder demos to be added to ElizaOS Developer YouTube channel | Mentioned By: Kenk", "messageCount": 82, "userCount": 39 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS development issues, with a focus on v2 implementation challenges. Users discussed plugin development, database integration, and deployment problems. Several users encountered Content Security Policy (CSP) errors when running ElizaOS v2 on Windows machines. There were questions about configuring agents to interact with social media platforms like Twitter, particularly regarding image generation and reply behaviors. Database connection issues were common, with users seeking guidance on PostgreSQL integration. The community also discussed LLM model support, with specific questions about DeepSeek compatibility. Some developers shared their custom plugins, including a MIDI communication plugin. Kenk shared a list of projects using ElizaOS across various domains including gaming, DeFi, marketplaces, and social applications. The chat demonstrates an active community working through technical challenges in implementing and extending ElizaOS functionality.\n\n## 2. FAQ\nQ: How do I setup my plugin to communicate with my database? (asked by [elizaos] ) A: Unanswered\nQ: How do I retrieve data from the plugin specifically? Do I need to connect via PostgreSQL credentials? (asked by [elizaos] ) A: Unanswered\nQ: Is there a plugin to use a custom openAI API compatible base URL and API key? (asked by BowTiedBlueFin) A: You may need to create your own plugin by following the documentation (answered by Kenk)\nQ: Does eliza-v2 work with deepseek? (asked by [elizaos] ) A: Unanswered\nQ: Where is the SQL URL stored when a new project is created using CLI? (asked by [elizaos] ) A: Unanswered\nQ: How do I get my agent to not reply/retweet/like any posts? (asked by [elizaos] ) A: Unanswered\nQ: How could I configure the agent to reply to the REPLIES of a target account? (asked by [elizaos] ) A: Unanswered\nQ: How do I prevent agent to select \"None\" action if question repeats? (asked by happylol123) A: Unanswered\nQ: Is the PDF plugin currently working? (asked by Beja) A: Yes, it's available at github.com/elizaos-plugins/plugin-pdf and was updated 2 weeks ago (answered by Kenk)\nQ: How can my AI agent with Twitter client post images with text? (asked by TruffleSoul) A: Unanswered\nQ: Is it possible to run 2 different characters in the same machine? (asked by [elizaos] ) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: BowTiedBlueFin | Context: Needed to use custom OpenAI API compatible provider | Resolution: Suggested creating a new plugin and provided documentation links\nHelper: Kenk | Helpee: [elizaos] | Context: User unable to see auto.fun channels history | Resolution: Added verified tag to user's profile to grant access\nHelper: Kenk | Helpee: Beja | Context: User asking if PDF plugin is working | Resolution: Confirmed it's available and provided GitHub repository link\nHelper: Zarathustra | Helpee: FlipWhale | Context: Issues with plugin-image-generation | Resolution: Suggested attending ElizaOS office hours for Q&A with Shaw\nHelper: Kenk | Helpee: FlipWhale | Context: Issues with plugin-image-generation | Resolution: Shared calendar link for dev rel weekly office hours\n\n## 4. Action Items\nTechnical: Review and merge pull request for plugin-zilliqa | Description: PR #1 has been tested and is ready for merging | Mentioned By: mtbc\nTechnical: Fix CSP issues with V2 on Windows machines | Description: Content Security Policy triggering from eval statement | Mentioned By: [elizaos] \nTechnical: Investigate Twitter post issues in Version 1.0.0-beta | Description: Verify if Twitter posting functionality is working properly | Mentioned By: AK\nTechnical: Fix build issues in v2-develop branch | Description: src/commands/create.ts has import issues | Mentioned By: lantianlaoli\nTechnical: Add DeepSeek support to V2 | Description: User unable to find plugin for DeepSeek LLM | Mentioned By: [elizaos] \nTechnical: Fix agent creation REST endpoint issue | Description: Not getting agent ID back from the endpoint | Mentioned By: [elizaos] \nFeature: Support for custom OpenAI-compatible LLM providers | Description: Allow setting custom base URL and API key | Mentioned By: BowTiedBlueFin\nFeature: Configure agents to reply to replies of target accounts | Description: Agent missing replies as they aren't posts | Mentioned By: [elizaos] \nFeature: Prevent agent selecting \"None\" action on repeated questions | Description: Agent ignores and doesn't call action | Mentioned By: happylol123\nDocumentation: Create tutorial for new project setup and first steps using v2 | Description: Users need guidance on v2 implementation | Mentioned By: [elizaos] ", "messageCount": 58, "userCount": 17 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "The chat contains a single message from Mr. Nucleus proposing a technofeudalist DAO concept. The idea involves creating a DAO with token value backed by physical land assets. Mr. Nucleus states they already possess the land and have established a DAO structure, but no tokens have been distributed yet. They are seeking both funding for the project and guidance on governance mechanisms for the DAO. No further discussion, responses, or technical details were provided in the chat segment.", "messageCount": 1, "userCount": 1 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Analysis of \"spartan_holders\" Discord Channel\n\n## 1. Summary\nThe chat segment is extremely brief, containing only three messages from two users (Void and Preshtime). There are no detailed technical discussions or problem-solving activities in this limited exchange. The conversation merely indicates anticipation for upcoming V2 updates to both \"auto.fun creations\" and \"Spartan\" products. One user (Void) acknowledges seeing a \"featured\" item and later inquires about the expected release timeframe for V2, specifically asking if it might be released within the current month. No technical details, implementations, or concrete solutions are discussed in this brief exchange.\n\n## 2. FAQ\nQ: May we expect the release of V2 sometime this month? (asked by Void) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions are present in this chat segment.\n\n## 4. Action Items\nFeature: V2 updates for auto.fun creations and Spartan | Description: Upcoming version 2 releases mentioned as in development | Mentioned By: Preshtime", "messageCount": 3, "userCount": 2 }, { "channelId": "1351627860351258685", "channelName": "dao-organization", "summary": "# Discord Channel Analysis: dao-organization\n\n## 1. Summary\nThe chat segment shows discussions about token sentiment, particularly regarding ai16z token and its challenges. HoneyBadger raises concerns about the lack of coherent messaging around the token, noting that early narratives about GitHub stars, forks, and launchpad functionality have faded. There's uncertainty about whether autofun (apparently a recently launched product) can generate sufficient revenue to create buyback pressure. Kenk mentions upcoming communications about tokenomics. The conversation also touches on a debate about priorities in the ecosystem, with references to a statement from someone named Alon that emphasizes liquidity over other aspects. Some members disagree with this take, arguing that developers and creators are essential to having products to trade in the first place. There's also a brief mention of Chinese market attention for a token launch.\n\n## 2. FAQ\nQ: What are some additions being worked on to expand the tokenomic beyond buyback & \"dao\"? (asked by HoneyBadger) A: Unanswered\nQ: Are you using anything to track sentiment? (asked by Kenk) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: HoneyBadger | Context: Tracking token sentiment | Resolution: Kenk suggested using cookie.fun tracker and mentioned upcoming tokenomics communications\n\n## 4. Action Items\nTechnical Tasks: None explicitly mentioned\nDocumentation Needs: Description: Share communications around tokenomics | Mentioned By: Kenk\nFeature Requests: Description: Expand tokenomics beyond buyback & \"dao\" | Mentioned By: HoneyBadger", "messageCount": 11, "userCount": 7 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Discord Chat Analysis for \"fun\" Channel\n\n## 1. Summary\nThe chat primarily revolves around issues with the auto.fun platform during a maintenance period and upgrade. Users reported problems with token creation, where some tokens were created but liquidity pools weren't properly established, leaving users unable to sell tokens. The team acknowledged an indexing issue affecting early token migrations and worked to resolve it. The platform underwent database upgrades and feature additions, causing downtime that concerned users. A security incident occurred where Shaw's Twitter account was compromised, with the attacker creating a token called \"COO\" on Pump.fun. Team members warned users not to engage with this token. Throughout the downtime, team members provided updates but avoided giving specific ETAs, noting they were working around the clock to resolve issues and implement improvements.\n\n## 2. FAQ\nQ: Are you guys not planning to migrate shawai? (asked by hxf) A: There is an indexing issue impacting some tokens migration, we're working to resolve that asap (answered by eskender.eth)\nQ: How long will it take I wanna be able to use the app? (asked by noj) A: There are no known issues with any tokens being created now. It is solely limited to some of the early token creations. (answered by accelxr)\nQ: Anywhere we can see total volume for autofun? (asked by wire) A: Third party tools (answered by Zolo)\nQ: Is shaw hacked? (asked by Puppet) A: Shaw's account has been compromised. The attacker used the breach to issue a token called \"COO\" on Pump.fun - DO NOT ENGAGE (answered by eskender.eth)\nQ: Are there any agentic features in the current auto.fun release? (asked by 0xFastly) A: This is the core of it atm, the platform will be used as part of the DX for agent creation of V2 (answered by Kenk)\nQ: So a quick tldr for auto fun would be a simpler way of launching agents vs having to code one? (asked by flockaflame) A: That the core of the experience for now, we want to get users engaged with token and content creation in a fun way - once thats nailed, we can explore \"agentic\" features that boost that experience (answered by eskender.eth)\nQ: What is the cost to purchase tokens during token creation? (asked by 0xConsole) A: There is a calculator on the screen when you input the value, but idk the exact math off the top of my head (answered by eskender.eth)\nQ: What sort of issues were you guys facing? (asked by Penguin) A: Unanswered\nQ: Why is it taking so long? (asked by Penguin) A: Quite the opposite, we had to upgrade the DB and have added a few new features. This is just the start. Much to look forward to. (answered by Kenk)\n\n## 3. Help Interactions\nHelper: accelxr | Helpee: noj | Context: User had issues with tokens not working and SOL being stuck | Resolution: Issue was resolved, user confirmed \"It worked\"\nHelper: Kenk | Helpee: xw | Context: User created a token but no pool was created for it | Resolution: Kenk responded in support channel\nHelper: jasyn_bjorn | Helpee: Penguin | Context: User concerned about silence and timeline for platform relaunch | Resolution: Explained devs working around the clock with progress being made\nHelper: phetrusrodrigues ✈ | Helpee: Pyroman | Context: User didn't understand the abbreviation \"DB\" | Resolution: Explained it means \"Database\"\n\n## 4. Action Items\nType: Technical | Description: Resolve indexing issue impacting token migrations | Mentioned By: eskender.eth\nType: Technical | Description: Fix liquidity pool creation for affected tokens | Mentioned By: noj\nType: Technical | Description: Complete database upgrade for platform stability | Mentioned By: Kenk\nType: Feature | Description: Implement agentic features in future platform versions | Mentioned By: eskender.eth\nType: Feature | Description: Develop token volume tracking/analytics capabilities | Mentioned By: wire\nType: Documentation | Description: Provide clear explanation of token creation costs and calculations | Mentioned By: 0xConsole\nType: Documentation | Description: Update messaging around \"locked\" status for tokens | Mentioned By: shaw\nType: Technical | Description: Address platform stability issues causing frequent up/down status | Mentioned By: anon", "messageCount": 120, "userCount": 34 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "# Analysis of \"fun-support\" Discord Channel\n\n## 1. Summary\nThe Discord channel shows users experiencing issues with the Auto.fun platform, which appears to be a token creation and trading platform on Solana. The main technical issues revolve around token indexing problems for tokens created during or shortly after launch. Many users reported creating tokens that took their SOL but didn't properly create trading pools or appear on the platform. The development team, primarily represented by accelxr, has been manually fixing these issues by importing affected tokens. The platform underwent multiple maintenance periods to address these problems. Two distinct contract addresses were mentioned: the official one and a \"developer contract\" (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5) that was apparently leaked before launch. Tokens created on the developer contract couldn't be recovered. Other issues included problems with the \"Claim Fees\" function, sorting filters not working correctly, and UI bugs. The platform has a bonding curve mechanism where tokens migrate to Raydium after reaching 85 SOL in the curve (approximately 60k market cap).\n\n## 2. FAQ\nQ: Why can't I see or trade my token after creation? (asked by multiple users) A: 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)\nQ: What happens to tokens created using the leaked developer link? (asked by multiple users) A: These tokens cannot be recovered as they were created on a different contract than the official one. (answered by accelxr)\nQ: When does a token migrate from the bonding curve? (asked by Pyroman) A: When it reaches 85 SOL in the bonding curve, approximately 60k market cap. (answered by accelxr)\nQ: How does the \"Claim Fees\" function work? (asked by Xyness) A: Post-bonding, token creators can claim fees from the LP, receiving a combination of the created token and SOL. (answered by accelxr)\nQ: What is the fee split for token creators? (asked by Xyness) A: It's a 90/10 split for the token owner and the platform respectively. (answered by Borko)\nQ: Is there a way to add our website to our auto.fun page? (asked by 🧧ThanosDaSith24🧧) A: Unanswered\n\n## 3. Help Interactions\nHelper: accelxr | Helpee: NotYourBudi | Context: User created a token but no LP was created | Resolution: Identified as an indexing error that would be resolved\nHelper: accelxr | Helpee: FatalPie | Context: Token \"eddy\" was stuck in migration for 2 days | Resolution: Successfully migrated the token\nHelper: accelxr | Helpee: Prowler | Context: Token was created but not showing up | Resolution: Fixed the token page and made it accessible\nHelper: accelxr | Helpee: uloze | Context: User had multiple failed token creation attempts | Resolution: Identified which tokens were recoverable and added them to import list\nHelper: accelxr | Helpee: MONO | Context: Token created before official launch not showing up | Resolution: Added to manual fix list\nHelper: Kenk | Helpee: bheau | Context: Early tokens from developer program not migrated | Resolution: Added to migration list for manual handling\n\n## 4. Action Items\nType: Technical | Description: Fix indexing issues for tokens created during early launch | Mentioned By: Multiple users\nType: Technical | Description: Fix \"Claim Fees\" function that's returning errors | Mentioned By: Xyness\nType: Technical | Description: Fix bonding curve percentage display in UI | Mentioned By: Pyroman\nType: Technical | Description: Fix sorting filters (bonding, age) not working correctly | Mentioned By: Curtisdonthurtus\nType: Technical | Description: Fix list view UI where left tab selection disappears | Mentioned By: HoneyBadger\nType: Technical | Description: Remove test tokens from the platform | Mentioned By: Pyroman\nType: Technical | Description: Fix volume and holder data sometimes showing as zero | Mentioned By: HoneyBadger\nType: Feature | Description: Add ability to include website information on token pages | Mentioned By: 🧧ThanosDaSith24🧧\nType: Feature | Description: Add two parameters for sorting (bonding and time, or bonding and MC) | Mentioned By: Curtisdonthurtus\nType: Feature | Description: Add bonding curve percentage to Telegram bot data | Mentioned By: MONO\nType: Feature | Description: Create statistical dashboard with platform metrics | Mentioned By: Moliza", "messageCount": 331, "userCount": 40 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Analysis of 🥇-partners Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around auto.fun, a recently launched platform similar to pump.fun but with AI integration capabilities. The platform experienced several technical issues during launch, including indexing problems with early tokens that required manual migration. The site went into maintenance mode for upgrades after experiencing high traffic. Users reported specific bugs including claim fee button not working, Jupiter errors on price detection for percentage-based sells (25%, 50%, 75%), and issues with token liquidity. \n\nThe team is working on fixes before proceeding with marketing activities and launching partnerships. There are discussions about potential AI agent integration with tokens created on the platform, with suggestions about using token fees to power AI agents. Some users created tokens like $CRIME and $FUN on the platform and shared their experiences. There's also mention of Shaw's account being compromised at one point, leading to a suspicious token called \"COO\" being issued.\n\nThe chat also includes discussions about upcoming demos for agent projects, including Smolverse's Neurochimp which appears to integrate NFTs with memory functions.\n\n## 2. FAQ\nQ: What is the current status of auto.fun? (asked by anon) A: The site is temporarily in maintenance mode while updates are being merged and the platform is being optimized before marketing begins. (answered by Kenk)\nQ: What were the main issues with auto.fun at launch? (asked by kalshnikov) A: Initial issues included backend overload and indexing problems where some tokens created early didn't get indexed and had to be manually migrated. (answered by accelxr)\nQ: Why is the Jupiter error happening on percentage-based sells? (asked by accelxr) A: It appears to be related to too many decimals in the calculations. (answered by accelxr)\nQ: What is the fee split for tokens on auto.fun? (inferred from Kenk's message) A: 90/10 split between the creator and platform, with the platform portion going to $ai16z buybacks. (answered by Kenk)\nQ: Is Shaw's account compromised? (asked by siggy) A: Yes, the attacker used the breach to issue a token called \"COO\" on Pump.fun. (answered by eskender.eth)\nQ: When will auto.fun be back online? (asked by anon) A: After maintenance is complete and the platform is confirmed fully stable, followed by a large marketing push. (answered by accelxr)\nQ: What are the launch partners for auto.fun? (asked by litn) A: They are ready to deploy but waiting for platform polishing before starting marketing activity. (answered by Kenk)\nQ: Why can't I use I and O in token suffixes? (asked by yikesawjeez) A: Because you can only use base58 encoding. (answered by accelxr)\n\n## 3. Help Interactions\nHelper: accelxr | Helpee: yikesawjeez | Context: Jupiter errors on percentage-based sells (25%, 50%, 75%) | Resolution: Identified the issue as too many decimals in calculations, suggested removing the last number to fix and fetch properly.\nHelper: Kenk | Helpee: Channel members | Context: Provided a comprehensive update on auto.fun status | Resolution: Explained successful launch despite issues, indexing problems being fixed, and plans for launch partners.\nHelper: yikesawjeez | Helpee: iprintmoney | Context: Helping navigate a hidden puzzle/game on tournament.x-ware.online | Resolution: Successfully guided user through accessing a hidden AI character interaction.\nHelper: accelxr | Helpee: anon | Context: Question about liquidity pairing being off | Resolution: Explained that pairing is off for some test coins due to lowered bonding curve for mainnet testing.\n\n## 4. Action Items\nType: Technical | Description: Fix claim fees button that's currently broken | Mentioned By: yikesawjeez\nType: Technical | Description: Fix Jupiter error on price detection for percentage-based sells (25%, 50%, 75%) | Mentioned By: yikesawjeez\nType: Technical | Description: Address token balance/value using cached data issue | Mentioned By: yikesawjeez\nType: Technical | Description: Resolve backend overload issues causing maintenance mode | Mentioned By: accelxr\nType: Technical | Description: Implement model switching capability for agents to dynamically swap LLMs based on evaluation criteria | Mentioned By: DorianD\nType: Feature | Description: Create mechanism for tokens to fund their own AI agents through fee allocation | Mentioned By: DorianD\nType: Feature | Description: Add database functionality to tournament.x-ware.online to track user profiles | Mentioned By: yikesawjeez\nType: Documentation | Description: Update language to clarify token mechanics to prevent confusion | Mentioned By: yikesawjeez", "messageCount": 311, "userCount": 27 } ] }