# Hyperfy Discord - 2025-12-11

## Overall Discussion Highlights

### Hyperfy 2.0 Platform Status
- Hyperfy 2.0 is considered feature-complete as an open-source engine, sandbox, and toolkit for building virtual experiences
- The platform supports generative AI integration to make development accessible to non-coders
- Users can choose self-hosting or third-party hosting services, which require more user responsibility than v1
- Some community members are actively developing projects (like "Hyperscape") using the platform, though details remain private

### Community Sentiment
- Tension exists between members expecting more direct platform development versus those who see Hyperfy 2.0 as a complete toolkit ready for community-driven innovation
- Some frustration expressed about limited communication from founder Ash regarding development progress
- Supporters defend the platform's current capabilities, emphasizing it's an open-source platform not a game

### $HYPER Token Integration
- Questions raised about the removal of native $HYPER token integration from the main branch
- Community members interested in possibilities for incorporating token utility in custom builds or forks

## Key Questions & Answers

**Q: Does "some ppl" mean ASH, or is there a whole Group of people keeping this "Hyperscape" Project out of Public Vision?** (asked by Agent12)  
**A:** Partially answered by vox, indicating multiple people are working on projects including Hyperscape that aren't yet public

**Q: What is Hyperfy 2.0?** (asked by Agent12)  
**A:** Explained by vox that Hyperfy 2.0 is a versatile engine/toolkit allowing for various projects including Hyperscape

## Community Help & Collaboration

- **vox helped Agent12** by clarifying what Hyperfy 2.0 is and how it's being used, explaining that it's a versatile engine/toolkit allowing for various projects
- **3rdEyeVisuals helped the general community** by addressing frustration about expectations for Hyperfy development, clarifying that V2 is complete and ready for anyone to develop their own experiences

## Action Items

### Technical
- Explore self-hosting or third-party hosting options for Hyperfy 2.0 projects (Mentioned by: vox)
- Consider how to incorporate $HYPER token utility in custom builds (Mentioned by: MetaDJ)

### Documentation
- Clarify the current status of native $HYPER token integration in the codebase (Mentioned by: MetaDJ)

### Feature
- Evaluate possibility of adding native $HYPER integration back to main branch (Mentioned by: MetaDJ)