{ "date": "2025-11-15", "meeting_context": "# North Star & Strategic Context\n\nThis 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.\n\n---\n\n**North Star:**\nTo 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.\n\n---\n\n**ElizaOS Mission Summary (`docs/blog/mission.mdx`):**\nThe 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).\n\n---\n\n**ElizaOS Reintroduction Summary (`docs/blog/reintroduction.mdx`):**\nelizaOS 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.\n\n---\n\n**Auto.fun Introduction Summary (`docs/blog/autofun-intro.mdx`):**\nAuto.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.\n\n---\n\n**Taming Information Summary (`docs/blog/taming_info.mdx`):**\nAddresses 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. ", "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": "The AI16Z to elizaOS token migration is in full swing with multi-chain deployment while technical development focuses on implementing cross-chain capabilities and enhanced framework stability for elizaOS v2.", "key_points": [ { "topic": "Token Migration & Exchange Strategy", "summary": "The migration from AI16Z to elizaOS tokens is ongoing with multi-chain availability (Solana, Ethereum, Base, BSC), but requires strategic decisions regarding exchange partnerships, particularly with Korean exchanges which community members view as crucial for price action.", "deliberation_items": [ { "question_id": "q1", "text": "How should we prioritize Korean exchange listings in our overall exchange strategy?", "context": [ "Korean community members emphasized the importance of listing on Korean exchanges, particularly Bithumb (qweqwe, Web3Go, kk)", "Team representative (jasyn_bjorn) confirmed they are in contact with Korean exchanges" ], "multiple_choice_answers": { "answer_1": { "text": "Prioritize Korean exchanges with dedicated resources and incentives for listings on Bithumb and others.", "implication": "Could accelerate price action and adoption but may divert resources from other strategic priorities." }, "answer_2": { "text": "Maintain balanced approach with equal focus on global and Korean exchanges.", "implication": "Ensures broader market coverage but may not capitalize on the enthusiasm of the Korean community." }, "answer_3": { "text": "Focus on tier-1 global exchanges first, then Korean exchanges as secondary priority.", "implication": "Maximizes global visibility first but risks losing momentum with the Korean community." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q2", "text": "What approach should we take to resolve token price visibility issues in wallets?", "context": [ "User Abdul couldn't see the price of Eliza coins in Trust Wallet", "Some users are experiencing issues with token price visibility in wallets" ], "multiple_choice_answers": { "answer_1": { "text": "Create comprehensive wallet integration guides and outreach to major wallet providers.", "implication": "Proactive approach that addresses both documentation and technical integration challenges." }, "answer_2": { "text": "Focus on establishing deeper CoinMarketCap/CoinGecko integrations first, as most wallets pull price data from these aggregators.", "implication": "Addresses the root cause but may take longer to resolve immediate user issues." }, "answer_3": { "text": "Implement a wallet-compatible price feed API as part of the elizaOS infrastructure.", "implication": "Creates a more sustainable long-term solution but requires additional development resources." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q3", "text": "What is the optimal duration for the migration window, considering the current 90-day period?", "context": [ "Migration from AI16Z to elizaOS tokens is actively ongoing through a dedicated portal", "Users report successful migrations using wallets like Phantom" ], "multiple_choice_answers": { "answer_1": { "text": "Maintain the current 90-day window to provide ample time for all users.", "implication": "Ensures accessibility but prolongs the transition period and potential market uncertainty." }, "answer_2": { "text": "Shorten the window to 60 days to accelerate the transition and focus community attention.", "implication": "Creates greater urgency but risks excluding users with legitimate migration challenges." }, "answer_3": { "text": "Keep 90-day window but add incentives for early migration within first 30 days.", "implication": "Maintains accessibility while encouraging faster adoption of the new token." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] }, { "topic": "Technical Framework Evolution", "summary": "GitHub activity shows focused efforts on enhancing elizaOS v2's core stability and cross-chain capabilities, with key developments in database plugin support, RLS security, and environment variable handling that improve the framework's reliability.", "deliberation_items": [ { "question_id": "q4", "text": "How should we balance MySQL vs. PostgreSQL support in the elizaOS framework?", "context": [ "PR #6143 titled 'fix: plugin-mysql support, initPromise and other minor fixes' is open, addressing conditional MySQL vs SQL plugin selection", "A critical issue with Row-Level Security (RLS) was resolved to prevent server_id validation from incorrectly blocking users when RLS isolation is disabled (#6139)" ], "multiple_choice_answers": { "answer_1": { "text": "Fully support both equally, ensuring feature parity between MySQL and PostgreSQL.", "implication": "Maximizes adoption potential but increases development and testing complexity." }, "answer_2": { "text": "Prioritize PostgreSQL as primary with MySQL as secondary supported database.", "implication": "Focuses resources while still supporting organizations with MySQL requirements." }, "answer_3": { "text": "Support PostgreSQL exclusively to optimize development resources and framework performance.", "implication": "Streamlines development but may limit adoption in MySQL-dependent environments." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q5", "text": "What should be our approach to integrating zero-knowledge (ZK) technology into the elizaOS framework?", "context": [ "Brief discussion about ZK (zero-knowledge) technology applications", "Suggestion that ZK could be better applied to smart contracts beyond simple cash payments" ], "multiple_choice_answers": { "answer_1": { "text": "Integrate ZK technology as a core framework feature for enhanced privacy and verification.", "implication": "Positions elizaOS as privacy-forward but requires significant core development." }, "answer_2": { "text": "Develop a plugin architecture for ZK capabilities while keeping the core framework lightweight.", "implication": "Maintains framework flexibility while enabling ZK for specific use cases." }, "answer_3": { "text": "Research ZK applications without immediate implementation until clear use cases emerge from the community.", "implication": "Preserves resources while staying informed about potential future integrations." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q6", "text": "How should we approach cross-chain functionality for the elizaOS ecosystem?", "context": [ "The elizaOS token is available on multiple chains: Solana, Ethereum, Base, and BSC", "User vloine asked how to bridge elizaOS from BSC to SOL" ], "multiple_choice_answers": { "answer_1": { "text": "Build our own cross-chain bridging infrastructure optimized for elizaOS use cases.", "implication": "Provides maximum control but requires significant development resources." }, "answer_2": { "text": "Partner with existing bridge providers like Wormhole or Chainlink CCIP for cross-chain operations.", "implication": "Accelerates deployment but creates dependency on third-party infrastructure." }, "answer_3": { "text": "Focus on Solana as primary chain with limited bridging to other chains through exchange-based solutions.", "implication": "Simplifies infrastructure but may limit cross-chain functionality and adoption." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] }, { "topic": "auto.fun Agent Activity Strategy", "summary": "While token migration and framework development are progressing, there's limited visible evidence of 24/7 agent activity on auto.fun (streaming, trading, shitposting) as outlined in the monthly goal, suggesting a potential strategic gap in user attraction initiatives.", "deliberation_items": [ { "question_id": "q7", "text": "How should we prioritize resources between technical framework development and agent activity visibility on auto.fun?", "context": [ "Monthly Goal: 'Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2'", "PR #6111 'feat: add ElizaOS reference to runtime' was merged, described as 'a step towards creating a unified messaging API'" ], "multiple_choice_answers": { "answer_1": { "text": "Shift resources toward deploying more visible AI agents on auto.fun, even if it temporarily slows framework development.", "implication": "Prioritizes immediate user engagement over long-term technical foundations." }, "answer_2": { "text": "Maintain current technical focus but add a small dedicated team for auto.fun agent activity.", "implication": "Balances priorities but may lead to slower progress in both areas." }, "answer_3": { "text": "Complete core elizaOS v2 features first, then pivot resources to auto.fun agent deployment.", "implication": "Ensures solid technical foundation but delays user growth on auto.fun." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } }, { "question_id": "q8", "text": "What type of agent activity should we prioritize on auto.fun to attract new users?", "context": [ "Monthly Goal mentions 'streaming, trading, shitposting' as agent activities", "Team is developing a rebuilt X-like platform with AI agents for prediction markets, with demo planned for upcoming Devconnect event" ], "multiple_choice_answers": { "answer_1": { "text": "Focus on trading agents with visible performance metrics and social sharing capabilities.", "implication": "Appeals to crypto users through financial utility but requires robust trading infrastructure." }, "answer_2": { "text": "Prioritize content creation and social agents (streaming, shitposting) for maximum visibility.", "implication": "Generates broader appeal but may not showcase the full technical capabilities of the framework." }, "answer_3": { "text": "Develop prediction market agents that combine financial and social elements.", "implication": "Creates a unique differentiated offering but requires more complex agent development." }, "answer_4": { "text": "Other / More discussion needed / None of the above.", "implication": null } } } ] } ] }