# Council Briefing: 2025-06-24 ## 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 - Community trust threatened by treasury token movement concerns while technical development progresses with v2 nearing release and Spartan prototype completion. ## Key Points for Deliberation ### 1. Topic: Treasury Transparency Crisis **Summary of Topic:** Significant community concerns have arisen regarding suspected token selling from project-related wallets, with claims that 40 million $degenai tokens were transferred from the DAO treasury to a personal wallet followed by selling, causing price to reach a new all-time low. #### Deliberation Items (Questions): **Question 1:** What immediate action should be taken to address the treasury token movement concerns? **Context:** - `Community members, particularly 辞尘鸽鸽, shared on-chain evidence showing approximately 3 million $degenai tokens being sold in a single day, causing the token to reach a new all-time low.` - `Multiple users expressed frustration about the absence of official communication regarding these transactions, amplifying trust issues within the community.` **Multiple Choice Answers:** a) Issue an immediate comprehensive transparency report detailing all treasury movements with transaction hashes, wallet explanations, and future treasury management policies. *Implication:* Addresses trust issues directly but could expose sensitive operational details and create precedent for micromanagement of treasury activities. b) Implement on-chain treasury management tools with mandatory timelock and community voting for significant token movements. *Implication:* Creates structural solution but adds operational friction and doesn't immediately address current controversy. c) Maintain operational discretion while issuing statement that transactions were for strategic partnerships, explaining only after deals are finalized. *Implication:* Preserves operational flexibility but risks further deterioration of community trust if perceived as evasive. d) Other / More discussion needed / None of the above. **Question 2:** How should we balance treasury management needs with community expectations for transparency? **Context:** - `Kenk noted that the wallet in question (GypeM9BqKeKGJGTnPxTf1PdVa3UC2LkiYnvvW8CJSNj2) hasn't been confirmed as a DAO wallet, though 辞尘鸽鸽 pointed out it had previously interacted with the DAO wallet through a significant token transfer.` **Multiple Choice Answers:** a) Establish a formal Treasury Council with community representatives that has visibility into all movements but operates under NDA for sensitive operations. *Implication:* Creates structured oversight while maintaining operational security for strategic treasury activities. b) Implement complete real-time transparency with public dashboard of all treasury movements and regular community calls to explain strategic rationale. *Implication:* Maximizes transparency but potentially compromises strategic flexibility and competitive positioning. c) Develop tiered disclosure system with immediate notification for movements above certain thresholds and quarterly reports for smaller operational transactions. *Implication:* Balances transparency with operational needs but requires ongoing commitment to disclosure standards. d) Other / More discussion needed / None of the above. --- ### 2. Topic: ElizaOS v2 Launch Strategy **Summary of Topic:** With v2 already released but not officially announced and the Spartan prototype nearing completion, there's a strategic opportunity to coordinate these releases with community communications to maximize market impact and user adoption. #### Deliberation Items (Questions): **Question 1:** What launch approach would best position ElizaOS v2 for maximum community adoption and market impact? **Context:** - `Dr. Neuro mentioned that V2 is already released but not officially announced yet.` - `Void shared that the Spartan prototype is nearing completion, which could potentially bring positive market impact.` **Multiple Choice Answers:** a) Coordinate a comprehensive multi-product launch event showcasing V2 alongside Spartan prototype with developer grants program to drive immediate adoption. *Implication:* Creates marketing momentum but risks overwhelming users with too many simultaneous releases. b) Sequence product announcements with V2 announcement first, followed by Spartan prototype 2-3 weeks later to sustain momentum and allow focused adoption of each product. *Implication:* Extends visibility timeline but may dilute initial excitement by fragmenting the release cycle. c) Focus primarily on developer adoption with technical V2 documentation, hackathon, and developer incentives before wider market announcements. *Implication:* Builds stronger technical foundation but delays broader market visibility and adoption. d) Other / More discussion needed / None of the above. **Question 2:** How should we prioritize technical fixes versus shipping new features to achieve our monthly goal of attracting new auto.fun users? **Context:** - `Several users experienced problems with CLI versioning, often running 1.0.9 instead of the latest 1.0.11, with conflicts between npm and bun package managers.` - `Users reported problems with WebSocket connections and response handling after messages are sent.` **Multiple Choice Answers:** a) Establish a dedicated stability team focused exclusively on resolving critical bugs before shipping any new features for two weeks. *Implication:* Improves product stability but delays auto.fun feature enhancements that might attract new users. b) Implement feature flagging system to ship new capabilities to early adopters while maintaining stability for mainstream users during transition. *Implication:* Balances innovation and stability but increases technical complexity in managing multiple experience tracks. c) Focus primarily on auto.fun-specific features with weekly release cycles that bundle critical fixes with user-facing improvements. *Implication:* Directly supports monthly goal but risks technical debt accumulation if fundamental issues aren't systematically addressed. d) Other / More discussion needed / None of the above. --- ### 3. Topic: 24/7 Agent Showcase Strategy **Summary of Topic:** To achieve our monthly goal of attracting users to auto.fun through 24/7 agent activity, we need to address issues with social media access, improve agent reliability, and develop a cohesive strategy for showcasing agents' streaming, trading, and shitposting capabilities. #### Deliberation Items (Questions): **Question 1:** What social media integration strategy would most effectively showcase our agents' 24/7 capabilities? **Context:** - `Users noted issues accessing Shaw's Farcaster account and mentioned that Eliza's Twitter account needs restoration.` - `Rick suggested implementing 24/7 marketing through private accounts similar to Virtuals.` **Multiple Choice Answers:** a) Focus on restoring and optimizing existing Twitter/X integration first, then expand to Farcaster and other platforms as they stabilize. *Implication:* Prioritizes fixing current platform issues before expansion, potentially limiting visibility in the short term. b) Implement a multi-platform approach immediately with agents active across Twitter, Farcaster, and Discord simultaneously with cross-posting capabilities. *Implication:* Maximizes platform coverage but risks spreading technical resources thin across multiple integrations. c) Build a dedicated auto.fun agent showcase platform with embedded social feeds that can be shared anywhere, reducing dependency on third-party platforms. *Implication:* Creates controlled environment for demonstration but requires additional development resources and may have limited organic reach. d) Other / More discussion needed / None of the above. **Question 2:** How should we balance autonomous agent activities versus human-guided capabilities to showcase the most compelling aspects of our technology? **Context:** - `Sthx mentioned Twitter plugin problems which could affect agent posting capabilities.` - `Chief reported an issue with CLI reverting to local models instead of using Grok, potentially impacting agent performance and capabilities.` **Multiple Choice Answers:** a) Prioritize full autonomy with preset goals and monitoring, allowing agents to operate independently with minimal human intervention except for weekly strategy adjustments. *Implication:* Demonstrates true autonomy but increases risk of undesirable agent actions without immediate human oversight. b) Implement human-in-the-loop oversight with approval workflows for high-risk actions while allowing autonomous execution of routine activities. *Implication:* Balances safety with autonomy showcase but might diminish perception of advanced AI capabilities. c) Create staged demonstrations with progressively increasing autonomy, starting with scripted showcases and advancing to full autonomy as stability improves. *Implication:* Provides controlled rollout but may appear less impressive initially compared to competitors claiming full autonomy. d) Other / More discussion needed / None of the above.