Council Briefing

Strategic Deliberation
▶North Star & Strategic Context

North Star & Strategic Context



This file combines the overall project mission (North Star) and summaries of key strategic documents for use in AI prompts, particularly for the AI Agent Council context generation.

---

North Star: To build a truly autonomous, sustainable DAO that develops open-source software accelerating the path toward AGI, blending AI researchers, open-source hackers, and crypto degens to create AI agents streaming, shitposting, and trading 24/7 on auto.fun to attract users and bootstrap an autonomous organization.

---

ElizaOS Mission Summary (`docs/blog/mission.mdx`): The elizaOS mission is to build an extensible, modular, open-source AI agent framework for Web2/Web3, seeing agents as steps toward AGI. Core values are Autonomy, Modularity, and Decentralization. Key products include the framework itself, DegenSpartanAI (trading agent), Autonomous Investor/Trust Marketplace (social trading intelligence), and the Agent Marketplace/auto.fun (launchpad).

---

ElizaOS Reintroduction Summary (`docs/blog/reintroduction.mdx`): elizaOS is an open-source "operating system for AI agents" aimed at decentralizing AI development away from corporate control. It's built on three pillars: 1) The Eliza Framework (TypeScript toolkit for persistent, interoperable agents), 2) AI-Enhanced Governance (building autonomous DAOs), and 3) Eliza Labs (R&D for future capabilities like v2, Trust Marketplace, auto.fun, DegenSpartanAI, Eliza Studios). The native Solana token coordinates the ecosystem and captures value. The vision is an intelligent internet built on open protocols and collaboration.

---

Auto.fun Introduction Summary (`docs/blog/autofun-intro.mdx`): Auto.fun is an AI-native, creator-first token launchpad designed for sustainable AI/crypto projects. It aims to balance fair community access with project funding needs through mechanisms like bonding curves and liquidity NFTs. Key features include a no-code agent builder, AI-generated marketing tools, and integration with the elizaOS ecosystem. It serves as a core product driving value back to the native token ($ai16z) through buybacks and liquidity pairing.

---

Taming Information Summary (`docs/blog/taming_info.mdx`): Addresses the challenge of information scattered across platforms (Discord, GitHub, X). Proposes using AI agents as "bridges" to collect, wrangle (summarize/tag), and distribute information in various formats (JSON, MD, RSS, dashboards, 3D shows). Showcases an AI News system and AI Assistants for tech support as examples. Emphasizes treating documentation as a first-class citizen to empower AI assistants and streamline community operations.
▶Daily Strategic Focus
Token migration process shows progress but remains a critical bottleneck for community momentum and product development timelines.
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.

Key Deliberations

Token Migration Execution
The migration from AI16Z to ElizaOS tokens continues to progress with major exchanges expected to complete the process this week, but uncertainty and communication gaps are causing community frustration and potential trust issues.
Q1
How should we improve the migration communication strategy to maintain community trust during the final phases?
  • Community members expressed concern about the migration process on various exchanges, particularly Gate.io, where withdrawals are paused but the swap hasn't completed yet.
  • Team member Borko confirmed that Gate.io should complete the migration "this week" as they've received all necessary information.
1Create daily migration status updates with specific exchange timelines and technical progress.
Increases operational transparency but requires dedicated resources and risks exposing the team to criticism if timelines slip.
2Develop comprehensive migration documentation and educational content while maintaining the current ad-hoc updates.
Balances providing detailed information with operational flexibility but may not address immediate anxiety.
3Focus on incentivizing self-migration with token airdrops or promotions rather than waiting for exchanges.
Could accelerate migration completion but potentially increases token inflation and privileges technically-savvy users.
4Other / More discussion needed / None of the above.
Q2
How should we address community concerns about the increased token supply (from 1B to 11B) and its impact on token value?
  • There are questions about the new tokenomics, with concerns about the increased supply (from 1B to 11B). Team members clarify that only 13% is initially added to circulation, with team tokens locked for one year and the rest reserved for community growth.
  • Some community members express concern about the declining price despite the broader market uptrend, while others remain optimistic about the project's long-term potential, pointing to active GitHub development.
1Launch a tokenomics transparency dashboard showing real-time circulation, lock-ups, and utility metrics.
Builds trust through radical transparency but requires significant technical resources to implement.
2Implement a token burning mechanism tied to auto.fun platform usage to counter inflationary concerns.
Creates a deflationary narrative but may limit future treasury flexibility and require complex economic modeling.
3Focus messaging on token utility within the ecosystem rather than supply, emphasizing upcoming use cases in ElizaCloud and Babylon.
Redirects the narrative toward long-term value creation but doesn't directly address immediate price concerns.
4Other / More discussion needed / None of the above.
Q3
What is the best strategy to leverage the token migration process to bootstrap auto.fun activity?
  • DorianD suggested implementing competitions for ElizaCloud with rewards for agents generating highest payments or reputation scores.
  • DorianD also proposed implementing token snapshot and airdrop mechanisms to create incentives for users to migrate tokens.
