# elizaOS Discord - 2025-02-23

## Overall Discussion Highlights

### ElizaOS Development & Releases
- **v0.25.8 Release**: Odilitime announced the release of v0.25.8, which moved plugins out of the main codebase
- **ElizaOS V2 Codebase**: Shaw is developing a new V2 codebase with expected release in early April
- **Plugin System Changes**: Multiple users noted the recent changes to the plugin architecture, with plugins being moved to separate repositories
- **Technical Challenges**: Users reported issues with database integration (particularly Qdrant and PGVector), embedding model configurations, and API authentication with various LLM providers

### Rebranding from ai16z to ElizaOS
- **Token Contract Address**: Team members clarified that despite rebranding, the token contract address will remain unchanged
- **Ticker Change**: Working with daos.fun to change the ticker while maintaining the same contract address
- **Messaging Concerns**: Partners discussed the challenge of maintaining clear messaging during the transition period
- **Timeline**: accelxr confirmed the rebrand is on track for midweek implementation, pending community feedback and logistics

### Community Projects & Implementations
- **Instacart Agent**: A community member (scooper) shared their successful implementation of an Instacart agent built using ElizaOS for meal planning and grocery ordering
- **L2 Development**: DorianD is working on an L2 solution for ElizaOS using Solana validators, despite facing significant build errors
- **Avalanche Integration**: yikesawjeez offered to implement something on Avalanche over the weekend
- **Eliza Fighter Game**: Discussion about creating a fighting game with Eliza characters using a VRM-to-spritesheet pipeline
- **Clank Tank Show**: Jin announced the premiere of "Clank Tank" (a show featuring AI projects) with plans for improvements

### Tokenomics & Blockchain
- **Liquidity Layer**: Focus on building a liquidity layer for AI16 SPL2022 token across projects rather than creating a true L1 blockchain
- **Token Status**: Multiple clarifications that ai16z is an infrastructure token for the ElizaOS ecosystem, not merely a meme coin
- **Mintable Status**: wlt provided documentation explaining why the token remains mintable
- **Yield Generation**: Research into re-hypothecation of staked coins to generate yield for paying L2 nodes

### AI Model Discussions
- **Grok-3 Trading Bot Claims**: Skepticism about claims of a profitable trading bot created using Grok-3, with experienced members dismissing it as "engagement farming"
- **Embedding Models**: Questions about free embedding models for testing purposes
- **Memory Vector Size**: Technical discussions about changing default memory vector size from 384 to 768 for Qdrant database

## Key Questions & Answers

**Q: Why is minting authority not renounced on ai16z token?**  
A: Documentation explains the rationale: https://elizaos.github.io/eliza/community/Notes/lore/#why-mintable-on-dexscreener (answered by wlt 🧩)

**Q: How does the upcoming rebrand affect the ai16z token?**  
A: The contract address remains unchanged. Once the rebrand is complete, they will be able to promote the token and announce planned tokenomics. (answered by Patt)

**Q: Is ai16z token more like a meme coin or an elizaos ai infrastructure ecosystem token?**  
A: It's an ElizaOS infrastructure token. Started as a meme token (parody of a16z) but has evolved into the largest web3 AI framework. (answered by Spyros and witch)

**Q: Do I need to convert ai16z token to ElisaOS token?**  
A: No new contract address, no new token. No action needed from holders. (answered by Spyros)

**Q: Why is my Hyperbolic API failing to authenticate in v0.25.6?**  
A: It's likely an issue on Hyperbolic's side as the plugin code hasn't changed; you need a valid API key with credits in your account. (answered by Odilitime and AIFlow.ML)

**Q: How do I give an agent access to a SQL database as knowledge?**  
A: Integrate it with langchain SQL service using langchain_community.utilities SQLDatabase. (answered by Kren)

**Q: Does Eliza send the full character context each time or does it vectorize the input?**  
A: It sends samples from the character file, including randomly selected engagements from the DB; there's context trimming if it exceeds model limits. (answered by NoContext)

**Q: Does direct client of Eliza support websocket?**  
A: No, but they want to add it. (answered by shaw)

**Q: Is the project creating an actual L1 blockchain?**  
A: No, it's still the AI16 SPL2022 token, just functioning as a liquidity layer across projects. (answered by yikesawjeez)

