# elizaOS Discord - 2026-03-21 ## Summary ### Project Communication and Management The AI16Z/Eliza project faced significant community criticism regarding communication practices and project management. Team member Odilitime defended the communication strategy, noting that weekly video updates (cronjob) and daily updates are posted in a dedicated channel. However, community members expressed frustration that these updates do not address their primary concerns. The team acknowledged internal organization with developers focused on development, staff managing partners, Shaw handling Twitter, and others managing accounting and taxes. Odilitime handles community engagement during downtime due to marketing and branding background. ### Token Economics and Performance Community frustration centered on token performance and perceived mismanagement. The Babylon launch occurred but did not positively impact price. Token migration completed with 1 billion tokens minted post-migration, with community members criticizing the 40% community token allocation as a cash grab. The token initially traded upward for 3 consecutive months, which the team considered pivotal for the memecoin-as-investment narrative. However, the Trump token launch caused market-wide selloff that impacted AI16Z. The team acknowledged that token recovery is lagging behind broader market recovery, stating "something isn't right" though the cause remains unknown. Community members identified CEX listings and perpetual futures as needed for price recovery. ### Token Utility and Product Development A major point of contention was the lack of implemented token utility despite ongoing development. Community members repeatedly asked for use cases and reasons to buy the token, with no concrete answers provided. The team was compared unfavorably to Virtuals protocol regarding token utility implementation. Despite development activity, no token utility has been tied to products being built, leading to community frustration about broken promises. ### Eliza Ecosystem Architecture Technical clarification was provided regarding the Eliza ecosystem structure. ElizaOS functions as an operating system for agents, serving as the foundational layer. Milady is built on top of elizaos rather than being a replacement or competitor, leveraging elizaos as its underlying infrastructure. OpenClaw agents can exist within the milady framework, indicating these technologies are complementary rather than competing. This clarification resolved fundamental misunderstandings about the ecosystem hierarchy. ### Team Accountability and Community Relations The team acknowledged mistakes with Odilitime stating they "fucked up plenty" but maintained they have not abandoned the project. Some community critics were suspected to be "paid shills" attempting to tank the project. Community members expressed concerns about broken promises and poor communication beyond just price performance. Team members positioned themselves as having "most information about the landscape" for decision-making. ValleyBeyond shared personal experience losing money on GalaGames to emphasize personal responsibility and the principle of only investing what one can afford to lose. ## FAQ **Q: By when will team mint remaining tokens and finish selling? Will project shut down after team sells all tokens?** A: Unanswered **Q: Why isn't the token recovering at the same rate as the market?** A: Something isn't right, cause unknown (answered by Odilitime) **Q: Why is this chat full of posts saying the team is NOT communicating?** A: Team puts out weekly videos (cronjob) and daily updates in dedicated channel, but updates may not be what people are interested in (answered by Odilitime) **Q: Is there someone who coordinates information in the team or does everyone do it their own way?** A: Devs are developing, staff dealing with partners, Shaw on Twitter, others on accounting/taxes. Odilitime handles community in downtime due to marketing/branding background (answered by Odilitime) **Q: What is one use case of this token?** A: Unanswered **Q: Why should anyone buy this token?** A: Unanswered **Q: How stable is milaidy? Will it replace elizaos?** A: Milady is built on elizaos and won't replace it. ElizaOS is an operating system for agents that isn't getting replaced by anything (answered by sb) **Q: Is milady the competitor for openclaw?** A: No, it's not a competitor. OpenClaw agents can exist in milady (answered by sb) ## Help Interactions Odilitime helped Rainman understand team communication practices by pointing to weekly cronjob videos and daily updates channel, explaining that updates may not match community interests. ValleyBeyond helped gby and averma who were frustrated about losses and team accountability by sharing personal experience losing money on GalaGames and emphasizing personal responsibility and the principle of only investing what one can afford to lose. Rainman helped the community address ongoing complaints about lack of communication by suggesting replying with link to UPDATES channel whenever someone accuses team of not communicating. sb helped HatcherLabs resolve confusion about whether milady would replace elizaos by clarifying that milady is built on elizaos, which serves as the foundational operating system for agents. sb helped HatcherLabs understand the relationship between milady and openclaw by explaining that openclaw agents can exist within milady, showing they are complementary technologies. ## Action Items ### Technical Address token recovery rate lagging behind market (mentioned by Odilitime) ### Features Implement actual token utility tied to products being built (mentioned by gby) Secure good CEX listings and perpetual futures trading to improve price recovery (mentioned by ValleyBeyond) ### Documentation Better communicate existing update channels (cronjob videos, daily updates) to address perception of poor communication (mentioned by Rainman) Study and understand the Eliza ecosystem architecture and component relationships (mentioned by HatcherLabs)