# elizaOS Discord - 2025-12-30

## Overall Discussion Highlights

### Token & Price Movement
- **Significant Price Increase**: ElizaOS token experienced approximately 120% growth following Shaw's return to X (formerly Twitter)
- **Sentiment Shift**: Community sentiment dramatically improved after the price increase, with previously negative members becoming more optimistic
- **Token Migration**: Ongoing discussions about migration from ai16z to ElizaOS, with many users seeking clarification on the process and timeline
- **Token Information**: Kenk acknowledged the need for improved website accessibility regarding token information, adding details to docs.elizaos.ai/tokenomics

### Technical Development
- **Hooks Implementation**: Stan shared progress on unified hooks with multi-transport support (HTTP/SSE/WebSocket) and fixed issues with duplicate events
- **Plugin Improvements**: Odilitime fixed image generation in the OpenAI plugin and added caching to prevent redundant media processing
- **Agent Development**: MemeBroker shared GitHub repositories for Eliza agent skills and a plugin for OpenSouls framework integration
- **ElizaCloud Integration**: Discussions about integrating ElizaCloud agents into websites using API endpoints

### Infrastructure Plans
- **Jeju Infrastructure**: Shaw outlined plans to initially launch on AWS with a goal to transition to self-owned permissionless infrastructure with physical racks in data centers by year-end
- **Alternative Platforms**: Discussions about platforms for agent deployment that avoid Twitter API costs ($200/month barrier)

### Community & Ecosystem
- **Spartan Group**: Several users inquired about joining the Spartan group/channel, which requires holding a specific amount of tokens for access
- **Related Projects**: Discussions about the relationship between ElizaOS, DegenAI, and Ruby tokens within the ecosystem
- **Documentation Needs**: Suggestions to enhance documentation explaining ElizaOS's role as the first appcoin on Jeju and its relationship with future appcoins

## Key Questions & Answers

- **Q**: What are the plans for Jeju infrastructure?  
  **A**: Initially launching on AWS with plans to transition to self-owned permissionless infrastructure in data centers by year-end (answered by Shaw)

- **Q**: Where can users find token information?  
  **A**: Currently at docs.elizaos.ai/tokenomics with plans to improve website accessibility (answered by Kenk)

- **Q**: How can I join the Spartan group?  
  **A**: Verify your holding in #verify-wallet (answered by Kenk)

- **Q**: What's with the pump?  
  **A**: Shaw returned to X (answered by chomppp)

- **Q**: How do I get the correct character URL?  
  **A**: Copy the URL directly from the browser instead of using the share link button; it should contain the character ID (answered by Destiny)

- **Q**: How do I integrate an ElizaCloud agent into my website?  
  **A**: You need to get the agent ID using the ElizaCloud API endpoint with your API key (answered by sam)

- **Q**: Should I pump the version for every plugin PR I make?  
  **A**: "That's what I'm doing. But I guess we should have a CI like in monorepo like release please or something like that" (answered by Stan)

- **Q**: Is there a Twitter plugin which still uses cookie-based authentication?  
  **A**: No (answered by Odilitime)

## Community Help & Collaboration

- **MemeBroker** created and shared GitHub repositories with skills for making Eliza agents (https://github.com/Merlinthewizord/Skills_elizaos) and a plugin for OpenSouls framework integration (https://github.com/Merlinthewizord/plugin-opensouls)

- **Destiny** helped **Peter Gibbons** with getting the correct character URL by instructing to copy the URL directly from browser instead of using the share link

- **sam** assisted **BAOVERSE** with integrating ElizaCloud agent into a website by providing API endpoint code to retrieve agent ID and DMing additional integration code

- **Omid Sa** directed **Moto** to the #migration-help channel for step-by-step assistance with ai16z token migration

- **Kenk** helped **MATTIOBOY** join the Spartan gated channel by instructing to verify holdings in #verify-wallet

- **Odilitime** offered to cover Northern California for data center infrastructure in response to Shaw's infrastructure plans

## Action Items

### Technical
- Fix action call log type registration (PR #6296) (Mentioned by Stan)
- Implement unified hooks with multi-transport support (HTTP/SSE/WebSocket) (PR #6300) (Mentioned by Stan)
- Fix image generation and add caching in OpenAI plugin (PR #23) (Mentioned by Odilitime)
- Clean up cloud codebase by reducing duplications and improving type handling (Mentioned by Stan)
- Update Collabland to properly reflect ElizaOS token holdings instead of ai16z (Mentioned by coinfucius.eth)
- Implement ElizaOS for role verification (Mentioned by Kenk)
- Complete web3 EVM signing for stack that's already built (Mentioned by Odilitime)
- Update MCP status for Kaizen (Mentioned by Diamondhandwhiteboy)
- Explore alternative platforms for agent deployment to avoid Twitter API costs (Mentioned by M I A M I)
- Implement ElizaCloud agent integration with websites using API endpoints (Mentioned by sam)
- Website refresh with improved token information accessibility (Mentioned by Kenk)
- Add Coingecko links to website footer as short-term solution (Mentioned by Kenk)
- Transition from AWS to self-owned permissionless infrastructure by end of year (Mentioned by Shaw)

### Documentation
- Create dedicated token page with CA addresses, exchanges, links to community hubs and tracking sites (Mentioned by Broccolex)
- Add explanation of ElizaOS as first appcoin on Jeju and its relationship with future appcoins (Mentioned by DorianD)
- Create visual aids to help explain new concepts related to Jeju and ElizaOS (Mentioned by DorianD)
- Create a list of projects launching on Eliza Cloud (Mentioned by Cryptor)
- Clarify the relationship between ElizaOS, DegenAI, and Ruby tokens (Mentioned by Jack)

### Feature
- Consider implementing action calls by embeddings for IoT plugins (Mentioned by Stan)
- Create skills specifically for making Eliza agents (Mentioned by jin)
- Integrate OpenSouls framework with Eliza via plugin (Mentioned by MemeBroker)
- Develop proprietary fine-tune of Llama 3.2 optimized for social platform ecosystem (Mentioned by M I A M I)