**Q: Are you planning to change up the setting for every episode of Clank Tank?**  
A: No, they want to be consistent per season at least, but can still make light improvements. (answered by jin)

## Community Help & Collaboration

1. **Hyperbolic API Authentication**  
   - Helper: Odilitime  
   - Helpee: Slise  
   - Context: Hyperbolic API authentication failing in v0.25.6  
   - Resolution: Identified it was a Hyperbolic issue, suggested switching to Redpill model which worked

2. **Character Context Understanding**  
   - Helper: NoContext  
   - Helpee: devilsadvocate.sol  
   - Context: Understanding how character context is sent to LLM  
   - Resolution: Explained that samples from character file and random DB engagements are used, with context trimming if needed

3. **Memory Allocation Error**  
   - Helper: boolkeys  
   - Helpee: domanodes  
   - Context: JavaScript heap out of memory error  
   - Resolution: Suggested increasing memory allocation with NODE_OPTIONS="--max-old-space-size=4096" and provided options for different memory sizes

4. **Plugin Registry Issue**  
   - Helper: Odilitime  
   - Helpee: ian  
   - Context: SQD plugin missing from registry after being merged  
   - Resolution: Identified the commit that accidentally removed multiple plugins and offered to handle restoring them

5. **RAG Configuration**  
   - Helper: boolkeys  
   - Helpee: 9000  
   - Context: How to use knowledge/RAG with Eliza  
   - Resolution: Provided detailed documentation on RAG configuration, knowledge types, and file path setup

6. **Nous Research Relationship**  
   - Helper: jin  
   - Helpee: Community  
   - Context: Clarifying relationship with Nous Research  
   - Resolution: Jin spoke with John and another Nous representative, confirmed that labeling ElizaOS as "enemies" didn't reflect the organization's view and they're on good terms

7. **Rebranding Strategy**  
   - Helper: accelxr  
   - Helpee: Community  
   - Context: Rebranding strategy and timeline  
   - Resolution: Shared rebrand designs and confirmed midweek timeline for implementation, noting ticker change is outside their control

## Action Items

### Technical
- Continue development of ElizaOS V2 codebase for early April release (mentioned by witch)
- Implement token ticker change while maintaining the same contract address (mentioned by Patt)
- Fix validation in action handlers to properly respect return values (mentioned by Sabochee)
- Add websocket support to direct client (mentioned by shaw)
- Fix memory vector size configuration for different embedding dimensions (mentioned by Lucas Fernandes)
- Fix Twitter client ACTION_TIMELINE_TYPE=following setting (mentioned by Slise)
- Fix "Invalid array length" error in knowledge processing (mentioned by Dean)
- Implement liquidity layer on Avalanche over the weekend (mentioned by yikesawjeez)
- Continue development of L2 for ElizaOS using Solana validators (mentioned by DorianD)
- Implement logging/evaluation system for plugins (mentioned by DorianD)
- Research re-hypothecation of staked coins (mentioned by DorianD)
- Make discord-summarizer loop more autonomous/easier to deploy (mentioned by jin)
- Improve AI/writers room for Clank Tank (mentioned by jin)

### Documentation
- Provide complete tokenomics documentation after launchpad release (mentioned by witch)
- Update memory configuration documentation (mentioned by Lucas Fernandes)
- Create guide for custom database adapters (mentioned by Lucas Fernandes)
- Add examples for actions implementation (mentioned by domanodes)
- Improve ElizaOS docs (mentioned by jin)
- Ensure clear messaging during rebranding that ai16z ticker is ElizaOS (mentioned by HoneyBadger)
- Change DEX screener banner to ElizaOS (mentioned by HoneyBadger)

### Feature
- Consider multi-chain support for the token beyond Solana (mentioned by Void)
- Develop agent launch platform powered by Eliza with fee sharing back to protocol (mentioned by Zeke)
- Open source the Instacart plugin for community use (mentioned by scooper)
- Implement LinkedIn client (mentioned by 0xConsole)
- Support for local embedding models (mentioned by Waqas Wahid)
- Make Clank Tank judges less agreeable/include rejections (mentioned by HoneyBadger)
- Develop Eliza plugin (Nethermind working on eliza-chaoschain-plugin) (mentioned by mat)
- Explore VRM-to-spritesheet pipeline for Eliza Fighter game (mentioned by jin)
- Prepare something for partners to help pick next episode pitches (mentioned by jin)