# elizaOS Development Discord - 2025-05-03

## Overall Discussion Highlights

### Development Branches & Version Management
- Discussion about the differences between ElizaOS version 1.0.0.Beta 41 (current stable release) and V2 (development branch)
- V2 branch includes new features like improved plugin architecture, enhanced character system, and better multimodal support
- Timeline for V2 stable release is estimated at "a few months" according to Ruby
- Clarification that "v2-develop" is the recommended branch for plugin development

### CLI Installation Issues
- Multiple users experienced difficulties updating the ElizaOS CLI from beta.38 to beta.41
- Various installation methods were attempted (npm, GitHub, local build) with mixed results
- Persistent version conflicts observed where the system reports an older version despite successful installation of newer version

### Feature Requests
- Request for cryptocurrency-related functionality including:
  - Token price/data retrieval
  - Token swapping and transfers with status updates
  - Token deployment capabilities
  - Wallet connection integration

## Key Questions & Answers

**Q: What is the difference between ElizaOS version 1.0.0.Beta 41 and V2?**  
A: V2 is the development branch which will eventually become 2.0, while beta.41 is the current stable release. V2 has a new plugin architecture, improved character system, and better multimodal support. (answered by Ruby)

**Q: When will V2 be available?**  
A: V2's timeline is still fluid, but we're looking at a few months for stable release. (answered by Ruby)

**Q: Which codebase should I use to develop a simple text chat plugin?**  
A: Use the v2-develop branch. (answered by shaw)

**Q: How can I update the ElizaOS CLI from beta.38 to beta.41?**  
A: Try running 'npm i -g @elizaos/cli@beta' to install the latest beta version directly. (answered by sayonara)

## Community Help & Collaboration

1. **CLI Update Troubleshooting**
   - Helper: Ruby & sayonara
   - Helpee: kandizzy
   - Context: CLI update failing with 404 error
   - Resolution: Partially successful - guided through multiple approaches including npm install, GitHub install, and building from monorepo, but version conflict persisted

2. **Plugin Development Guidance**
   - Helper: shaw
   - Helpee: lantianlaoli
   - Context: User was confused about which codebase to use for developing a text chat plugin
   - Resolution: Suggested using "v2-develop" branch

3. **Version Clarification**
   - Helper: Ruby
   - Helpee: BMK
   - Context: Confusion about ElizaOS versions
   - Resolution: Explained that V2 is the development branch with new features while Beta 41 is the stable release

## Action Items

### Technical
- Fix dependency loop issues in bun link/unlink functionality (Mentioned by Ruby)
- Resolve version reporting inconsistency between npm and elizaos CLI (Mentioned by kandizzy)
- Develop a text chat plugin using the v2-develop branch (Mentioned by lantianlaoli)
- Address unspecified issue in next beta release (Mentioned by sayonara)

### Feature Development
- Create functionality to retrieve token information (price, volume, marketcap) (Mentioned by OpsDev | Onyx)
- Implement token swap and transfer functionality with status updates and transaction hash links (Mentioned by OpsDev | Onyx)
- Add token deployment capabilities (Mentioned by OpsDev | Onyx)
- Integrate wallet connection without private key usage (Mentioned by OpsDev | Onyx)

### Documentation
- Create clearer documentation about version differences between stable and development branches (Mentioned by BMK)