{ "server": "Hyperfy", "title": "Hyperfy Discord - 2025-01-07", "date": 1736208000, "stats": { "totalMessages": 2936, "totalUsers": 305 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Analysis of 💻│developers Channel\n\n## 1. Summary\nThe discussion primarily revolves around Hyperfy development challenges, particularly focusing on documentation gaps and the upcoming V2 release. StrawberrySith repeatedly expresses frustration about the lack of clear documentation for modifying existing apps in live Hyperfy environments. Several developers attempt to help, explaining that in V1, users cannot directly edit live apps but must create new ones and upload them. Jin shares an unofficial documentation link that hasn't been merged into the official docs. Ashxn provides a preview of V2 features, demonstrating an AI agent (Shaw) integration that can interact with the world environment without coding. The conversation highlights that V2 will simplify development by allowing in-browser coding without local setup, support multi-chain functionality through plugins, and improve the overall developer experience. There's also discussion about UI components, with Ashxn sharing examples of undocumented GuiView elements.\n\n## 2. FAQ\nQ: How do I access my space using CLI? (asked by StrawberrySith) A: Use npm run connect and npm run upload where is the app id (answered by yung_algorithm)\nQ: Is there a way to download an environment that's live, modify it, and then re-upload it? (asked by StrawberrySith) A: For V1 you cannot edit current apps in your \"live\" world, you can only upload new ones made by you (answered by Lastraum)\nQ: Will V2 support a in-game marketplace and custom currencies? (asked by SotoAlt) A: Details for V2 are still being polished but customization and interoperability are part of the vision (answered by maximus)\nQ: Can we use wallet as inventory so each NFT is a 3D asset? (asked by SotoAlt) A: V1 supports the wallet as a backpack concept, so V2 will likely be able to read wallet contents (answered by maximus)\nQ: Will there be a customization interface to use different cosmetics on your agent or character? (asked by SotoAlt) A: Unanswered directly, but implied yes based on V2 capabilities\nQ: Do V1 lands support the Solana network? (asked by 3rdEyeVisuals) A: No (answered by ApeironCreations)\nQ: Is it safe to assume the V2 will offer Solana capability? (asked by 3rdEyeVisuals) A: Yes, multi-chain through plugins (answered by Ashxn)\nQ: If I write a custom app for V1 is it likely to work in V2? (asked by hiroP) A: Unanswered\nQ: Are there V1 SDK components for 2D UI elements? (asked by mattimus) A: Yes but undocumented right now, like GuiView (answered by Ashxn)\nQ: Does it support images too? (asked by mattimus) A: Unanswered\n\n## 3. Help Interactions\nHelper: yung_algorithm | Helpee: StrawberrySith | Context: Accessing Hyperfy space via CLI | Resolution: Provided commands for connecting and uploading to live environment\nHelper: jin | Helpee: Channel members | Context: Documentation access | Resolution: Shared link to unofficial documentation that wasn't merged into official docs\nHelper: Lastraum | Helpee: StrawberrySith | Context: Editing live apps in Hyperfy | Resolution: Explained that in V1 you cannot edit current apps in live worlds, only upload new ones\nHelper: Ashxn | Helpee: Channel members | Context: UI components in V1 | Resolution: Shared example of undocumented GuiView component for 2D UI elements\nHelper: maximus | Helpee: yung_algorithm | Context: Performance monitoring | Resolution: Explained how to view performance stats using the tilde (~) key\n\n## 4. Action Items\nType: Documentation | Description: Create better documentation for accessing and modifying Hyperfy spaces | Mentioned By: StrawberrySith\nType: Documentation | Description: Document the process for uploading and using custom apps | Mentioned By: StrawberrySith\nType: Documentation | Description: Create a dedicated #documentation channel for community contributions | Mentioned By: StrawberrySith\nType: Documentation | Description: Document UI components like GuiView | Mentioned By: mattimus\nType: Feature | Description: Fix camera-jitter bug when switching from 1st to 3rd person | Mentioned By: yung_algorithm\nType: Technical | Description: Optimize world models for better performance | Mentioned By: yung_algorithm\nType: Feature | Description: Support for multi-chain functionality in V2 | Mentioned By: Ashxn\nType: Feature | Description: In-browser coding without local setup in V2 | Mentioned By: Ashxn\nType: Feature | Description: Integration of AI agents like Shaw that can interact with world elements | Mentioned By: Ashxn", "messageCount": 212, "userCount": 28 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of Hyperfy Discord Chat\n\n## 1. Summary\nThe chat revolves around Hyperfy, a web-based metaverse platform transitioning from V1 to V2. The V1 version required NFT ownership to build worlds, while the upcoming V2 will be open source, self-hostable, and accessible to everyone without NFTs. The project recently launched its $HYPER token on Solana with an airdrop for V1 NFT holders and eligible ai16z partners (those holding 100k+ tokens at snapshot). The airdrop process involves registering ETH addresses and connecting Solana wallets to claim approximately 151,200 tokens per world owned. \n\nKey technical discussions focused on V2's features: browser-based 3D environments that work across devices including VR, lightweight server requirements (1-2GB RAM), and upcoming Eliza AI agent integration. The platform allows for codeless interaction between AI agents and world objects. Developers emphasized that V2 is a complete rebuild with better performance, in-browser editing capabilities, and open-source architecture. The token will power a DAO that will fund ecosystem development, though specific utility details haven't been released yet.\n\nCommunity members expressed concerns about airdrop selling pressure affecting token price, with approximately 13% of the airdrop allocation remaining unclaimed. The team clarified that liquidity is locked, and the token distribution includes 15% for the team (3-year linear vesting), 30% for the DAO, and 20% for liquidity.\n\n## 2. FAQ\nQ: What is the difference between V1 and V2? (asked by iebaz) A: V2 is a complete rebuild with better performance, open source, self-hostable, better in-world editing including coding in-browser. (answered by Ashxn)\nQ: Will V1 worlds be transferred to V2? (asked by MokonaW) A: No automatic transfer, but 3D models, avatars and emotes will still be supported using the same formats. (answered by Ashxn)\nQ: How much server resources are needed for self-hosting? (asked by mattimus) A: Very lightweight - tests showed it running with 512MB RAM, but 1-2GB recommended as the world simulates on the server with all models. (answered by Ashxn)\nQ: How many tokens were airdropped per world? (asked by devilsadvocate.sol) A: About 151,200 tokens per world. (answered by maximus)\nQ: What will happen to unclaimed airdrop tokens? (asked by Juank) A: Likely to be locked in the claims program forever with ownership renounced, or moved to the DAO. (answered by Saori)\nQ: What is the tokenomics breakdown? (asked by ᴍ ᴀᴍɪɴ) A: 15% team (3-year linear vesting), 30% DAO (eventually controlled by token voting), 20% locked liquidity. (answered by Saori)\nQ: Do V1 NFTs have any additional utility? (asked by Dave.) A: No more than building on V1 worlds. No extra utility related to V2. (answered by maximus)\nQ: When is V2 releasing? (asked by WarfreakzPlays) A: Very soon, likely within a week or two. (answered by maximus)\nQ: What will the DAO be used for? (asked by Juank) A: To let token holders vote on third-party projects that benefit Hyperfy, marketplaces, free content, AI research, etc. (answered by Ashxn)\nQ: Is the liquidity locked? (asked by CryptoFarmer) A: Yes, liquidity is locked on Raydium. (answered by Saori)\n\n## 3. Help Interactions\nHelper: maximus | Helpee: Kz | Context: Wanted to try building in Hyperfy | Resolution: Added user to a sandbox world to experiment with building components\nHelper: maximus | Helpee: SotoAlt | Context: Requested access to build in a world | Resolution: Added user to a world with building permissions\nHelper: maximus | Helpee: 0xVincent | Context: Confusion about airdrop eligibility and registration process | Resolution: Directed to support channel and warned about scammers\nHelper: TropixMusic | Helpee: leonhunter 🍄 | Context: Confusion about claim site legitimacy (.xyz vs .io domains) | Resolution: Confirmed both domains are legitimate and explained their different purposes\nHelper: maximus | Helpee: Milito $BAG 🚀 | Context: Confusion about airdrop eligibility status | Resolution: Explained registration takes about a day to process\nHelper: Ashxn | Helpee: Multiple users | Context: Released a batch update for airdrop claims | Resolution: Users who registered late were able to claim their tokens\nHelper: maximus | Helpee: Gamer | Context: Identified a scammer creating fake support tickets | Resolution: Warned about the scam and reported to team to fix permissions\n\n## 4. Action Items\nTechnical: Implement Eliza AI agent integration into Hyperfy | Description: Adding AI agents that can interact with world objects | Mentioned By: Ashxn\nTechnical: Launch V2 platform | Description: Release open-source, self-hostable version with better performance | Mentioned By: Ashxn\nTechnical: Fix permissions to prevent scammers from creating fake support tickets | Description: Scammers were able to create threads that looked like support tickets | Mentioned By: maximus\nTechnical: Create a token-specific channel | Description: Separate channel for token price discussions | Mentioned By: maximus\nDocumentation: Update OpenSea profile to clarify V1 NFTs' limited utility | Description: Prevent people from buying V1 NFTs expecting V2 benefits | Mentioned By: Ashxn\nDocumentation: Create documentation for V2 features | Description: Comprehensive documentation for the new platform | Mentioned By: Ashxn\nFeature: Implement DAO governance system | Description: Allow token holders to vote on ecosystem projects | Mentioned By: Ashxn\nFeature: Develop codeless AI agent interaction system | Description: Allow users to create AI interactions without coding | Mentioned By: Ashxn\nFeature: Determine process for unclaimed tokens | Description: Decide whether to burn or move to DAO | Mentioned By: Saori\nFeature: Consider world migration tools from V1 to V2 | Description: Tools to help transfer existing worlds to the new platform | Mentioned By: BallisticBanana", "messageCount": 2319, "userCount": 276 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Discord Chat Analysis for 🧊│3d-design Channel\n\n## 1. Summary\nThe chat segment contains brief discussions about Hyperfy's 3D design capabilities, particularly regarding Blender integration and the upcoming v2 release. A user asked about documentation for Blender integration with Hyperfy, and was directed to the v1 documentation. There was anticipation expressed about individual object criteria in the new version. Another user inquired whether it would be better to wait for v2 before starting to build, to which maximus confirmed it would be preferable for new users to avoid learning v1 nuances. There was also a brief mention of virtual protocol agent integration, which was redirected to another channel as it was more development-focused than design-specific.\n\n## 2. FAQ\nQ: Any docs on how it works for blender? (asked by Matt [Cheems Guevara]) A: https://docs.hyperfy.io/designers/overview This is for v1 (answered by Ashxn)\nQ: is it better to wait for v2 to start building, right? (asked by Milito $BAG 🚀) A: Haha since we're so close may be better to wait if you're completely new to hyperfy so that it's all fresh. You don't have to worry about v1 nuances (answered by maximus)\nQ: when.v2？(asked by Xandaz) A: Unanswered\nQ: is it possible to add virtuals protocolo agents too? (asked by Milito $BAG 🚀) A: That sounds like a <#994775534733115412> question haha... I'm 99% the answer is use, assuming the protocol uses an API or something to allow people to connect with it. (answered by maximus)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: Matt [Cheems Guevara] | Context: Needed documentation for Blender integration with Hyperfy | Resolution: Provided link to v1 documentation\nHelper: maximus | Helpee: Milito $BAG 🚀 | Context: Whether to wait for v2 before starting to build | Resolution: Advised waiting for v2 if completely new to Hyperfy to avoid learning v1 nuances\n\n## 4. Action Items\nTechnical: Wait for v2 release before starting new Hyperfy projects | Description: New users should wait for v2 to avoid learning soon-to-be-outdated v1 features | Mentioned By: maximus\nDocumentation: Update documentation for v2 | Description: Current documentation is for v1 and will need updating | Mentioned By: Ashxn\nFeature: Individual object criteria | Description: Users are anticipating object-specific features in v2 | Mentioned By: scoe", "messageCount": 13, "userCount": 7 }, { "channelId": "999870741069692958", "channelName": "🌆│share", "summary": "# Analysis of Discord Channel \"🌆│share\"\n\n## 1. Summary\nThe chat primarily consists of community members sharing links to Twitter/X threads, articles, and content about Hyperfy - a metaverse platform. Several informative threads about Hyperfy's vision, journey, and capabilities were shared by members including MetaMike, maximus, and The Smart Entrepreneur. There was a brief technical discussion comparing Hyperfy with BitmapOS, highlighting Hyperfy's superior technology and upcoming open-source capabilities (v2). Members discussed how Hyperfy's open-source approach would allow projects to leverage its technology as a base for virtual environments. The conversation touched on the implications of Hyperfy going open-source, with predictions that many projects would benefit from using it as their foundation rather than building their own \"clunky virtual world environment.\" There was also mention of potential increased need for technical support once the platform becomes more widely accessible.\n\n## 2. FAQ\nQ: Are there any seasoned builders here who can help me with a few questions privately? (asked by StrawberrySith) A: Unanswered\nQ: Is there a video where I can see that in-world [BitmapOS]? (asked by Cynnx, son of Ash and Roustan) A: Yeah there's a bunch of videos you can dig through on the BlockRunners YT... Here's a good quick build tutorial that gives an idea of the current state of things (answered by ctramount)\n\n## 3. Help Interactions\nHelper: ctramount | Helpee: Cynnx, son of Ash and Roustan | Context: Requested information about BitmapOS in-world experience and videos | Resolution: Provided YouTube channel link and a specific tutorial video showing the current state of BitmapOS\n\n## 4. Action Items\nTechnical Tasks: None explicitly mentioned\nDocumentation Needs: None explicitly mentioned\nFeature Requests: None explicitly mentioned", "messageCount": 26, "userCount": 11 }, { "channelId": "1022421054582423562", "channelName": "🐞│issues", "summary": "# Analysis of 🐞│issues Channel\n\n## 1. Summary\nThe chat primarily revolves around the Hyperfy airdrop claiming process. Users are experiencing various issues with claiming their tokens, including wallet eligibility problems, registration delays, and technical difficulties. The airdrop requires users to register their Ethereum wallet (which held Hyperfy Worlds NFTs during a snapshot) and link it to a Solana wallet for claiming tokens. The process typically takes 24 hours after registration before claiming becomes available. Several technical challenges emerged, particularly with certain wallet types like Coinbase wallets and Safe wallets. The team processes registrations in batches and is actively helping users troubleshoot issues. There were also some scam attempts targeting users trying to claim their airdrops. Additionally, there was a brief DDoS threat from a user claiming to have been banned after attempting to disclose a vulnerability, though this appeared to be an isolated incident.\n\n## 2. FAQ\nQ: When will I be able to claim my airdrop after registering? (asked by multiple users) A: It takes about 24 hours after registration for the claim to become available (answered by maximus)\nQ: Why does my wallet show as \"not eligible\" on the claim site? (asked by multiple users) A: You need to register on hyperfy.io/airdrop first, then wait about 24 hours for the batch processing (answered by maximus)\nQ: What's the difference between hyperfy.io and hyperfy.xyz? (asked by Clammy Devito) A: The .io site is for v1 and the .xyz site is for v2 (answered by maximus)\nQ: Can I use a Coinbase wallet for the airdrop? (asked by VTATV) A: It's not recommended as you don't fully own that wallet, but some users found workarounds (answered by ash)\nQ: Will worlds created in v1 function in v2? (asked by AcidManhattan) A: No, v1 will be left as is, v2 will be a new platform and won't port old worlds (answered by maximus)\nQ: Is there auto-save when building in Hyperfy? (asked by AcidManhattan) A: No, you need to manually save by scrolling to the bottom of the palette and pressing the save button (answered by maximus)\nQ: What are best practices for importing GLBs? (asked by AcidManhattan) A: Reduce draw calls, use textures to reduce footprint/polygons, and keep object size small (answered by maximus)\nQ: What if I changed my SOL address after registration? (asked by jomalon) A: Updates don't work well and will delay the process by 12-24 hours (answered by maximus)\nQ: How do I connect my Ledger wallet for the airdrop? (asked by lorenzo) A: Use Metamask + Ledger to connect to the airdrop site (answered by maximus)\nQ: What if I moved my World NFT after the snapshot? (asked by masosim) A: Only the wallet that was holding it at snapshot works for claiming (answered by maximus)\n\n## 3. Help Interactions\nHelper: maximus | Helpee: zocktay | Context: User claimed 2x2 but couldn't claim tokens | Resolution: Explained they would be in the next batch in 24 hours\nHelper: maximus | Helpee: VTATV | Context: User registered with Coinbase wallet but couldn't claim | Resolution: Team investigated the issue; user eventually found a workaround\nHelper: maximus | Helpee: TheMattEmpire | Context: User encountered error when claiming | Resolution: User found solution by checking Console in Developer Tools and refreshing page\nHelper: maximus | Helpee: stikkx | Context: User received scam invitation to fake support server | Resolution: Maximus requested screenshots to identify scammer and warned about scam attempts\nHelper: ash | Helpee: masosim | Context: User moved NFT after snapshot and couldn't claim | Resolution: Ash investigated and confirmed NFT should be claimable, promised to follow up\nHelper: wondering chew | Helpee: lorenzo | Context: User needed to sync ETH ledger wallet with SOL wallet | Resolution: Provided step-by-step instructions for registration process\nHelper: maximus | Helpee: PabloFM | Context: User having issues with Safe wallet signature | Resolution: Identified technical issue with Safe wallets, suggested porting wallet if possible\n\n## 4. Action Items\nTechnical: Investigate and fix issues with Safe wallet signatures for airdrop registration | Mentioned By: PabloFM\nTechnical: Process new batch of airdrop registrations | Mentioned By: ash\nTechnical: Fix circulating supply information on Dexscreener | Mentioned By: Kizzah\nTechnical: Investigate \"message does not match signature\" error with multisign wallets | Mentioned By: DevStarlight\nTechnical: Address issue with Coinbase wallet compatibility | Mentioned By: VTATV\nTechnical: Fix registration updates not working properly when users change SOL address | Mentioned By: jomalon\nDocumentation: Create guide for connecting hardware wallets to claim airdrop | Mentioned By: lorenzo\nDocumentation: Clarify the difference between hyperfy.io and hyperfy.xyz domains | Mentioned By: Clammy Devito\nDocumentation: Add warning about manual save requirement in builder | Mentioned By: AcidManhattan\nDocumentation: Create best practices guide for importing GLB files | Mentioned By: AcidManhattan\nFeature: Implement auto-save functionality in world builder | Mentioned By: AcidManhattan\nFeature: Improve wallet connection reliability | Mentioned By: BitFiend", "messageCount": 361, "userCount": 47 }, { "channelId": "958214956426350652", "channelName": "📣│announcements", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe announcements channel contains critical security warnings and important updates about NFT claims and wallet linking deadlines. Key points include:\n- Users who linked SOL addresses late can now claim their tokens\n- Multiple warnings about scammers impersonating staff members in DMs\n- Critical announcement that Hyperfy World NFTs are no longer mintable from the website\n- Warning that future utility for these NFTs is not guaranteed\n- Extension of the deadline for linking ETH and SOL wallets for the $HYPER airdrop from January 7 to January 12, 2025\n- Security alert about fake support threads/tickets being created to scam users\n\nThe communications focus primarily on security concerns, deadline extensions, and ensuring users don't miss important opportunities to link wallets or claim tokens.\n\n## 2. FAQ\nNo explicit questions and answers were present in this announcement channel.\n\n## 3. Help Interactions\nNo explicit help interactions between community members were present in this announcement channel.\n\n## 4. Action Items\nTechnical: Link SOL addresses to claim tokens | Description: Users who linked SOL addresses late should now be able to claim | Mentioned By: ash\nTechnical: Link ETH and SOL wallets before deadline | Description: Users must link wallets before January 12, 2025 to be eligible for $HYPER airdrop | Mentioned By: Saori\nDocumentation: Update NFT status information | Description: Hyperfy World NFTs are no longer mintable and future utility is not guaranteed | Mentioned By: ash\nDocumentation: Security warning about scammers | Description: Users should be cautious of DM impersonators and fake support threads | Mentioned By: ash, Saori", "messageCount": 5, "userCount": 2 } ] }