▶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

X (Twitter) account suspension continues to impact social presence and community engagement while development efforts on v2 show significant progress with feature migration and bugfixes.

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

X Account Suspension Strategy

The AI16Z X (Twitter) accounts have been suspended for approximately one month despite ongoing communication with X, impacting the project's ability to showcase agent activity and communicate with the community.

How should we adapt our social media strategy while our X accounts remain suspended?

Kenk confirmed they are in communication with X to resolve the issue. Communications with X have improved in recent days, but response times remain slow.
Some users suggested using alternative accounts like autofun in the meantime.

1Double down on the restoration effort by escalating to X executives and mobilizing our community support.

Could expedite account restoration but risks diverting resources from core development tasks.

2Shift focus to alternative platforms (Farcaster, Discord) and officially announce auto.fun as our primary social presence.

Maintains social momentum but potentially dilutes brand recognition tied to the main AI16Z identity.

3Launch a temporary campaign featuring AI-generated content about suspended accounts to gain viral attention.

Could generate visibility and pressure on X, but might further strain the relationship with platform moderators.

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

How critical is the X account restoration to our goal of attracting users to auto.fun?

Community members expressed frustration about the prolonged suspension compared to other projects.
The X account suspension issue coincides with reports of token performance concerns, with the AI16Z token experiencing significant volatility with a 30% drop in one day.

1Extremely critical - Twitter's crypto-native audience is essential for auto.fun growth and adoption strategy.

Would prioritize X restoration as a top-level objective, potentially allocating significant resources.

2Moderately important - A balanced approach of platform diversification while continuing X restoration is optimal.

Would maintain current efforts while building presence on other platforms for redundancy.

3Minimally important - The suspension has created an opportunity to innovate our distribution strategy beyond X.

Would redirect social media resources to emerging platforms that may better align with our decentralized principles.

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

ElizaOS v2 Development Progress

Substantial progress has been made on ElizaOS v2 development, with comprehensive refactoring of prompts to XML format, critical security hardening, and resolution of key bugs, while numerous community-requested features are being implemented.

What should be our approach to addressing community concerns about on-chain storage for character files and memories?

DorianD criticized that ElizaOS doesn't store character files and memories on-chain. He described it as a "wrapper for black box LLMs" rather than a true decentralized protocol.
Kenk defended the approach, arguing that blockchain should be used purposefully. The team is focusing on agent-led services, money markets, and micropayments as the path to fee capture.

1Maintain current approach with clear communication on why we're focusing on agent-led services rather than on-chain storage.

Preserves development velocity but may not address decentralization concerns from some community members.

2Develop an optional on-chain storage module for users who prioritize decentralization over performance.

Addresses community concerns while maintaining flexibility, but increases complexity and maintenance burden.

3Pivot to make on-chain storage a core feature of v2, emphasizing our commitment to decentralization principles.

Aligns with crypto-native user expectations but may significantly impact performance and development timeline.

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

Should we prioritize action chaining and image generation capabilities in the v2 release to showcase advanced agent capabilities?

A key new capability for action chaining was implemented, allowing for more complex, sequential agent behaviors.
This PR adds a new generateImageAction to the agent pipeline, enabling the agent to generate images based on conversational context using ModelType.IMAGE.

1Yes, prioritize these visually impressive features to drive user engagement and adoption.

Could accelerate user growth but may delay stability improvements needed for core functionality.

2Include them in v2 but focus marketing on stability and reliability improvements rather than new capabilities.

Balances feature richness with stability messaging, potentially building more sustainable user trust.

3Hold these features for a v2.1 release to ensure v2 core is rock-solid before adding complexity.

May extend timeline for showcasing advanced capabilities but would ensure a more reliable initial v2 experience.

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

How should we approach Windows compatibility issues that continue to be a source of user friction?

Windows compatibility problems with the knowledge plugin were identified and fixed.
Despite some fixes, Windows remains a source of user-reported issues, including failures to load specific plugins like `plugin-local-ai` and errors during agent creation related to directory paths.

1Dedicate a specialized team to systematically address all Windows compatibility issues before v2 release.

Could delay release timeline but would expand the potential user base and improve overall quality.

2Implement feature flags to gracefully degrade functionality on Windows until compatibility issues are resolved.

Maintains release schedule while providing transparent expectations for Windows users.

3Officially recommend WSL/Docker as the preferred Windows deployment solution in our documentation.

Simplifies development by standardizing on Unix-like environments but may increase initial setup complexity for some users.

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

Token Utility and Value Capture

Community members have expressed significant concerns about token utility, slow implementation of tokenomics, and unclear path to value capture, which may be contributing to token volatility.

What immediate steps can we take to address community concerns about tokenomics and value capture?

Community members expressed frustration about: Lack of token utility, slow implementation of tokenomics, unclear path to value capture.
Dr. Neuro explained that the token enables an agent-to-agent marketplace with AI16Z as the settlement layer.

1Accelerate tokenomics implementation with a clear roadmap for how AI16Z will capture value in the agent ecosystem.

Could restore confidence but risks implementing untested economic models under time pressure.

2Publish a detailed tokenomics white paper while continuing careful implementation to ensure long-term sustainability.

Provides transparency while maintaining development quality but may not satisfy those seeking immediate utility.

3Launch a token utility beta program focused on agent-to-agent marketplace settlement to demonstrate value capture mechanisms.

Shows concrete progress through working code rather than just documentation, but introduces new development priorities.

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

Should we prioritize staking mechanisms to address token utility concerns in the short term?

Questions about potential token staking system were raised.
Dr. Neuro explained: Not yet, more will be clear once tokenomics are released.

1Yes, implement a basic staking mechanism that provides governance rights as an immediate utility.

Provides a quick win for token utility but may set precedents that constrain future tokenomics design.

2No, focus on use-case driven token utility tied to the agent marketplace rather than financial engineering.

Maintains focus on sustainable value creation but delays addressing immediate community concerns.

3Implement a phased approach with a simple staking mechanism now, evolving to more sophisticated utility over time.

Balances immediate needs with long-term vision, but increases complexity of tokenomics implementation.

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

Council Briefing

North Star & Strategic Context

Key Deliberations