▶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 challenges and price volatility are undermining community confidence during a critical adoption period for auto.fun, requiring immediate strategic response.

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 & Market Confidence

The recent token migration (AI16Z to elizaOS) has faced technical difficulties and coincided with a significant market cap decline from $2.5B to ~$30-50M following the Binance Alpha airdrop, creating both technical and trust challenges.

What immediate action should be prioritized to stabilize the token situation?

Users reported difficulties with the ElizaOS token migration from AI16Z, particularly those who moved tokens to new wallets after the November 11th snapshot
Significant price drop (30-50%) following Binance Alpha airdrop announcement

1Optimize migration process with automated solutions for edge cases (post-snapshot transfers, exchange holdings).

Technical focus addresses immediate user frustration but doesn't directly address price decline or perception issues.

2Deploy emergency liquidity across all chains, focusing on Solana ecosystem for auto.fun integration.

Addresses price stability but requires significant capital deployment during uncertain market conditions.

3Release comprehensive tokenomics clarification emphasizing utility implementation timeline and transparent governance structures.

Rebuilds long-term confidence but may not provide immediate price relief or resolve technical migration issues.

4Other / More discussion needed / None of the above.

How should we respond to the market cap decline to maintain alignment with our monthly goal of attracting new users to auto.fun?

Token market cap reportedly fell to $30-50M from previous highs of $2.5B
Poor liquidity across chains, with BSC having better liquidity than Solana/Base/ETH

1Accelerate auto.fun agent demonstrations with high-profile trading, content creation, and social activity to showcase real utility.

Shifts narrative from token price to product value, though benefits may lag behind immediate market concerns.

2Implement token utility features ahead of schedule, particularly staking for governance and fee reduction on auto.fun.

Creates demand-driven price support but risks shipping incomplete features under pressure.

3Pause new initiatives temporarily to conduct a token buyback program across all chains, with priority on Solana ecosystem.

Provides immediate market support but diverts resources from product development and may create unsustainable price expectations.

4Other / More discussion needed / None of the above.

ElizaOS v2 Technical Readiness

Recent GitHub activity shows focused work on core stability and configuration, with notable progress on entity-level security and runtime enhancements that are foundational for the production-ready elizaOS v2.

Based on recent technical progress, what remaining priority should be addressed to declare elizaOS v2 production-ready?

A critical bug was fixed where environment variables were not being loaded correctly, preventing agents from accessing settings.
Work started on adding an ElizaOS reference directly to the runtime, likely to streamline framework interactions.

1Focus on the entity isolation functionality for websocket and API that Stan is close to completing.

Prioritizes security and multi-tenancy capabilities, enabling enterprise adoption but potentially delaying other features.

2Expedite MySQL plugin support and initPromise implementation from PR #6143 for broader database compatibility.

Expands deployment options and stability, attracting developers from diverse technical backgrounds but with limited direct user impact.

3Complete the unified messaging API referenced in PR #6111 to enable more sophisticated agent interactions.

Enhances the quality and complexity of agent behaviors on auto.fun, directly supporting the monthly goal but potentially at the expense of stability.

4Other / More discussion needed / None of the above.

What development approach should be taken for the points/leaderboard and parallel actions features mentioned in recent issues?

New issues were created for "Entity-level RLS" (#6112), which complements the ongoing PR, and a "Points / Leaderboard" system (#6110) to enhance user interaction.
Discussions were initiated around implementing "Parallel actions" (#6108) and "Background tasks" (#6109), indicating a focus on scaling the system's operational capacity.

1Prioritize points/leaderboard as an immediate auto.fun integration to boost user engagement with 24/7 agent activities.

Directly supports the monthly goal of attracting users but delays performance improvements for complex agent operations.

2Focus on parallel actions and background tasks to enable more sophisticated agent behaviors for trading and content creation.

Improves the quality and capabilities of showcase agents but provides less immediate user-facing value.

3Develop both tracks simultaneously with distinct teams, using auto.fun as the testing ground for integration.

Maintains balanced progress but divides development resources and introduces coordination complexity.

4Other / More discussion needed / None of the above.

Agent-Based Engagement Mechanisms

Proposals for novel agent-based interaction models, including gaming and gambling elements with token incentives, present opportunities to create unique engagement loops for auto.fun that align with our goal of showcasing 24/7 agent activity.

How should we prioritize the proposed interactive agent games with token rewards in relation to our current goals?

DorianD proposes creating a gambling agent using ElizaOS tokens with zero-knowledge proofs to verify game outcomes
DorianD suggests interactive games where users pay to interact with Eliza agents, potentially earning trophy tokens and NFTs

1Implement as a core feature of auto.fun, integrating with token utility to drive engagement and token velocity.

Aligns perfectly with goal of showcasing 24/7 agent activity but introduces regulatory and technical complexity.

2Develop as an experimental showcase separate from main token utility, using minimal amounts to demonstrate technology.

Reduces regulatory risk and technical complexity while still demonstrating novel agent capabilities.

3Defer implementation until after elizaOS v2 is stable, focusing instead on non-monetary agent engagement models.

Prioritizes core stability and reduces complexity but misses an opportunity for differentiated engagement.

4Other / More discussion needed / None of the above.

What technological foundation should be prioritized to enable the proposed agent-user interaction models?

DorianD questions whether the upcoming ElizaCloud platform would support functionality for agent-based transactions and blockchain interactions
Proposal for creating a gambling agent using ElizaOS tokens with zero-knowledge proofs (ZK) to verify game outcomes

1Focus on enabling blockchain transaction capabilities for ElizaCloud agents as a core platform feature.

Creates a foundation for all token-based agent interactions but requires significant infrastructure development.

2Prioritize integration with zero-knowledge technology for verifiable agent behaviors and outcomes.

Enables trust-minimized interactions particularly suitable for games and betting but has steeper technical requirements.

3Develop a trophy/achievement framework first, then add token capabilities as an extension.

Provides immediate non-monetary engagement while building toward token integration with less regulatory concern.

4Other / More discussion needed / None of the above.

Council Briefing

North Star & Strategic Context

Key Deliberations