1Implement post-migration bonuses that reward early adopters with special auto.fun agent capabilities or features.
Creates immediate incentives for migration but risks devaluing these exclusive capabilities over time.
2Launch an agent competition program with token rewards tied directly to migration completion.
Drives both migration and platform engagement but may attract primarily mercenary capital rather than long-term users.
3Create a tiered migration program where early migrators gain progressively better positions in auto.fun governance.
Builds long-term alignment between early adopters and platform governance but may create an entrenched power structure.
4Other / More discussion needed / None of the above.
Product Development Roadmap
Multiple key products (ElizaCloud, Babylon, OTC agent, and an agent game for Devconnect) are progressing but require clearer prioritization against the backdrop of the token migration and v2 shipping goals.
Q4
Which product should be prioritized for immediate completion to best advance our monthly goal of attracting new users to auto.fun?
  • ElizaCloud Timeline: Borko confirmed release by year-end
  • Babylon Release: Coming "much sooner" than ElizaCloud
  • Agent Game: Team focused on developing an "agent game" for upcoming Devconnect event
1Fast-track the agent game for Devconnect to showcase 24/7 agent activity to a high-value audience.
Capitalizes on a specific event for exposure but may divert resources from more sustainable platform development.
2Prioritize Babylon release as it appears closest to completion and can demonstrate agent trading functionality.
Delivers a concrete product sooner but may not fully showcase the breadth of agent capabilities beyond trading.
3Accelerate a minimum viable version of ElizaCloud to establish infrastructure for all subsequent agent activities.
Builds foundational infrastructure but delays visible user-facing features that could drive immediate adoption.
4Other / More discussion needed / None of the above.
Q5
How should we integrate the youth entrepreneurship initiative into our product roadmap?
  • Youth Entrepreneurship: Discussion about creating opportunities for young entrepreneurs to generate income through AI agents by summer 2026
1Create a dedicated GenZ-focused incubator track within auto.fun with simplified onboarding and specialized mentorship.
Appeals to a specific demographic but requires significant educational resources and may dilute the core technical focus.
2Incorporate youth-focused templates and use cases into the main auto.fun platform without a separate initiative.
Maintains product cohesion but may not sufficiently address the specific needs and barriers for younger entrepreneurs.
3Defer the youth entrepreneurship initiative until after v2 is stable and focus exclusively on technical users first.
Maintains focus on core technical development but risks missing early adoption from a potentially valuable demographic.
4Other / More discussion needed / None of the above.
Technical Stability and Performance
Recent GitHub activity shows progress in addressing core stability issues including bug fixes for entity name serialization and agent settings persistence, while new features for enhanced security and dynamic prompts are in development.
Q6
How should we balance shipping production-ready elizaOS v2 against implementing new features like entity-level row security and dynamic prompts?
  • Pull request #6107 by @standujar titled 'feat: implement entity-level row level security' is in progress.
  • Pull request #6113 by @odilitime titled 'feat: Framework for adjusting prompts to best fix model contexts' is in progress.
  • 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.'
1Freeze feature development and focus exclusively on stability, testing, and documentation for v2 release.
Ensures a more stable v2 release but delays potentially valuable features and may demotivate innovation-focused developers.
2Implement a feature flagging system that allows new capabilities to be developed but disabled by default in production.
Balances innovation and stability but increases technical complexity and potential for regressions.
3Prioritize only features that directly enable 24/7 agent activity on auto.fun, deferring others until after v2 release.
Aligns directly with monthly goals but may result in technical debt if foundational improvements are postponed.
4Other / More discussion needed / None of the above.
Q7
What approach should we take to resolve the technical issues with the Next.js application and database requirements for the OTC agent?
  • The team is working with Vercel for hosting a Next.js application, with cjft noting build errors preventing deployment.
  • R0am requested a PostgreSQL database (either Supabase or Neon) with connection string for their deployment needs.
1Create standardized infrastructure templates and managed services for all elizaOS products and agents.
Reduces infrastructure overhead for developers but requires upfront investment and ongoing maintenance.
2Establish a dedicated DevOps team to support individual product teams with their deployment and database needs.
Provides specialized support but creates potential bottlenecks and additional organizational complexity.
3Focus on documentation and self-service tools while maintaining the current ad-hoc infrastructure support model.
Empowers teams to solve their own issues but may lead to inconsistent implementations and repeated work.
4Other / More discussion needed / None of the above.