# elizaOS Discord - 2025-06-20

## Overall Discussion Highlights

### X (Twitter) Account Issues
- **Account Suspension**: Shaw confirmed their X account was suspended, likely due to concerns about data scraping
- **Resolution Status**: They've submitted clarification that they don't scrape or sell X data and are awaiting account restoration
- **API Challenges**: Discussion about X's new API pricing ($50k/month) making it prohibitively expensive for many AI agent developers
- **Alternative Solutions**: Community member z1 claimed to have developed a scraper that bypasses the official API but warned about potential detection

### ElizaOS V2 Development
- **Release Status**: Shaw confirmed V2 is complete and ready to be announced once their X accounts are restored
- **Upcoming Features**: Shaw hinted at "big breakthroughs in capability" coming soon
- **Alternative Platforms**: Mentioned building a presence on Farcaster as an alternative to X

### Technical Discussions
- **Decentralized Network Concept**: DorianD proposed a system where numerous Eliza Nodes could scrape X and store data in encrypted vaults with vectorization to avoid legal issues
- **Architecture Considerations**: Discussion about keeping agents lean by separating backend processing for complex multi-step processes
- **Plugin Issues**: Users reporting problems with the Twitter plugin not functioning despite proper API credentials

### Governance Discussions
- **Jupiter DAO Issues**: Detailed explanation of recent controversies involving token allocation proposals, voting mechanisms, and community trust issues
- **Governance Models**: Brief discussion comparing Bitcoin's mining-based approach to consensus versus traditional voting systems

## Key Questions & Answers

**Q: When will version 2 be released?** (asked by ghk9698)  
A: "V2 is done and shipped and we'll announce it when we get the accounts back" (answered by shaw)

**Q: When will X account be back?** (asked by ghk9698)  
A: Shaw thinks it will return after they filled out a questionnaire clarifying they don't scrape or sell X data (answered by Odilitime and shaw)

**Q: What happened to agent-twitter-client repo?** (asked by SajidBanday)  
A: It's been taken offline, guessing X asked them to remove it (answered by Odilitime)

**Q: I want to build an agent that's aware of market prices and can post crypto insights. Could you tell me what tools I should use or where to start?** (asked by Jon)  
A: "With regards to where to start, the quickstart in eliza.how is a good 0-1 starting point. We are currently on 1.0.9 within the framework and some of the plugins have not yet been migrated but within the plugin directory you will see availability of market data like pyth, coinmarket cap, coingeko." (answered by Kenk)

**Q: Does anybody have insight to what is going on within Jup DAO?** (asked by Kenk)  
A: "It started when lot of people unstaked and sold after Meow put a proposal where you could vote to fund talent acquisition..." (answered by Toni with a detailed explanation of the controversy)

## Community Help & Collaboration

### Installation Support
- **Helper**: cjft  
- **Context**: Shared installation command "npm i -g @elizaos/cli && elizaos create" with link to v1.0.10 release to help users get started with ElizaOS

### Crypto Agent Development Guidance
- **Helper**: Kenk  
- **Helpee**: Jon  
- **Context**: User needed guidance on building a crypto market insights agent  
- **Resolution**: Provided links to quickstart documentation and suggested relevant plugins (pyth, coinmarketcap, coingecko)

### Technical Troubleshooting
- **Helper**: sayonara and 0xbbjoker  
- **Helpee**: Devansh  
- **Context**: User experiencing "Text is not JSON" error and module import issues  
- **Resolution**: Suggested using latest ElizaOS version (v1.0.11) and alternative installation methods using Bun, requested environment information to diagnose the problem

### X Account Suspension Concerns
- **Helper**: shaw  
- **Helpee**: phetrusrodrigues and community  
- **Context**: Concerns about X account suspension and FUD  
- **Resolution**: Explained they're working on it and have submitted required information to X

### Jupiter DAO Explanation
- **Helper**: Toni  
- **Helpee**: Kenk  
- **Context**: Kenk asked about Jupiter DAO governance issues  
- **Resolution**: Toni provided a detailed explanation of the controversy surrounding Meow's proposals, token allocations, and community trust breakdown

## Action Items

### Technical
- Develop decentralized network for X data scraping with encrypted vaults and vectorization (Mentioned by DorianD)
- Complete benchmarks for new capability breakthroughs (Mentioned by shaw)
- Investigate and fix the pg module import issue in ElizaOS CLI - Error with named export 'Pool' from pg module causing installation failures (Mentioned by Devansh)
- Resolve JSON parsing error in ElizaOS core - "Text is not JSON" error when processing certain inputs (Mentioned by Devansh)
- Investigate issues with plugin-twitter functionality - Plugin reportedly "does nothing" despite proper API credentials (Mentioned by lord_dubious)
- Consider architecture for separating backend processing from agents - Allow agents to stay lean while handling complex multi-step processes separately (Mentioned by orayo)

### Feature
- Build presence on Farcaster as alternative platform (Mentioned by shaw)

### Documentation
- Create guide for agent creation (requested indirectly) (Mentioned by digitalalchemy)
- Update documentation for latest ElizaOS setup process - Current docs may be missing steps like adding bootstrap plugin (Mentioned by Devansh)