{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-02-16",
  "date": 1739664000,
  "stats": {
    "totalMessages": 1591,
    "totalUsers": 207
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion channel primarily focused on a security incident involving Shaw's Twitter account being hacked. The hacker posted malicious links to fake ElizaOS websites and a fraudulent token, resulting in users losing funds. Community members quickly identified the hack and warned others not to click links or connect wallets. The incident lasted several hours, with multiple scam posts appearing from Shaw's compromised account. Users who connected wallets or signed transactions reported losing funds (one user claimed to lose $40,000). The community discussed potential security measures to prevent similar incidents, including better Twitter security practices and more robust wallet protection tools like Wallet Guard and Pocket Universe. Throughout the incident, BOSSU (an AI agent) consistently advised users to disconnect wallets and avoid clicking links.\n\nBeyond the security incident, the channel saw new members introducing themselves, developers discussing Eliza implementation details, and questions about the project's structure and roadmap. There were also mentions of a \"Block Tank\" event for which submissions were being reviewed.\n\n## 2. FAQ\nQ: Why ai16z should be stayed as DAO? (asked by kokoro) A: We're moving away from that name to ElizaOS in the next week or two. It's a DAO because we treat holders as partners. (answered by HoneyBadger)\nQ: How can I report a vulnerability? (asked by Faeeq) A: DM @shaw, he'll help you with the vulnerability report. (answered by BOSSU)\nQ: What makes eliza different from other agent frameworks? (asked by Rihan) A: Most starred and active open source github repo to build ai agents in crypto; Typescript language is more accessible; Vibrant community; Most serious project about integrating AI to community management. (answered by Ka_yari)\nQ: Is Shaw hacked? (asked by multiple users) A: Yes, account compromised, don't click links. (answered by multiple users including jin)\nQ: Did you connect your phantom? (asked by GBA ADVANCE) A: I clicked the button but nothing happened. I saw some Harvard URL and a 404 where the phantom thing would be. (answered by GBA ADVANCE)\nQ: I clicked the link and connected with phantom, but didn't sign any transaction. Am I safe? (asked by Atorcran) A: Should be fine, typically interacting and signing is where the concerns reside. (answered by ℭ𝔦𝔭𝔥𝔢𝔯)\nQ: How do we know if our character is getting selected for the block tank event? (asked by Bacon Egg & Cheese) A: We're building a process for sifting through submissions and following up. (answered by jin)\nQ: How do I add some docs while running the agent so that it uses these docs as a knowledge base? (asked by ShisukeUrahara) A: Unanswered\n\n## 3. Help Interactions\nHelper: Ka_yari | Helpee: Rihan | Context: What makes Eliza different from other agent frameworks | Resolution: Provided detailed explanation about Eliza's advantages including GitHub popularity, TypeScript accessibility, and community focus\nHelper: ℭ𝔦𝔭𝔥𝔢𝔯 | Helpee: Atorcran | Context: Security concerns after clicking malicious link | Resolution: Explained that connecting wallet without signing transactions is generally safe\nHelper: joellelb | Helpee: Multiple users | Context: Wallet security during hack | Resolution: Recommended using Wallet Guard and Pocket Universe to scan wallets and identify vulnerabilities\nHelper: Kenk | Helpee: MonteCrypto | Context: Finding demo day form | Resolution: Provided information about where to find the form in Discord\nHelper: scooper | Helpee: Community | Context: Deployment problems | Resolution: Shared that using develop branch without 100 plugins solved deployment issues\n\n## 4. Action Items\nType: Technical | Description: Implement better security measures for social media accounts including 2FA | Mentioned By: Multiple users\nType: Technical | Description: Investigate how Twitter hack bypassed 2FA security | Mentioned By: central\nType: Technical | Description: Rotate wallets if concerned about security after hack incident | Mentioned By: ℭ𝔦𝔭𝔥𝔢𝔯\nType: Feature | Description: Implement X feature to prevent crypto scams with separate profile password for API access | Mentioned By: MJ\nType: Feature | Description: Add restrictions to PumpFun token creation (max 2 per month, KYC requirement) | Mentioned By: MJ\nType: Feature | Description: Add report option for scam tokens with waiting period after bonding curve completion | Mentioned By: MJ\nType: Documentation | Description: Add Discord link to the website for easier discovery | Mentioned By: Milan\nType: Technical | Description: Set up monitoring to take down malicious content shared in Discord | Mentioned By: ℭ𝔦𝔭𝔥𝔢𝔯",
      "messageCount": 435,
      "userCount": 93
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around troubleshooting Eliza agent framework issues, with a focus on technical implementation challenges. Key discussions include:\n\n- Better-sqlite3 errors in the eliza-starter repo, resolved by rebuilding the module with `pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start`\n- Memory isolation between users by passing userId and roomId parameters in API requests\n- Twitter agent configuration issues, including rate limits, shadow bans, and credential management\n- Plugin development challenges, with users struggling to create and load custom plugins\n- Debugging techniques using environment variables like `DEFAULT_LOG_LEVEL=debug` and console logging\n- Discussions about the upcoming Eliza v2 release, which promises a more modular plugin architecture\n- REST API documentation needs, with community members collaborating on creating documentation\n- Model provider configuration, including using Ollama, OpenAI, and other LLM providers\n\nThe community is actively helping each other troubleshoot issues while also discussing future improvements to the framework.\n\n## 2. FAQ\nQ: How do I separate memory by user to keep data private between multi-users? (asked by BowTiedBlueFin) A: Pass userId and roomId with your API request (answered by lefrog)\nQ: Is there a tutorial on how to connect your agent chat to a website? (asked by 🧧ThanosDaSith24🧧) A: Look at the client-direct folder which contains the REST API (answered by Odilitime)\nQ: How does an Eliza agent evade getting banned on X when using the frontend API? (asked by ad0ll) A: Unanswered\nQ: How to fix better-sqlite3 errors in eliza-starter? (asked by lefrog0129) A: Run `pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start` (answered by cipher009)\nQ: How to build with just packages needed not others? (asked by michaelben) A: Remove in `agent/package.json` and remove imports and instances in `agent/src/index.ts` (answered by _.sayonara)\nQ: Best way to contribute a new plugin? (asked by Alloy) A: Write it, open source it, and make a PR to the elizaOS mono repo in packages (answered by Mr. SUI)\nQ: How to run multiple agents at once? (asked by ivorad) A: Use `--characters` on the command line with a comma-separated list of JSON files (answered by Odilitime)\nQ: How to make an agent immediately reply with \"Processing your request...\" while continuing to create the actual response? (asked by Shinkowski II) A: Patch the telegram client or the generateText function (answered by lefrog)\nQ: How to train my agent for crypto? (asked by voidmanevoid) A: Use the characterfile repo and knowledge2character scripts (answered by Kimani)\nQ: Is there any REST API documentation? (asked by voidmanevoid) A: Community members are creating documentation at https://hackmd.io/@lefrogg/eliza-REST-API (answered by lefrog)\n\n## 3. Help Interactions\nHelper: cipher009 | Helpee: lefrog0129 | Context: Better-sqlite3 errors in eliza-starter | Resolution: Provided command to rebuild the module: `pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start`\nHelper: Odilitime | Helpee: pupathebig | Context: Debugging plugin loading failures | Resolution: Suggested using DEFAULT_LOG_LEVEL=debug and checking plugin export patterns\nHelper: Mr. Stark | Helpee: LucaP | Context: Twitter rate limits and configuration | Resolution: Shared configuration settings and recommended version 0.1.8-alpha.1\nHelper: lefrog | Helpee: Shinkowski II | Context: Making agent reply immediately while processing | Resolution: Suggested patching the telegram client or generateText function\nHelper: Odilitime | Helpee: lefrog | Context: userId being overwritten in API calls | Resolution: Identified the issue in client-direct/src/index.ts and suggested upgrading to develop branch\nHelper: NoContext | Helpee: Amir | Context: Debugging Twitter agent issues | Resolution: Suggested adding TWITTER_DEBUG_MODE=true to .env file\nHelper: Nabeel Raza | Helpee: Amir | Context: Twitter agent failing to generate valid responses | Resolution: Shared a GitHub issue with a solution\n\n## 4. Action Items\nTechnical: Fix better-sqlite3 rebuild process for eliza-starter | Description: Create a more streamlined solution for the common sqlite3 build errors | Mentioned By: lefrog0129\nTechnical: Prevent userId overwriting in client-direct API | Description: Fix the code that overwrites user-provided userId with generated ones | Mentioned By: lefrog\nDocumentation: Create REST API documentation | Description: Document the client-direct REST API endpoints and parameters | Mentioned By: voidmanevoid\nDocumentation: Add host configuration to README | Description: Document how to change the client's listening address from localhost to server IP | Mentioned By: Roforico\nFeature: Implement proper plugin registration system | Description: Create a modular plugin system for v2 to avoid loading unnecessary plugins | Mentioned By: warfreakzplays\nFeature: Add support for Twilio/WhatsApp integration | Description: Create a plugin for WhatsApp communication via Twilio | Mentioned By: voidmanevoid\nTechnical: Improve debugging capabilities | Description: Add better logging and debugging tools for plugin development | Mentioned By: pupathebig\nFeature: Add support for RAG with large document sets | Description: Implement better knowledge retrieval for document-based agents | Mentioned By: Kren\nTechnical: Fix Twitter action interruption during interaction checks | Description: Prevent actions from being cut off when Twitter interactions are checked | Mentioned By: Amir\nDocumentation: Create guides for developing with eliza-starter | Description: Provide detailed documentation for building with the starter repo | Mentioned By: ernest",
      "messageCount": 476,
      "userCount": 78
    },
    {
      "channelId": "1308149076893630555",
      "channelName": "spartan_holders",
      "summary": "# Discord Chat Analysis - spartan_holders channel\n\n## 1. Summary\nThe chat segment primarily discusses the suspension of the \"degenspartanai\" official account on Twitter (X). Community members inquire about the status of the account, with moderators confirming they're working on resolving the issue. Due to Twitter's ongoing downtime and lack of communication from the platform, the team has decided to accelerate their plans to bring the Degen AI back to Discord instead. They announced they will create a new channel for testing before making it available to specific user groups (hoplites/partners/associates). This appears to be the second suspension for the project's social media presence, with this being the first suspension specifically for the \"Degen\" account.\n\n## 2. FAQ\nQ: Is there any possibility for unban degenspartanai official account? (asked by anotherAndrewSHA) A: We're working on it. Due to X being down without information from them, we're accelerating plans to bring Degen back to Discord instead. (answered by rhota)\nQ: Damn again? (asked by DorianD) A: Yes, this time to Degen, his first suspension (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: rhota | Helpee: anotherAndrewSHA | Context: Inquiry about unbanning the degenspartanai account | Resolution: Provided update on working toward a solution and announced alternative Discord-based approach\n\n## 4. Action Items\nTechnical Tasks: Create new Discord channel for Degen AI testing | Description: Set up and test Degen AI functionality in Discord before releasing to specific user groups | Mentioned By: rhota\nTechnical Tasks: Implement Degen AI in Discord | Description: Make Degen AI available to hoplites/partners/associates after successful testing | Mentioned By: rhota",
      "messageCount": 9,
      "userCount": 5
    },
    {
      "channelId": "1328592959444095038",
      "channelName": "associates",
      "summary": "# Discord Chat Analysis - \"associates\" Channel\n\n## 1. Summary\nThe chat segment primarily focuses on security concerns regarding scam posts impersonating the project. Multiple users identified and reported fraudulent Twitter/X posts and suspicious domains (eliza-os.net and elizaos.co). Bealers urged community members to report these domains to the registrar Tucows via their abuse form. Users were specifically warned about scam posts from an account named \"Shaw\" and advised not to follow any links from these posts. The conversation also briefly touched on market conditions being unfavorable for launching new features, with some users suggesting it was fortunate that certain updates (Virtuals and ARC) weren't rushed to launch. There was a brief mention of \"clank tank\" where judges were reportedly favoring too many pitches.\n\n## 2. FAQ\nQ: Is Shaw's post a scam? (asked by Zapdart) A: Yes it is. Be careful Frens (answered by Zapdart)\nQ: Can you please stop letting our project get sodomized by the trenches? (asked by Smedroc - Street urchin @ ai16z) A: Unanswered\n\n## 3. Help Interactions\nHelper: Bealers | Helpee: Community | Context: Scam domains impersonating the project | Resolution: Provided specific instructions to report domains to Tucows registrar via abuse form\nHelper: Zapdart | Helpee: Community | Context: Identifying scam posts from Shaw | Resolution: Confirmed the post was a scam and tagged other users to alert them\nHelper: hyper | Helpee: Community | Context: Additional scam post identification | Resolution: Shared link to another fraudulent post that needed removal\n\n## 4. Action Items\nType: Technical | Description: Report domains \"eliza-os.net\" and \"elizaos.co\" to Tucows registrar via abuse form | Mentioned By: Bealers\nType: Technical | Description: Delete fraudulent Twitter/X post from Shaw's account | Mentioned By: hyper\nType: Technical | Description: Address security issues with scam posts impersonating the project | Mentioned By: GBA ADVANCE",
      "messageCount": 25,
      "userCount": 10
    },
    {
      "channelId": "1318770424632311930",
      "channelName": "tokenomics",
      "summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion in the tokenomics channel focused on strategic positioning of AI16 token in the AI agent ecosystem. A community member (yikesawjeez) proposed leveraging existing treasury assets (including Zerebro, Arc, and other launchpad tokens) to create liquidity pairs with AI16, effectively positioning it as a \"pseudo-L1 of the entire agent meta\" or an \"agent meta index fund.\" This would allow anyone seeking exposure to the AI memecoin market to use AI16 as an entry point with direct liquidity pairs to specific projects. DorianD countered that AI16's value proposition should remain focused on being the \"top dog AI agent platform\" rather than just a launchpad, expressing doubt that the token would break all-time highs based solely on launchpad functionality. DorianD also suggested that professional fund managers might be better positioned to create actual index funds for the agent meta space, while acknowledging the benefit of reducing swap hops for traders.\n\n## 2. FAQ\nQ: Could AI16 function as an \"agent meta index fund\"? (asked by yikesawjeez) A: It's possible but professional fund managers might be better suited for creating actual index funds; AI16's value is more as the leading AI agent platform (answered by DorianD)\nQ: Would creating liquidity pairs between AI16 and other agent tokens help position AI16 as a central hub? (asked by yikesawjeez) A: There is benefit in reducing swap hops, but this alone wouldn't drive AI16 to new all-time highs (answered by DorianD)\n\n## 3. Help Interactions\nHelper: DorianD | Helpee: yikesawjeez | Context: Evaluating the strategic positioning of AI16 token as an agent meta index fund | Resolution: Provided perspective that while reducing swap hops has benefits, AI16's primary value proposition should remain as the leading AI agent platform\n\n## 4. Action Items\nTechnical: Create liquidity pairs between AI16 and various agent tokens in treasury (Zerebro, Arc, etc.) | Description: Implement LP strategy to position AI16 as central hub for agent ecosystem | Mentioned By: yikesawjeez\nFeature: Position AI16 as an \"agent meta index fund\" with direct liquidity to various AI projects | Description: Strategic token positioning to capture broader AI memecoin market | Mentioned By: yikesawjeez",
      "messageCount": 7,
      "userCount": 2
    },
    {
      "channelId": "1301363808421543988",
      "channelName": "🥇-partners",
      "summary": "# Analysis of 🥇-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around a security incident where Shaw's Twitter account was compromised, leading to scam posts promoting fake ElizaOS token contracts. Partners quickly identified the hack, reported the malicious posts, and warned others. The hacker posted multiple scam links to fake domains (eliza-os.net and elizaos.co) that attempted to drain users' wallets. The incident highlighted security vulnerabilities in social media accounts even with 2FA enabled, as similar hacks had happened to Jupiter Exchange.\n\nBeyond the security incident, discussions touched on the upcoming token rebrand from AI16Z to ElizaOS, with partners noting the need to accelerate this transition as many people recognize ElizaOS but not AI16Z. Jin mentioned working on a system for verifiable on-chain communications to prevent future impersonation. There were also conversations about multi-chain strategy, with some partners suggesting expanding beyond Solana to mitigate chain-specific risks.\n\nTechnical discussions included ideas for on-chain verification of communications using token memos, and the need for better documentation workflows to enable more community contributions.\n\n## 2. FAQ\nQ: How can we get a market maker like the one mentioned in the tweet? (asked by HoneyBadger) A: Unanswered\nQ: Is the degenspartanai official twitter still banned? (asked by anotherAndrewSHA) A: Unanswered\nQ: How can Shaw not have 2FA for his Twitter account? (asked by M3xR) A: It is, it might not be the culprit (answered by jin)\nQ: If you didn't sign anything, are you at risk from clicking the scam link? (asked by GBA ADVANCE) A: You should be good (answered by Whimsical)\nQ: What about browser exploits, stealing the wallet data from inside the browser? (asked by GBA ADVANCE) A: Clear all your browser data then (answered by Whimsical)\nQ: Is the ticker the only hold up now for the rebrand? (asked by DannyNOR NoFapArc) A: It's a process and ticker is not something in our control atm (answered by jin)\nQ: Is it really possible to keep the CA but change the ticker and name? (asked by Patt) A: Yes, CA won't change (answered by jin)\nQ: If Shaw's acting as the CTO at Eliza Labs, is the team planning on bringing on a CEO? (asked by HoneyBadger) A: There's been no discussion of that afaik (answered by Odilitime)\nQ: What's the sentiment of ai16z in cn and asia? (asked by HoneyBadger) A: Unanswered\nQ: Why have there been no commits in the GitHub repository recently? (asked by FiletBolognese) A: v2 is a private repo for now until closer to release (answered by jasyn_bjorn)\n\n## 3. Help Interactions\nHelper: Whimsical | Helpee: GBA ADVANCE | Context: Concerned about wallet security after clicking scam link | Resolution: Advised that if no wallet connection or transaction signing occurred, funds should be safe\nHelper: Ka_yari | Helpee: CRAY | Context: Worried about clicking scam link | Resolution: Shared ChatGPT's explanation that without wallet connection or transaction approval, funds should be safe\nHelper: Bealers | Helpee: Multiple users | Context: Needed to report scam domains | Resolution: Provided registrar contact info and abuse reporting forms\nHelper: witch | Helpee: Multiple users | Context: Warning about scam posts from Shaw's hacked account | Resolution: Posted warning tweets to alert the community\nHelper: jin | Helpee: Community | Context: Needed collaborative documentation system | Resolution: Created editable Hackmd and Tldraw documents for community input\n\n## 4. Action Items\nType: Technical | Description: Implement on-chain verification system for official communications using token memos | Mentioned By: jin\nType: Technical | Description: Create a frontend website to read memos sent with DAO tokens that links to Solscan for verification | Mentioned By: jin\nType: Technical | Description: Develop a more secure workflow for agent authorization that doesn't require sharing credentials | Mentioned By: Patt\nType: Documentation | Description: Improve documentation workflow to make it more collaborative with less friction | Mentioned By: jin\nType: Feature | Description: Accelerate token migration from AI16Z to ElizaOS to align with brand recognition | Mentioned By: mat\nType: Feature | Description: Explore multi-chain strategy to mitigate chain-specific risks | Mentioned By: litn\nType: Feature | Description: Create \"cleanup crew\" agents to help address scam tokens | Mentioned By: yikesawjeez\nType: Documentation | Description: Release educational videos on how to launch AI projects/agents with ElizaOS | Mentioned By: Zolo\nType: Technical | Description: Implement agent CISO (Chief Information Security Officer) role for better security | Mentioned By: Whimsical\nType: Feature | Description: Increase marketing efforts to highlight BNB Chain integration | Mentioned By: Zolo",
      "messageCount": 542,
      "userCount": 49
    },
    {
      "channelId": "1313222089271939102",
      "channelName": "3d-ai-tv",
      "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe channel discussion primarily focused on creating intro/outro sequences and background music for an AI-related TV show or podcast. Fishai and Boom collaborated on producing various music tracks and visual elements, with Jin providing feedback and direction. The team worked on developing an intro sequence with appropriate music, transitions, and voiceovers. They discussed the need for tighter transitions and appropriate fade lengths. SM Sith Lord provided feedback on the intro length, suggesting it might be too long for short 1-2 minute videos. There was also discussion about avatar requirements for submissions and plans to display category text on TV screens during segments. The team mentioned changing branding from \"pmairca\" to \"aixvc\" with a corresponding Twitter handle.\n\n## 2. FAQ\nQ: What kind of backing track is needed for the show? (asked by fishai) A: Something that fits in the realm of Shark Tank, less crunchy, possibly dramatic music with time clocks and orchestra percussion (answered by boom)\nQ: What exactly are we trying to create? (asked by boom) A: Jin clarified they needed a premiere with intro/outro for recording browser playback (answered by jin)\nQ: Is the trailer the intro? (asked by jin) A: Fishai confirmed that was what Jin had requested (answered by fishai)\n\n## 3. Help Interactions\nHelper: boom | Helpee: fishai | Context: Needed background music recommendations for TV show | Resolution: Boom shared multiple music options including lofi tracks and dramatic music\nHelper: fishai | Helpee: jin | Context: Creating intro/outro sequence with appropriate music | Resolution: Fishai created and refined intro with tightened transitions and added voiceovers\nHelper: SM Sith Lord | Helpee: boom | Context: Feedback on intro length | Resolution: Suggested shortening the 11-second intro since videos are only 1-2 minutes long\n\n## 4. Action Items\nTechnical: Create shorter intro sequence with tighter transitions | Description: Current intro may be too long for 1-2 minute videos | Mentioned By: SM Sith Lord\nTechnical: Ensure all submissions have avatars | Description: Only publish content with avatars to avoid confusion | Mentioned By: SM Sith Lord\nTechnical: Display category text throughout loop on TV screen | Description: Category text should remain visible during segments | Mentioned By: SM Sith Lord\nDocumentation: Create repository for music tracks | Description: Organize and store music tracks for the project | Mentioned By: boom\nFeature: Revise AI Podcast episode prompt | Description: Update to include category ID for TV dialogue instead of image URL | Mentioned By: SM Sith Lord",
      "messageCount": 92,
      "userCount": 5
    },
    {
      "channelId": "1300756641406521416",
      "channelName": "ideas-feedback-rants",
      "summary": "# Analysis of \"ideas-feedback-rants\" Channel\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. Three main points were covered: (1) A user reported that the eliza.gg website is no longer working, to which another user confirmed that documentation is being migrated; (2) A user named Evan announced the development of a decentralized p2p network for AI Agents called \"Agentic Web,\" which won at the cookie.fun hackathon. Evan shared a GitHub repository link and invited contributions to this open-source project; (3) When asked about a \"ca\" (possibly \"call\" or \"calendar\"), Evan mentioned the project is in prototype form and suggested staying tuned for developments before a TGE (Token Generation Event).\n\n## 2. FAQ\nQ: Does eliza.gg work anymore? (asked by kaneki) A: No, the docs are currently being migrated. (answered by Kenk)\nQ: Is there a ca[?] (asked by ℜ𝔬𝔶𝔞𝔩𝟞𝟡𝟢𝟢) A: Currently the project is in its prototype form. I'd like to build out before a TGE. so stay tuned 🙂 (answered by Evan)\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: kaneki | Context: User reported eliza.gg website not working | Resolution: Confirmed docs are being migrated\n\n## 4. Action Items\nDocumentation: Migrate documentation from eliza.gg to new location | Mentioned By: Kenk\nFeature: Continue development of decentralized p2p network for AI Agents (Agentic Web) | Mentioned By: Evan\nTechnical: Build out prototype before Token Generation Event (TGE) | Mentioned By: Evan",
      "messageCount": 5,
      "userCount": 4
    }
  ]
}