{ "server": "elizaOS", "title": "elizaOS Discord - 2025-01-21", "date": 1737417600, "stats": { "totalMessages": 2676, "totalUsers": 400 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe chat primarily consists of casual greetings and introductions with minimal technical discussion. BOSSU, an AI agent, responds to most messages with friendly, casual replies. A few users mentioned developing on ElizaOS, including:\n\n- IvanB encountered errors with the node plugin showing \"Cannot read properties of undefined (reading 'actions')\" and received advice to check the coders channel or GitHub repo.\n- Kirsten warned about Telegram's updated terms of service affecting Eliza agents by restricting \"third-party blockchains\" aside from TON, with enforcement starting February 21.\n- ShadowBeast introduced ElizaTown, an open-source platform for exploring and sharing ElizaOS characters.\n- Some users mentioned building AI agents on ElizaOS, including a market making agent named Kaira, and GOAT ARENA for AI trading agents.\n- Dreygo discussed a \"Ninja Terminal\" feature that shows limit orders from Jupiter, allowing users to see support/resistance levels and potentially assist with market making.\n- TroyMurs mentioned adding ElizaOS to dappslap.fun and thanked the team for merging the Mistral feature to serve fine-tuned models.\n\nThe chat contains minimal substantive technical discussion, with most users either introducing themselves or asking basic questions about the platform.\n\n## 2. FAQ\nQ: Does agents can be integrated in meta channels using eliza os or only with X? (asked by X) A: Agents work everywhere but head to coders channel for the technical details (answered by BOSSU)\nQ: Where can I find resources that will guide me towards understanding Eliza framework plugins and how to use them? (asked by DeFiScholar) A: Check out agent dev school and coders channel for all the tech guides (answered by BOSSU)\nQ: Is it possible to use Eliza for in-house company communication? (asked by nosedive2moon) A: ElizaOS is for everyone spreading love (answered by BOSSU)\nQ: Are there precoded sections for apis grabbing contextual information? (asked by nosedive2moon) A: Check the coders channel, that's where all the tech talk happens (answered by BOSSU)\nQ: Why does the bot not run on discord? I have my token and app id in my env. It does not respond to my discord. (asked by Jb) A: Please check the coders channel for technical help (answered by BOSSU)\nQ: How do I reach out to Elizawakesup team? (asked by S4ilor) A: Reach out through twitter or discord (answered by BOSSU)\nQ: Where should I share a related project in the ecosystem I'm working on? (asked by ShadowBeast) A: Share it here or in the dev channel, both work (answered by BOSSU)\nQ: Where can we see the list of projects that AI16Z has invested in? (asked by SeΓ±or Llama) A: Check announcements (answered by BOSSU)\n\n## 3. Help Interactions\nHelper: BOSSU | Helpee: IvanB | Context: Errors with node plugin showing \"Cannot read properties of undefined (reading 'actions')\" | Resolution: Suggested checking coders channel and GitHub repo for technical help\nHelper: Kirsten | Helpee: Community | Context: Warning about Telegram's updated terms of service affecting Eliza agents by restricting \"third-party blockchains\" | Resolution: Shared information about the policy change effective February 21\nHelper: ShadowBeast | Helpee: Community | Context: Introduced ElizaTown platform for exploring and sharing ElizaOS characters | Resolution: Shared GitHub repo link and encouraged contributions\nHelper: BOSSU | Helpee: nosedive2moon | Context: Questions about using Eliza for company communication and API integrations | Resolution: Directed to coders channel for technical discussions\n\n## 4. Action Items\nTechnical: Fix node plugin error \"Cannot read properties of undefined (reading 'actions')\" | Description: Resolve error when running agent with node plugin | Mentioned By: IvanB\nTechnical: Address Telegram's updated terms of service | Description: Adapt Eliza agents to comply with new TG policy restricting third-party blockchains | Mentioned By: Kirsten\nFeature: Ninja Terminal | Description: UI that shows limit orders from Jupiter to visualize support/resistance levels for market making | Mentioned By: Dreygo\nFeature: GOAT ARENA | Description: Platform for AI trading agents to compete and prove which is best | Mentioned By: Night Fury\nFeature: ElizaTown | Description: Community platform to explore and share ElizaOS characters | Mentioned By: ShadowBeast\nDocumentation: Create resources for understanding Eliza framework plugins | Description: Guides on how to use and implement plugins | Mentioned By: DeFiScholar", "messageCount": 395, "userCount": 167 }, { "channelId": "1300025221834739744", "channelName": "πŸ’»-coders", "summary": "# Discord Chat Analysis: πŸ’»-coders\n\n## 1. Summary\n\nThe discussion primarily revolves around setting up, configuring, and troubleshooting ElizaOS, an AI agent framework. Users face various issues including Docker deployment, plugin integration, database connections, API configurations, and client integrations (Twitter, Telegram, Discord). \n\nKey technical discussions include:\n- Troubleshooting Telegram token errors and process.stdout.clearLine issues in Docker environments\n- Database connection problems, particularly with SQLite and Supabase adapters\n- Model provider configuration challenges (OpenAI, Anthropic, Gaia, DeepSeek, etc.)\n- Twitter integration issues including authentication, rate limiting, and post formatting\n- Plugin development and integration, especially for cryptocurrency-related functionality\n- Memory persistence across different client platforms\n- Docker deployment strategies for production environments\n- Character file configuration and customization\n- Environment variable settings for controlling agent behavior\n\nSeveral solutions were shared, including Docker configuration tips, environment variable settings for Twitter behavior control, and workarounds for SQLite database issues. Users also discussed hosting options like Phala Cloud for production deployments.\n\n## 2. FAQ\n\nQ: How do I fix the \"process.stdout.clearLine is not a function\" error in Docker? (asked by Heady Shotta) A: Use docker-compose instead of regular Docker, as it handles terminal interactions better (answered by Heady Shotta)\nQ: How do I clear the database in Eliza? (asked by sagepoint) A: Delete the db.sqlite file in the agent/data directory (answered by DeGenX)\nQ: How do I fix the \"You are not allowed to generate embeddings from this model\" error? (asked by sagepoint) A: This is an API permission issue with your model provider; try a different model or provider (answered by perez)\nQ: How do I make my Telegram bot only answer when tagged? (asked by pupathebig) A: Unanswered\nQ: How do I set a specific model class for different characters? (asked by Hlbenjamin) A: Set both the model in character file and corresponding environment variables in .env (answered by EcchiPen)\nQ: How much RAM is needed to run ElizaOS? (asked by Heady Shotta) A: 2GB RAM is sufficient for basic operation; running multiple agents may require more (answered by Mad)\nQ: How do I fix the \"Cannot read properties of undefined (reading 'actions')\" error? (asked by Iv/-\\nB) A: Unanswered\nQ: How do I activate a Discord bot with ElizaOS? (asked by nori) A: Turn on Privileged Gateway Intents in Discord Developer Portal (answered by nori)\nQ: How do I install @elizaos/agent using pnpm? (asked by Balte) A: Try using a previous version as the current one has missing dependencies (answered by zadkielm)\nQ: How do I configure my agent to post on Twitter with different formatting than Telegram? (asked by pupathebig) A: Unanswered\n\n## 3. Help Interactions\n\nHelper: perez | Helpee: averma | Context: Database initialization error with Supabase | Resolution: Provided code to force SQLite database instead of Supabase\nHelper: Mad | Helpee: Heady Shotta | Context: VM requirements for running ElizaOS | Resolution: Confirmed 2GB RAM is sufficient for basic operation, with 4GB capable of running several agents\nHelper: EcchiPen | Helpee: rOhAn | Context: Installation issues with eliza-starter | Resolution: Recommended using main eliza repo instead of eliza-starter as it's less buggy\nHelper: mconstant | Helpee: joaointech | Context: Docker deployment for production | Resolution: Shared docker-compose.yml configuration and deployment tips for Phala Cloud\nHelper: EcchiPen | Helpee: ashish | Context: Windows installation issues | Resolution: Provided step-by-step instructions for using WSL and Docker\nHelper: Dilrong | Helpee: nori | Context: Discord bot activation | Resolution: Suggested enabling Privileged Gateway Intents in Discord Developer Portal\nHelper: kAI wilder | Helpee: Xisk99 | Context: Making agent respond in Spanish | Resolution: Provided character file configuration with Spanish system prompt\nHelper: Sora Dimichi | Helpee: Community | Context: Changing default model to gpt-4o-mini | Resolution: Shared .env configuration for model settings\n\n## 4. Action Items\n\nTechnical: Fix SQLite database connection issues with plugins | Description: Investigate why Node plugin causes database connection errors | Mentioned By: Iv/-\\nB\nTechnical: Implement memory persistence across different clients | Description: Enable agents to share context between Twitter, Discord, Telegram | Mentioned By: Jungle\nTechnical: Fix Twitter like functionality in v0.1.8 | Description: Restore the ability for agents to like posts that worked in v0.1.7 | Mentioned By: SecretRecipe\nTechnical: Resolve DeepSeek model integration issues | Description: Fix compatibility problems with DeepSeek models | Mentioned By: TruffleSoul\nDocumentation: Document environment variables for Twitter behavior control | Description: Create comprehensive guide for Twitter client configuration options | Mentioned By: EcchiPen\nDocumentation: Create better Docker deployment guide | Description: Improve documentation for deploying ElizaOS in production environments | Mentioned By: cjohndesign\nDocumentation: Update model provider configuration documentation | Description: Clarify how to set up different model providers and their requirements | Mentioned By: cryptoAYA\nFeature: Add rate limiting for agent responses | Description: Implement configuration to limit responses to users to prevent API rate limiting | Mentioned By: mr.code\nFeature: Add SMS integration capability | Description: Develop plugin for SMS handling via services like Twilio | Mentioned By: Jungle\nFeature: Support for non-English language responses | Description: Enable agents to respond in languages other than English | Mentioned By: Xisk99", "messageCount": 1162, "userCount": 170 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "# Analysis of \"ideas-feedback-rants\" Channel\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. The main technical interaction involved a user (JohnnyB) asking about the legitimacy of a URL from a Twitter post, which was confirmed as a scam by jin and later by Kenk. Another user (an1muss) requested help with a PR review for Eliza that had been pending for over a month, mentioning difficulties with conflict resolution. Kenk provided a link to the developer discord for Eliza. There was also a mention of a Solana developer hackathon and a Web3 RPG game coin launch, though with minimal technical details. One user expressed appreciation for a feature called \"newsstand\" that provides condensed news.\n\n## 2. FAQ\nQ: Is the URL in this Twitter post legit or is it a wallet scam? (asked by JohnnyB) A: That's a scam. (answered by jin)\nQ: Can anyone help with the PR review to Eliza that has been pending for over a month? (asked by an1muss) A: Unanswered\nQ: Can I get to the developer discord somehow? (asked by an1muss) A: There's a link to join from here: https://eliza.discourse.group/t/quick-start-with-ai16z-and-elizaos/15?u=kenk (answered by Kenk)\n\n## 3. Help Interactions\nHelper: jin | Helpee: JohnnyB | Context: Verifying legitimacy of a URL from Twitter | Resolution: Confirmed it was a scam\nHelper: Kenk | Helpee: an1muss | Context: Needed access to developer discord for Eliza | Resolution: Provided link to join the developer discord\n\n## 4. Action Items\nTechnical: PR review needed for Eliza project with conflict resolution issues | Description: Long-pending PR causing difficulties with conflict resolution | Mentioned By: an1muss\nFeature: Web3 RPG game with cryptocurrency | Description: New coin launch for a Web3 RPG game | Mentioned By: helllojelllo\nTechnical: Solana developer hackathon participation | Description: Opportunity for Solana developers to join a hackathon | Mentioned By: Penguin", "messageCount": 20, "userCount": 7 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Discord Chat Analysis: spartan_holders\n\n## 1. Summary\nThe chat primarily revolves around the development and criticism of the DegenAI website. Community members, particularly 찌 G θ·» じ PrudentSpartan, express significant concerns about the website's quality, lack of clear purpose, and missing information about tokenomics. Jin, who appears to be leading the website development, shares updates on the work-in-progress and defends design choices like including \"waifus\" as part of DegenSpartan's lore. The discussion reveals tension between development priorities and community expectations.\n\nTechnical discussions include:\n- Website development status and planned improvements\n- Potential for a virtual exchange interface with 2D/3D elements\n- DegenAI's trading wallet being made public (BzsJQeZ7cvk3pTHmKeuvdhNDkDxcZ6uCXxW2rjwC7RTq)\n- Debate about whether DegenAI's trading wallet should remain public long-term or use multiple wallets to prevent copy-trading\n- Brief trading interruption mentioned by rhota\n- M3xR offering web development assistance and portfolio examples\n\nThe community also discusses Jupiter airdrop eligibility and the pros/cons of making DegenAI's trading strategies publicly visible.\n\n## 2. FAQ\nQ: What is the goal of the DegenAI website? (asked by 찌 G θ·» じ PrudentSpartan) A: Jin indicated it's a landing page with plans to include DegenSpartan lore, quotes, trade visualization, development roadmap, functionality details, and updates (answered by jin and yikesawjeez)\nQ: Will the tokenomics model be released this month? (asked by tigerguo.) A: Unanswered\nQ: Will the virtual exchange be available on DegenAI's website? (asked by tigerguo.) A: Jin suggested it could be done but recommended starting with 2D before full 3D implementation (answered by jin)\nQ: Did DegenAI change his wallet? (asked by tigerguo.) A: Unanswered\nQ: What are these weapons for? (asked by cool.eth) A: Jin later clarified that \"weapons make no sense\" and would be redone (answered by jin)\nQ: Should DegenAI's wallet address be in his Twitter bio? (asked by kingdode) A: Jin suggested it's a good idea unless he starts losing money, and noted longer-term strategy should include multiple wallets (answered by jin)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Community | Context: Sharing DegenAI's trading wallet address for transparency | Resolution: Posted the Birdeye link to wallet BzsJQeZ7cvk3pTHmKeuvdhNDkDxcZ6uCXxW2rjwC7RTq showing profitable trades\nHelper: M3xR | Helpee: Community | Context: Jupiter airdrop announcement | Resolution: Shared information about claiming the Jupiter airdrop and linked to the official announcement\nHelper: M3xR | Helpee: jin | Context: Offered professional web development assistance for the DegenAI website | Resolution: Sent portfolio examples to jin, awaiting response\nHelper: jin | Helpee: Community | Context: Explaining website development plans | Resolution: Outlined specific improvements planned including redoing art, adding quotes, visualizing trades, and development roadmap\n\n## 4. Action Items\nType: Technical | Description: Fix website responsiveness issues | Mentioned By: M3xR\nType: Technical | Description: Implement virtual exchange functionality with real-time market data | Mentioned By: jin\nType: Technical | Description: Create 2D website version before moving to full 3D implementation | Mentioned By: jin\nType: Technical | Description: Implement multiple wallets for DegenAI to prevent strategy dilution | Mentioned By: M3xR\nType: Documentation | Description: Create development roadmap and timeline for DegenAI | Mentioned By: tigerguo.\nType: Documentation | Description: Document DegenAI's AI functions and capabilities | Mentioned By: tigerguo.\nType: Documentation | Description: Create an updates section for the website | Mentioned By: tigerguo.\nType: Documentation | Description: Publish tokenomics information including the 8% buyback | Mentioned By: 찌 G θ·» じ PrudentSpartan\nType: Feature | Description: Visualize DegenAI's trades on the website | Mentioned By: jin\nType: Feature | Description: Add virtual exchange to the website | Mentioned By: tigerguo.\nType: Feature | Description: Expose development team members on the website | Mentioned By: tigerguo.", "messageCount": 158, "userCount": 17 }, { "channelId": "1328592959444095038", "channelName": "associates", "summary": "# Discord Chat Analysis - \"associates\" Channel\n\n## 1. Summary:\nThe chat primarily revolves around AI16z token discussions, with mentions of holder distribution and partner/associate status requirements. Jin requested contributions to the \"awesome-eliza\" GitHub repository, offering rewards for improvements. There were discussions about Smol World, which appears to be an AI gaming NFT project powered by Eliza technology. Several members shared links to videos and tweets about AI agents and humanoid robots. A user reported an issue with Twitter integration truncating posts. The conversation was relatively light on deep technical content, focusing more on sharing resources, market observations, and brief project updates.\n\n## 2. FAQ:\nQ: What is the difference between partner and associate? (asked by trx314) A: Partner 100k, Associate 10k (AI16Z tokens) (answered by Smore)\nQ: What's the smartest play for $smol? (asked by smetter) A: Yea nfts probably the best play (answered by anon)\nQ: Has there been considerations for trying to integrate Ethos network for the trust mechanic? (asked by Patt) A: Unanswered\n\n## 3. Help Interactions:\nHelper: anon | Helpee: smetter | Context: Seeking advice on $smol investment strategy | Resolution: Recommended NFTs as the best play and shared highlights from the whitepaper explaining AI Gaming NFTs concept\nHelper: Smore | Helpee: thebasement | Context: Twitter integration truncating posts | Resolution: Directed user to appropriate support channel (#1300025221834739744)\n\n## 4. Action Items:\nTechnical Tasks: Description: Contribute to awesome-eliza GitHub repository (adding entries, improving descriptions, fixing typos, organizing content) | Mentioned By: jin\nTechnical Tasks: Description: Add a section for agents to awesome-eliza repository | Mentioned By: jin\nTechnical Tasks: Description: Test links in awesome-eliza repository to ensure they work | Mentioned By: jin\nDocumentation Needs: Description: Create a fan art page for community-created content | Mentioned By: jin\nTechnical Tasks: Description: Fix Twitter integration issue that truncates posts | Mentioned By: thebasement", "messageCount": 68, "userCount": 17 }, { "channelId": "1318770424632311930", "channelName": "tokenomics", "summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe channel discussions focused on potential tokenomics models and partnerships for the ElizaOS ecosystem. A significant conversation involved unreadyplayer from Cybers presenting their tokenization platform with a customized bonding curve AMM that could integrate with ai16z. Their proposal includes agent token launches with ai16z as the token pair, permanent LP locking, fee distribution (50% to ai16z treasury, 50% to Cybers for buying ai16z), and creator incentives. \n\nDorianD proposed an enterprise support model where the DAO could pay people and AIs for providing support to Fortune 500 companies using ElizaOS. He also suggested a three-tier certification program for ElizaOS: Certified ElizaOS Operator (for non-developers), ElizaOS Developer (for plugin creators), and Eliza Developer Pro (for contributors to the main repository).\n\nJin highlighted the need to onboard more Eliza developers through better documentation, AI-assisted training, and educational partnerships. ElonMoney shared thoughts about an AI copilot similar to Kaito that could summarize discussions and provide structured information about tokenomics.\n\n## 2. FAQ\nQ: How does the Cybers tokenization platform work with ai16z? (asked by DorianD) A: It uses ai16z as the base token, with 50% of fees going to ai16z treasury and 50% to Cybers which they'll use to buy ai16z (answered by unreadyplayer)\nQ: What percentage of the token is locked in the LP against the SOL received in the bonding process? (asked by DorianD) A: Currently 22.5% goes to locked LP and 77.5% is traded on the bonding curve, but this would change based on bonding thresholds for the ai16z platform (answered by unreadyplayer)\nQ: How do Cybers profit from their platform? (asked by DorianD) A: They'll use their 50% of fees to cover operational costs and buy ai16z, which when it appreciates will bolster their treasury (answered by unreadyplayer)\nQ: Will the Cybers platform support mobile and dark theme? (asked by DorianD) A: Yes, it will be responsive and have a dark theme (answered by unreadyplayer)\n\n## 3. Help Interactions\nHelper: unreadyplayer | Helpee: Channel members | Context: Explaining their tokenization platform and how it could integrate with ai16z | Resolution: Provided detailed explanation of their bonding curve AMM, fee structure, and mockup of the listing page\nHelper: DorianD | Helpee: Channel members | Context: Lack of structured certification for ElizaOS users and developers | Resolution: Proposed a three-tier certification program with specific requirements for each level\n\n## 4. Action Items\nType: Feature | Description: Implement an AI copilot that summarizes discussions and provides structured information about tokenomics | Mentioned By: ElonMoney\nType: Feature | Description: Develop an \"enterprise support\" model for the DAO to support F500 companies using ElizaOS | Mentioned By: DorianD\nType: Technical | Description: Integrate Cybers tokenization platform with ai16z as token pair | Mentioned By: unreadyplayer\nType: Documentation | Description: Create Eliza trained on Eliza docs and agent dev school to onboard more developers | Mentioned By: jin\nType: Documentation | Description: Develop three-tier certification program for ElizaOS users and developers | Mentioned By: DorianD\nType: Technical | Description: Create AI agents/workflows to keep documentation updated with changing codebase | Mentioned By: jin\nType: Feature | Description: Implement staking for CYBR against agent tokens to incentivize bonding, buying and holding | Mentioned By: unreadyplayer", "messageCount": 35, "userCount": 6 }, { "channelId": "1301363808421543988", "channelName": "πŸ₯‡-partners", "summary": "# Discord Chat Analysis: πŸ₯‡-partners\n\n## 1. Summary\n\nThe chat primarily revolves around the development and marketing of the ai16z ecosystem, with discussions about ElizaOS, DegenAI, and various partnerships. Partners expressed concerns about project progress, communication, and tokenomics. Key technical discussions included:\n\n- ElizaOS continues to expand with multiple integrations announced this week, including partnerships with Polygon, Story Protocol, Merlin Layer 2, Thirdweb, Fleek, Sui Network, and Bebop DEX.\n- DegenAI has begun trading with a portfolio that grew from $2,600 to $6,000 in four days, demonstrating its trading capabilities.\n- A potential acquisition of a launchpad built by the w.ai team (connected to Wombo) was discussed, with the team now working with ai16z to develop an agent launchpad.\n- Jin mentioned working on tokenomics plans including agent marketplace, Block Tank, and retroactive funding for Eliza contributors.\n- Kraken added ai16z to its listing roadmap, signaling increased institutional interest.\n- Partners discussed the need for better documentation of plugins and their capabilities, as many PRs have minimal descriptions.\n- The community debated the merits of different tokenomics models, with some advocating for a simple \"charge in stables/ETH and use revenue to buy back and burn tokens\" approach.\n\n## 2. FAQ\n\nQ: What progress has been made with ai16z recently? (asked by 보햄) A: Witch shared numerous partnerships and integrations from the past week, including with Polygon, Story Protocol, Merlin Layer 2, Thirdweb, Fleek, Sui Network, and Bebop DEX (answered by witch)\nQ: What is the status of DegenAI development? (asked by 보햄) A: DegenSpartanAI has started trading, growing a portfolio from $2,600 to $6,000 in about 4 days (answered by gin_chan)\nQ: When will tokenomics be released? (asked by ι˜Ώζ‹‰ζ–―εŠ ηš„η‹—πŸ”―) A: Jin is working on it with plans for agent marketplace, Block Tank, and retroactive funding for contributors, but no specific timeline was given (answered by jin)\nQ: What is happening with the w.ai team and ai16z? (asked by BigChungus) A: According to a shared X Spaces call, the w.ai team built and sold a launchpad to ai16z and is now working with them to launch an official platform (answered by DannyNOR NoFapArc)\nQ: Is there a PR template for plugin submissions? (asked by avirtualfuture) A: For fixes there is, but for plugins it's unclear, though all plugins have readme files (answered by DorianD)\nQ: What is the best tokenomics design according to the community? (asked by shakejr) A: Wit suggested charging fees in real money (stables/ETH), using revenue to buy back and burn native tokens, with possibly some percentage going to R&D (answered by wit)\nQ: What is the Deepseek R1 model and why is it significant? (asked by DorianD) A: Jin described it as \"a wakeup call for American open source AI\" that offers performance comparable to o1/sonnet models at 30x cheaper cost and is MIT licensed (answered by jin)\nQ: Is there a newsletter or documentation hub for ElizaOS? (asked by DorianD) A: Jin shared https://elizaos.github.io/eliza/community/ and witch mentioned https://github.com/elizaOS/awesome-eliza (answered by jin and witch)\n\n## 3. Help Interactions\n\nHelper: witch | Helpee: 보햄 | Context: 보햄 expressed concern about lack of visible progress with ai16z | Resolution: Witch shared numerous tweets showing partnerships and integrations from the past week, demonstrating significant ecosystem growth\nHelper: jin | Helpee: DorianD | Context: DorianD was looking for ElizaOS documentation | Resolution: Jin shared links to Claude.ai, code2prompt repo, and the ElizaOS GitHub repo as starting points\nHelper: jin | Helpee: avirtualfuture | Context: Discussion about aixbt spreading misinformation about Pippin vs Eliza | Resolution: Jin wrote a thread to correct the misinformation and provide accurate comparisons\nHelper: witch | Helpee: Multiple partners | Context: Partners asking about tokenomics and project progress | Resolution: Witch created and shared a one-page document summarizing ai16z, Eliza Labs, ElizaOS, and tokenomics plans\nHelper: DannyNOR NoFapArc | Helpee: Multiple partners | Context: Questions about potential w.ai partnership | Resolution: Shared detailed notes from an X Spaces call about w.ai team building and selling a launchpad to ai16z\n\n## 4. Action Items\n\nTechnical: Improve PR templates for plugin submissions to better document capabilities | Description: Create standardized documentation requirements for plugin PRs to make it easier to understand what each plugin does | Mentioned By: DorianD\nTechnical: Develop a changelog -> newsletter pipeline | Description: Automate the process of converting GitHub changelogs into newsletters for the community | Mentioned By: jin\nTechnical: Push updates for better daily/weekly tweet-sized automated updates of contributors to Eliza | Description: Improve automation of PR/communications about contributions to the project | Mentioned By: jin\nDocumentation: Create a comprehensive overview of all plugin capabilities | Description: Develop an easily scannable resource that explains what each plugin does | Mentioned By: DorianD\nDocumentation: Update tokenomics documentation | Description: Finalize and publish tokenomics plans including agent marketplace, Block Tank, and retroactive funding | Mentioned By: jin\nFeature: Develop a \"capabilities\" marketing website | Description: Create a flashy 3D website showcasing ElizaOS capabilities for marketing purposes | Mentioned By: avirtualfuture\nFeature: Build a starter project generator | Description: Create a tool where users can activate plugins by \"loading cartridges\" to generate starter projects | Mentioned By: avirtualfuture\nFeature: Implement a soulbound NFT system for partners | Description: Create a system where partners can claim a wallet as holding 100k ai16z tokens without exposing their main wallet | Mentioned By: witch\nFeature: Develop an Eliza News Channel independent of Eliza Labs | Description: Create an independent news source for Eliza ecosystem updates to separate development from marketing | Mentioned By: DorianD", "messageCount": 752, "userCount": 69 }, { "channelId": "1313222089271939102", "channelName": "3d-ai-tv", "summary": "# Discord Chat Analysis for \"3d-ai-tv\" Channel\n\n## 1. Summary\nThe chat focuses on two main projects: a news show and a \"Block Tank\" project, both being developed in Unity. The team is working on scene setup, character models, and event handling for these interactive 3D environments. For the news show, they're dealing with issues in the daily summary JSON data showing incorrect dates. The Block Tank project involves setting up a new scene with proper lighting, fixing reversed normals on models using custom shaders, and implementing character animations. There are discussions about media loading approaches, with boom suggesting downloading assets directly to textures rather than using a web browser. Character models are being refined with proper visemes (mouth shapes for speech) and rigging for animations. The team is also working on an event system to handle different actions like scene preparation and character speech. Technical challenges include fixing reversed normals on models, implementing proper lighting, and handling JSON polling that causes delays in event responses. The developers are considering the pros and cons of using Unity versus other platforms like Unreal or Blender for their video production needs.\n\n## 2. FAQ\nQ: Are the normals reversed on the Block Tank models? (asked by boom) A: Yes, SM Sith Lord suggested scaling the model by -1, but boom ended up using a custom shader to fix it.\nQ: Is the date in the daily summary JSON correct? (asked by boom) A: No, SM Sith Lord confirmed it shows the wrong date and possibly contains old information.\nQ: Do we need a web browser to load images? (asked by boom) A: No, SM Sith Lord confirmed they're just image URLs that can be loaded directly.\nQ: Has the Unity project for Block Tank been started? (asked by jin) A: boom explained they have one main scene but not a separate project yet.\nQ: Do any of the avatars in the repo have visemes? (asked by boom) A: Implied no, as boom mentioned needing to use models from the news scene that do have visemes.\n\n## 3. Help Interactions\nHelper: SM Sith Lord | Helpee: boom | Context: Fixing reversed normals on Block Tank models | Resolution: SM Sith Lord suggested scaling the model by -1, but boom ultimately created a custom shader to handle it.\nHelper: SM Sith Lord | Helpee: boom | Context: Providing reference images for the Block Tank environment | Resolution: SM Sith Lord shared pictures of the real room for lighting reference.\nHelper: jin | Helpee: boom | Context: Fixing character model issues with the new Eliza model | Resolution: jin suggested using the old model with texture swaps for the hat and shirt.\n\n## 4. Action Items\nTechnical: Fix the daily summary JSON data showing incorrect dates | Description: Current news aggregator JSON shows wrong date and possibly old information | Mentioned By: boom\nTechnical: Implement media URL loading logic for images in Unity | Description: Download assets directly to textures instead of using a web browser | Mentioned By: boom\nTechnical: Create character personalities for Degen, Eliza, and Tubbs | Description: Develop personality profiles for characters to enable animation pipeline | Mentioned By: fishai\nTechnical: Fix visemes for character models, particularly Vitalik | Description: Some models lack proper mouth shapes for speech | Mentioned By: boom\nTechnical: Implement proper event handling for TV events | Description: Consider adding a dedicated HandleTvEvent method to the event processing system | Mentioned By: boom\nTechnical: Fix eyebrow clipping issue on new Eliza model during blinking | Description: Eyebrows get clipped when the character blinks | Mentioned By: boom\nTechnical: Improve lighting on back walls of Block Tank scene | Description: Current lighting setup doesn't properly illuminate the back walls | Mentioned By: boom\nDocumentation: Document the event system architecture | Description: Create documentation for the event handling system to make it more maintainable | Mentioned By: boom\nFeature: Implement character rigging to enable leaning animations | Description: Create rig system to allow characters to lean during interactions | Mentioned By: boom", "messageCount": 86, "userCount": 4 } ] }