{
  "server": "Hyperfy",
  "title": "Hyperfy Discord - 2025-01-06",
  "date": 1736121600,
  "stats": {
    "totalMessages": 5243,
    "totalUsers": 600
  },
  "categories": [
    {
      "channelId": "994775534733115412",
      "channelName": "💻│developers",
      "summary": "# Discord Chat Analysis for 💻│developers Channel\n\n## 1. Summary\nThe chat primarily revolves around developers seeking help with Hyperfy's React applications and documentation challenges. Several users, particularly StrawberrySith, express frustration with the current documentation's clarity and comprehensiveness. Ashxn (a core developer) mentions that version 2 (v2) of Hyperfy is in development, which will simplify app development by allowing in-browser coding without local development environments. Jin shares an unofficial documentation repository that hasn't been merged into the official docs yet. There are discussions about technical aspects like camera jitter bugs, performance optimization, and multi-chain support. The conversation also reveals that Hyperfy is moving toward open-sourcing their platform, with plans for plugin support and multi-chain compatibility in v2. Several community members, including the Numinia team, offer to help with documentation efforts.\n\n## 2. FAQ\nQ: How do I access my live Hyperfy space using CLI to edit React apps? (asked by StrawberrySith) A: Partial answer provided by yung_algorithm about using npm commands, but the full workflow wasn't clearly established\nQ: Will we have an opportunity to suggest new integrations like Zora when Hyperfy goes open source? (asked by StrawberrySith) A: Likely yes, according to maximus, as developers have spoken about open sourcing and \"giving human race a gift of the ages\"\nQ: Was the source code for the custom solana program (airdrop) ever published? (asked by t-900) A: Unanswered\nQ: Is there a way to download an environment that's live, modify it, and then re-upload it? (asked by StrawberrySith) A: Unanswered directly, though mattimus suggested reaching out to the original creator\nQ: Will there be docs on how to do UV mapping with screens? (asked by mattimus) A: Unanswered\nQ: Do V1 lands support the Solana network? (asked by 3rdEyeVisuals) A: No (answered by ApeironCreations), but Ashxn confirmed v2 will be multi-chain\nQ: If I write a custom app for v1 is it likely to work in v2? (asked by hiroP) A: Unanswered\n\n## 3. Help Interactions\nHelper: yung_algorithm | Helpee: StrawberrySith | Context: Setting up local development environment for Hyperfy | Resolution: Provided basic npm commands but full workflow wasn't established\nHelper: jin | Helpee: StrawberrySith | Context: Documentation needs | Resolution: Shared unofficial documentation repository that hasn't been merged into official docs\nHelper: maximus | Helpee: yung_algorithm | Context: Performance debugging | Resolution: Explained how to view performance stats using the tilde (~) key\nHelper: Ashxn | Helpee: StrawberrySith | Context: Difficulty with React app development | Resolution: Explained that v2 will simplify development by allowing in-browser coding\nHelper: DevStarlight | Helpee: Community | Context: Documentation needs | Resolution: Announced Numinia team is documenting components and making them public\n\n## 4. Action Items\nType: Documentation | Description: Create better documentation for React app development in Hyperfy | Mentioned By: StrawberrySith\nType: Documentation | Description: Merge Jin's unofficial documentation into official docs | Mentioned By: jin\nType: Technical | Description: Fix camera jitter bug in third-person view | Mentioned By: yung_algorithm\nType: Feature | Description: Implement multi-chain support in v2 | Mentioned By: Ashxn\nType: Feature | Description: Create in-browser coding capability for v2 | Mentioned By: Ashxn\nType: Documentation | Description: Document UV mapping with screens | Mentioned By: mattimus\nType: Technical | Description: Optimize world models for better performance | Mentioned By: yung_algorithm\nType: Feature | Description: Integrate Eliza app/AI capabilities | Mentioned By: SotoAlt\nType: Documentation | Description: Create video tutorials for developers | Mentioned By: Spizzy",
      "messageCount": 140,
      "userCount": 21
    },
    {
      "channelId": "958209074045026327",
      "channelName": "⚡│general",
      "summary": "# Analysis of Hyperfy Discord Chat\n\n## 1. Summary:\nThe conversation revolves around Hyperfy, a metaverse platform that recently launched its $HYPER token on Solana. The project is transitioning from a V1 model (where NFT ownership was required to build worlds) to a V2 model that will be open-source and permissionless. The token launch included an airdrop for legacy NFT holders and ai16z partners who held 100k tokens before the December 7th snapshot. Many discussions focused on the claim process, with users needing to link their ETH wallets to SOL addresses. The team emphasized that V1 NFTs no longer provide special benefits beyond building on the V1 platform, as V2 will be accessible to everyone. The token experienced significant price volatility after launch, reaching nearly 300M market cap before retracing. Developers Ash and Saori are actively working on V2 features, including AI agent integration with plans to launch within weeks. The community is excited about the platform's technical capabilities, particularly its browser-based accessibility across devices including VR.\n\n## 2. FAQ:\nQ: What is the difference between V1 and V2? (asked by Dave.) A: V1 was NFT-gated to build worlds, V2 will open gates and allow people to build more freely with newer features (answered by maximus)\nQ: Is it still worth buying V1 NFTs? (asked by felixcrypto0034) A: No, not for speculation. Only buy if you want to build on V1 worlds (answered by maximus)\nQ: What is the token utility? (asked by MwakaDegen) A: $HYPER is a utility token with DAO governance and will power the ecosystem (answered by Ashxn)\nQ: How many tokens did each world holder receive? (asked by syGMatMATTIOBOY) A: 151,200 tokens per world (answered by maximus)\nQ: Who was eligible for the airdrop? (asked by Believer | Fatty.io | CLONE) A: ETH NFT holders before December 7th snapshot and ai16z partners with 100k tokens (answered by maximus)\nQ: When will V2 be released? (asked by Alex) A: Less than 2 weeks based on updates from the dev team (answered by maximus)\nQ: Is the liquidity locked? (asked by Borriello) A: Yes, it is locked in Raydium (answered by Saori)\nQ: Will V1 worlds be migrated to V2? (asked by SomeOtherGuy) A: Team hasn't discussed exactly what migration may look like (answered by maximus)\nQ: How long does it take for registration to transfer to claim site? (asked by MrTouch) A: At least a day. It's a manual process (answered by maximus)\nQ: Is there a deadline for claiming the airdrop? (asked by Sceth iii) A: The deadline has been removed, it's now a claim process (answered by maximus)\n\n## 3. Help Interactions:\nHelper: maximus | Helpee: Spottie WiFi | Context: User having trouble connecting MetaMask to claim site | Resolution: Suggested clearing cache and waiting for registration to transfer to claim site\nHelper: maximus | Helpee: Gamer | Context: User targeted by scammer creating fake support ticket | Resolution: Warned about scam and explained that Hyperfy doesn't have a ticket system\nHelper: TropixMusic | Helpee: leonhunter 🍄 | Context: User confused about claim site legitimacy (.xyz vs .io domains) | Resolution: Provided official links from Twitter and explained both domains are legitimate\nHelper: Paradoxx | Helpee: Other ledger users | Context: Issues claiming with ledger connected to phantom wallet | Resolution: Suggested removing wallet from phantom and re-adding it\nHelper: maximus | Helpee: Ketsuban | Context: User stuck with wallet connect | Resolution: Suggested moving private key to MetaMask to connect correctly\nHelper: Uuuuuuuuu | Helpee: Community | Context: Explaining token price movements | Resolution: Clarified that price drops weren't just from airdrop recipients but also traders and market conditions\nHelper: Cynnx | Helpee: zombiekid12 | Context: User asking about platform experience | Resolution: Encouraged trying the platform and explained how accessible building will be for non-technical users\n\n## 4. Action Items:\nType: Technical | Description: Implement V2 with AI agent integration | Mentioned By: Ashxn\nType: Technical | Description: Update claim site to process new registrations | Mentioned By: Ashxn\nType: Technical | Description: Fix permissions to prevent scammers from creating fake support threads | Mentioned By: maximus\nType: Technical | Description: Update dexscreener with correct information | Mentioned By: Kizzah\nType: Technical | Description: Implement token-weighted voting system for DAO | Mentioned By: Uuuuuuuuu\nType: Documentation | Description: Create documentation for V2 features and building process | Mentioned By: OttisOts\nType: Documentation | Description: Post official CA on Twitter to prevent confusion | Mentioned By: jin\nType: Documentation | Description: Update OpenSea profile to clarify V1 NFTs are legacy | Mentioned By: BRANDO // ATS Founder\nType: Feature | Description: Develop system for AI agents to navigate worlds naturally | Mentioned By: Ashxn\nType: Feature | Description: Create mechanism for unclaimed tokens to be added to DAO fund | Mentioned By: Paradoxx\nType: Feature | Description: Implement cross-chain compatibility | Mentioned By: Ashxn\nType: Feature | Description: Develop migration path for V1 worlds to V2 | Mentioned By: metadantes",
      "messageCount": 4564,
      "userCount": 568
    },
    {
      "channelId": "1031058655581323324",
      "channelName": "🧊│3d-design",
      "summary": "# Discord Chat Analysis for 🧊│3d-design Channel\n\n## 1. Summary:\nThe discussion primarily focused on an issue with bone hierarchies in 3D models when imported into Hyperfy. JUAN and 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 discussed a problem where animations were connecting to the hip bone instead of the root bone in Hyperfy, causing incorrect animation behavior. The issue appears inconsistent, affecting some Mixamo and Rokoko animations but not others. They identified that Hyperfy might be misinterpreting bone hierarchies, especially with complex rigs that use control bones or multiple animation layers. 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 mentioned using Rokoko to get animations working properly, but the hip-root connection problem persisted. JUAN suggested using retargeting tools to assign animations to the correct bones. The conversation briefly touched on documentation for Blender integration with Hyperfy, with Ashxn providing a link to the v1 documentation.\n\n## 2. FAQ:\nQ: What issue sounds like it's related to how bone hierarchies or constraints are being handled by Hyperfy? (asked by JUAN) A: The issue where animations connect to hip instead of root bone (answered by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓)\nQ: Any docs on how it works for blender? (asked by Matt [Cheems Guevara]) A: https://docs.hyperfy.io/designers/overview (answered by Ashxn)\n\n## 3. Help Interactions:\nHelper: JUAN | Helpee: 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 | Context: Animations connecting to hip instead of root bone in Hyperfy | Resolution: Suggested the issue might be related to Hyperfy misinterpreting bone hierarchies and recommended using retargeting tools\nHelper: Ashxn | Helpee: Matt [Cheems Guevara] | Context: Request for Blender documentation | Resolution: Provided link to Hyperfy v1 documentation\n\n## 4. Action Items:\nTechnical: Investigate why some animations connect to hip instead of root bone in Hyperfy | Description: Fix inconsistent bone hierarchy interpretation | Mentioned By: 𝕽𝖔𝖚𝖘𝖙𝖆𝖓\nTechnical: Explore creating a one-click solution to fix bone hierarchy issues | Description: Develop tool to correct bone connections | Mentioned By: JUAN\nDocumentation: Update documentation for Blender integration | Description: Ensure current documentation covers bone hierarchy handling | Mentioned By: Matt [Cheems Guevara]\nDocumentation: Document individual object criteria | Description: Create specifications for objects like \"doritos\" | Mentioned By: scoe",
      "messageCount": 34,
      "userCount": 7
    },
    {
      "channelId": "999870741069692958",
      "channelName": "🌆│share",
      "summary": "# Analysis of Discord Channel \"🌆│share\"\n\n## 1. Summary\nThis channel appears to be primarily used for sharing content related to Hyperfy, including Twitter/X posts, personal projects, and articles. The discussions highlight enthusiasm for Hyperfy 2.0 and its React SDK capabilities. Users share links to their own content or interesting posts about Hyperfy's development and potential. There is mention of the React SDK enabling extensive scripting possibilities and interoperability between metaverses. Several users shared Twitter threads explaining Hyperfy's journey and capabilities. There was minimal technical problem-solving in this segment, with content being mostly promotional or informational in nature. One user mentioned completing a parkour map and asked for more, suggesting some gaming content exists within Hyperfy. There was also a brief mention of a token launch with a linked article.\n\n## 2. FAQ\nQ: Do you have more parkour maps? (asked by Jay_kaying) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nFeature: Consider restoring the #random channel for off-topic discussions | Mentioned By: maximus\nDocumentation: Create comprehensive guides about Hyperfy's capabilities and React SDK | Mentioned By: labmgr",
      "messageCount": 20,
      "userCount": 12
    },
    {
      "channelId": "1022421054582423562",
      "channelName": "🐞│issues",
      "summary": "# Analysis of 🐞│issues Discord Channel\n\n## 1. Summary\nThe Discord chat primarily revolves around users experiencing issues with claiming an airdrop of Hyperfy tokens. The airdrop was available to Hyperfy World NFT holders (snapshot taken December 7th) and ai16z partners. The claiming process required users to register their Ethereum wallet (which held the NFT during snapshot) and link it to a Solana wallet at hyperfy.io/airdrop, then wait approximately 24 hours for the registration to be processed before claiming at hyperfy.xyz/claim. \n\nMany users encountered the \"wallet not eligible\" error after registration, which moderators explained was due to the delay in transferring registration data to the claim site. Users were advised to be patient and wait for the next batch update. Some users faced technical challenges with specific wallet types - particularly smart wallets like Argent vaults and Gnosis Safe wallets had difficulty with the signature process. Mobile users, especially on iOS, reported problems with the claim page not loading properly.\n\nA notable edge case involved users who had their NFTs stolen, where the team explained that only the current NFT owner could claim the airdrop. The team also clarified that Coinbase wallets were problematic for claiming, though one user eventually found a workaround. Throughout the conversation, moderators (particularly maximus and ash) provided consistent support, checking wallet eligibility, explaining the process, and coordinating with developers to resolve issues.\n\n## 2. FAQ\nQ: Why does the claim site say \"wallet not eligible\" after I registered my SOL address? (asked by multiple users) A: It takes approximately 24 hours for registration data to be transferred to the claim site. The team processes these in batches. (answered by maximus)\nQ: Is there a deadline for claiming the airdrop? (asked by itzler) A: The deadline was removed, so everyone who registers will be able to claim their tokens. (answered by maximus)\nQ: How much did people get per world? (asked by wind) A: 150k coins per world, worth approximately $20k+ USD. (answered by VTATV)\nQ: Can I claim the airdrop if I just purchased a Hyperfy World NFT? (asked by AN0610-Pirate) A: No, the snapshot was taken in December, so new NFT holders are not eligible. (answered by maximus)\nQ: What should I do if I'm having trouble claiming on mobile? (asked by Srile) A: Try using a desktop/laptop instead as mobile may have issues. (answered by maximus)\nQ: Can I claim if my World NFT is in a smart wallet like Argent or Gnosis Safe? (asked by heatherundertheweather) A: This is a challenging edge case that the team is working to resolve. (answered by ash)\nQ: What if my World NFT was stolen? Can I still claim? (asked by MasonMcFly0x♦) A: Unfortunately, only the current owner of the NFT can claim, though there might be potential for recourse through the DAO in the future. (answered by maximus)\nQ: Do I need SOL for gas to claim? (asked by Canessa) A: Yes, you need some SOL in your wallet for the transaction. (confirmed by Canessa)\nQ: Can I use a Coinbase wallet to claim? (asked by VTATV) A: The team advised against using Coinbase wallets, though one user found a workaround. (answered by ash)\nQ: Will worlds created in v1 function in v2? (asked by AcidManhattan) A: No, v1 will be left as is, and v2 will be a new platform that won't port old worlds. (answered by maximus)\n\n## 3. Help Interactions\nHelper: maximus | Helpee: zfko | Context: User's airdrop claim failed | Resolution: User resolved the issue by adding more gas to their wallet\nHelper: maximus | Helpee: Srile | Context: User getting an error while trying to claim with Phantom wallet on mobile | Resolution: Suggested trying on desktop/laptop instead of mobile\nHelper: maximus | Helpee: Deleted User | Context: User couldn't find the claim site | Resolution: Provided the correct link (hyperfy.xyz/claim) and explained the process\nHelper: maximus | Helpee: TheMattEmpire | Context: User encountered a red error when claiming | Resolution: User found solution by checking Console in Developer Tools, identifying a timeout error, and refreshing the page\nHelper: maximus | Helpee: VTATV | Context: User couldn't claim with Coinbase wallet | Resolution: User eventually figured out a workaround to claim with their Coinbase wallet\nHelper: Kronos | Helpee: sherrybeary | Context: User couldn't connect through ETH address after linking to SOL | Resolution: Explained that Brave browser has issues and suggested using Chrome instead\nHelper: maximus | Helpee: AcidManhattan | Context: User lost building changes | Resolution: Explained that there is no auto-save and user needs to manually save changes\n\n## 4. Action Items\nTechnical: Fix issues with smart wallets (Argent, Gnosis Safe) during registration process | Description: Users with smart wallets cannot complete the signature step | Mentioned By: heatherundertheweather, PabloFM | Numinia\nTechnical: Improve mobile experience for claiming | Description: Users on mobile devices (especially iOS) cannot load the claim page properly | Mentioned By: KamX, Lau\nTechnical: Fix Dexscreener market cap information | Description: Market cap information on Dexscreener needs correction | Mentioned By: Kizzah\nTechnical: Implement auto-save functionality for world building | Description: Users lose their work when they forget to manually save | Mentioned By: AcidManhattan\nTechnical: Resolve browser compatibility issues | Description: Brave browser has problems with wallet connections after linking ETH to SOL | Mentioned By: KronosLuxx\nDocumentation: Create guide for importing GLB files | Description: Best practices for importing 3D models to optimize performance | Mentioned By: AcidManhattan\nDocumentation: Clarify the airdrop claiming process | Description: Provide clearer instructions about registration, waiting period, and claiming | Mentioned By: multiple users\nFeature: Implement DAO infrastructure for voting | Description: Enable community governance for addressing issues like stolen NFTs | Mentioned By: maximus\nFeature: Improve performance on iOS | Description: Users can't load worlds at all on iOS | Mentioned By: cwe\nFeature: Develop mechanism to reward builders in v2 | Description: Create a system to recognize and reward active builders | Mentioned By: maximus",
      "messageCount": 482,
      "userCount": 65
    },
    {
      "channelId": "958214956426350652",
      "channelName": "📣│announcements",
      "summary": "# Analysis of 📣│announcements Channel\n\n## 1. Summary\nThe announcements channel contains three critical messages from a user named \"ash\" regarding NFT-related matters. First, ash notified users who linked their SOL addresses late that they can now claim their assets. Second, ash warned about impersonation attempts in direct messages. The most significant announcement clarified that Hyperfy World NFTs are no longer mintable from the website, with all links removed from Discord and updated descriptions on OpenSea. The announcement emphasized that future utility for these NFTs is not guaranteed and warned that minting directly from the contract would be pointless despite the absence of a pause mechanism in the contract.\n\n## 2. FAQ\nQ: Can users who linked their SOL addresses late claim now? (implied question) A: Yes, they should be able to claim now. (answered by ash)\nQ: Is someone impersonating ash in DMs? (implied question) A: Yes, users should be careful about who they speak to in DMs. (answered by ash)\nQ: Can Hyperfy World NFTs still be minted? (implied question) A: No, they are no longer mintable from the website. (answered by ash)\nQ: Is future utility guaranteed for Hyperfy World NFTs? (implied question) A: No, future utility for these NFTs is not guaranteed. (answered by ash)\nQ: Can users mint directly from the contract? (implied question) A: While technically possible (no pause mechanism), it would be pointless. (answered by ash)\n\n## 3. Help Interactions\nHelper: ash | Helpee: Users with late SOL address linking | Context: Users who linked their SOL addresses late needed to claim | Resolution: Notification that claiming is now possible\n\n## 4. Action Items\nTechnical: None explicitly mentioned\nDocumentation: Description: Update OpenSea descriptions for Hyperfy World NFTs | Mentioned By: ash (already completed)\nFeature: None explicitly mentioned",
      "messageCount": 3,
      "userCount": 1
    }
  ]
}