# Council Briefing: 2025-10-13 ## Monthly Goal Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2. ## Daily Focus - Amid significant market downturn and the looming token migration, the core team has maintained focus on technical advancement with successful deployment system overhaul and agent identification improvements. ## Key Points for Deliberation ### 1. Topic: Token Migration Strategy **Summary of Topic:** The upcoming migration from AI16Z to ElizaOS token on October 21st involves a 1:10 redenomination with 60% to holders and 40% to treasury, causing approximately 25% initial dilution for current holders while providing funds for partnerships and operational reserves. #### Deliberation Items (Questions): **Question 1:** Given the current market downturn and extreme volatility, should we consider postponing the token migration scheduled for October 21st? **Context:** - `Significant market downturn affecting cryptocurrency prices, including ElizaOS` - `Reports of a major liquidation event described as 'largest liquidation event in crypto history'` - `AI16Z reportedly dipped to as low as 1 cent on some exchanges` - `Migration from AI16Z to ElizaOS token will begin on October 21st` **Multiple Choice Answers:** a) Proceed with migration as scheduled on October 21st. *Implication:* Demonstrates commitment to roadmap but risks lower participation during market uncertainty and potential price pressure. b) Postpone migration until market conditions stabilize, focusing on technical advancements in the meantime. *Implication:* Avoids compounding market volatility effects but delays treasury funding needed for partnerships and development acceleration. c) Maintain October 21st start date but extend the migration window from the standard period to 60 days. *Implication:* Balances commitment to roadmap with flexibility for users during volatile market conditions. d) Other / More discussion needed / None of the above. **Question 2:** How should we address community concerns about the 25% dilution resulting from the migration design? **Context:** - `1:10 redenomination with 6 tokens going to holders and 4 to treasury` - `Approximately 25% initial dilution for current holders` - `15% SAFT allocation being used to secure partnerships with most tokens locked for 3 years` - `Some users noting lack of fundamental value drivers for the token currently` **Multiple Choice Answers:** a) Emphasize the long-term value creation from partnerships and agent-operated products enabled by treasury funding. *Implication:* Focuses on future benefits but may not address immediate dilution concerns effectively. b) Implement a partial token burn mechanism from treasury allocation to offset dilution effects over time. *Implication:* Directly addresses dilution concerns but reduces funding available for partnerships and development. c) Launch specific agent-operated products and utilities immediately alongside migration to demonstrate immediate token value. *Implication:* Creates tangible utility but risks rushing product development to match migration timeline. d) Other / More discussion needed / None of the above. **Question 3:** What is the most effective way to communicate token utility to increase adoption following the migration? **Context:** - `Token will operate cross-chain with CCIP, manage treasury with agent-governed liquidity system, and introduce agent-operated products with OTC Bond Desk being the first one. (Kenk)` - `Because there's no real need or must-have reason to buy it at the moment. (DorianD)` - `Agent-governed liquidity systems for treasury management` - `Agent-operated products with OTC Bond Desk as first offering` **Multiple Choice Answers:** a) Focus messaging on technical capabilities like cross-chain operations and CCIP integration. *Implication:* Appeals to technical users but may not resonate with broader market seeking clear utility narratives. b) Emphasize agent-operated products, particularly the OTC Bond Desk, as unique differentiators that create recurring token demand. *Implication:* Provides concrete utility examples but depends on timely product delivery to maintain credibility. c) Highlight governance utility and treasury management as primary value drivers, focusing on long-term protocol ownership benefits. *Implication:* Aligns with DAO vision but may not provide sufficient short-term incentives for new token adopters. d) Other / More discussion needed / None of the above. --- ### 2. Topic: Technical Architecture Strategy **Summary of Topic:** The team has made crucial architectural decisions including selecting Capacitor.js for mobile development, implementing a single database with row-level security for agent data, migrating deployment to a bootstrapper system, and transitioning authentication from WorkOS to Privy. #### Deliberation Items (Questions): **Question 1:** How should we prioritize resources between technical infrastructure improvements and user-facing features to best support our monthly goal? **Context:** - `Planning for 100K users, 500K agents, and 5M messages per month` - `Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2` - `PR #6058 titled 'elizaos deploy r2 artifacts style' significantly improved deployment speed and reduced resource usage` **Multiple Choice Answers:** a) Prioritize infrastructure scaling and stability to ensure seamless experience for current and new users as we grow. *Implication:* Creates robust foundation but delays new features that could attract users to auto.fun. b) Focus primarily on user-facing agent features (streaming, trading, shitposting) with minimal infrastructure work to maximize immediate user attraction. *Implication:* Accelerates user acquisition but risks technical debt and potential scalability issues. c) Balance resources with 60% to infrastructure and 40% to user-facing features, ensuring both progress simultaneously. *Implication:* Advances both areas but may slow progress in each compared to a more focused approach. d) Other / More discussion needed / None of the above. **Question 2:** Which social agent development partnership should receive priority resource allocation to best showcase 24/7 agent activity? **Context:** - `Social Agent Development: Partnerships with Hyperfy to build an 'AI RuneScape' and work with Ethereum Foundation on an agent game using ERC-8004 spec` - `Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2` **Multiple Choice Answers:** a) Prioritize the Ethereum Foundation partnership around ERC-8004 to strengthen positioning in the Ethereum ecosystem. *Implication:* Builds credibility with developers but may have slower path to mainstream user attraction. b) Focus resources on the Hyperfy 'AI RuneScape' partnership to create an engaging, accessible demonstration of persistent agent activity. *Implication:* Creates compelling user-friendly showcase but may not advance technical standards and integration as effectively. c) Develop an auto.fun-specific social agent system independent of these partnerships to maintain full control over user experience. *Implication:* Ensures direct alignment with auto.fun goals but forgoes partner resources and ecosystem benefits. d) Other / More discussion needed / None of the above. **Question 3:** What deployment and hosting strategy should we adopt given the new bootstrapper architecture to optimize for both developer experience and operational costs? **Context:** - `PR #6058 completely migrates the ElizaOS CLI deployment system from traditional Docker image builds to a modern bootstrapper architecture` - `Creates lightweight tar.gz artifacts (typically <50MB vs 500MB+ Docker images)` - `Serverless vs Container Architecture... clarified that they offer two experiences - serverless for regular users and containers for custom code deployment` - `Vercel's serverless architecture benefits including global distribution and built-in caching` **Multiple Choice Answers:** a) Standardize on serverless deployment for all users, optimizing for simplicity and minimizing infrastructure management overhead. *Implication:* Maximizes ease of use but limits flexibility for advanced agent developers requiring custom runtime environments. b) Maintain dual deployment paths (serverless and containerized) with clear documentation on optimal use cases for each approach. *Implication:* Provides flexibility for different developer needs but increases maintenance and support requirements. c) Transition primarily to containerized deployment using the new bootstrapper system while deprecating serverless options. *Implication:* Creates a more consistent deployment model but increases complexity for casual developers. d) Other / More discussion needed / None of the above. --- ### 3. Topic: Platform Expansion and Resilience **Summary of Topic:** Recent discussions have highlighted the need to expand beyond reliance on specific platforms like X/Twitter and consider multi-platform presence to avoid platform-specific shutdowns, while also exploring decentralized alternatives for long-term resilience. #### Deliberation Items (Questions): **Question 1:** How should we balance platform diversification against focused execution given our current resources? **Context:** - `Consider multi-platform presence for AI Agent beyond X to avoid platform-specific bans (admin123456)` - `I wonder if X account recovery is not on our side anymore? (asked by Void)` - `Brief discussion about using an AI avatar (Eliza) for video/audio interactions, conceptualized as a browser extension` **Multiple Choice Answers:** a) Maintain primary focus on X/Twitter while developing a strategic roadmap for gradual platform expansion. *Implication:* Preserves execution focus but maintains platform dependency risks in the near term. b) Immediately diversify to 2-3 additional high-impact platforms (Discord, Telegram, Farcaster) with simplified agent implementations. *Implication:* Reduces platform risk but divides development resources across multiple integration efforts. c) Build a platform-agnostic agent framework layer that abstracts away platform-specific details, enabling easier future expansion. *Implication:* Increases initial development time but creates long-term technical foundation for efficient multi-platform support. d) Other / More discussion needed / None of the above. **Question 2:** What approach should we take regarding the AI avatar concept for richer agent interactions? **Context:** - `Brief discussion about using an AI avatar (Eliza) for video/audio interactions, conceptualized as a browser extension` - `Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2` **Multiple Choice Answers:** a) Prioritize development of an Eliza avatar browser extension as a high-impact differentiator for agent interactions. *Implication:* Creates novel interaction capability but diverts resources from core platform stabilization. b) Explore avatar concept through a limited prototype but defer significant development until after elizaOS v2 ships. *Implication:* Balances innovation exploration with focus on core deliverables. c) Partner with existing avatar/identity projects rather than building custom solution to accelerate time-to-market. *Implication:* Leverages external expertise but creates dependency on partner roadmaps and capabilities. d) Other / More discussion needed / None of the above. **Question 3:** How should we approach the relationship between auto.fun and social agent development to create the most compelling 24/7 agent showcase? **Context:** - `Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2` - `Members shared and discussed AI-generated Sora videos, with some users exchanging prompt engineering techniques` - `Sora Prompt Engineering: Several members shared techniques and examples for creating effective prompts for Sora video generation` **Multiple Choice Answers:** a) Focus on integrating Sora-like video generation capabilities into auto.fun agents to create rich visual content streams. *Implication:* Creates high-engagement visual content but requires significant technical investment in advanced AI integration. b) Prioritize agent conversational capabilities and inter-agent interactions to demonstrate emergent social behaviors on auto.fun. *Implication:* Highlights agent autonomy and intelligence but may be less visually compelling than rich media approaches. c) Develop template-based content generation systems focused on trading insights, market analysis, and financial memes. *Implication:* Aligns with DeFi/trading audience expectations but narrows the content appeal to financially-focused users. d) Other / More discussion needed / None of the above.