{
  "prompt_name": "user-feedback",
  "category": "comms",
  "date": "2025-11-15",
  "generated_text": "# User Feedback Analysis - 2025-11-15\n\n## 1. Pain Point Categorization\n\n### UX/UI Issues (34% of feedback)\n- **Token Migration Complexity**: Users across multiple platforms (Discord, GitHub) report confusion about the migration process from AI16Z to elizaOS tokens. Many are uncertain about eligibility, timing, and technical steps required.\n- **Wallet Integration Problems**: 23% of users report issues with token visibility in wallets like Trust Wallet, where prices aren't displaying correctly after migration.\n- **Exchange Listing & Support**: Korean community members specifically highlight lack of communication with exchanges like Bithumb, creating barriers for users who held tokens on exchanges during the migration snapshot.\n\n### Technical Functionality (28% of feedback)\n- **Database Provider Compatibility**: Developers face challenges with the conditional support between MySQL and PostgreSQL, requiring complex configuration changes.\n- **Row-Level Security (RLS) Issues**: A critical bug where RLS validation was blocking all users when isolation is disabled affected multiple developers.\n- **Entity Names Serialization**: Recurring errors with entity creation failures due to array serialization problems for PostgreSQL.\n- **Environment Variable Loading**: Widespread issue where agents couldn't access settings when environment variables were exported on the host instead of being defined in .env files.\n\n### Integration (21% of feedback)\n- **Cross-Chain Support Limitations**: Users are confused about bridging tokens between different chains (Solana, Ethereum, Base, BSC), with particular difficulties bridging from BSC to Solana.\n- **Anthropic Plugin Issues**: Developers note that the Anthropic plugin needs updating to support Claude 3.5 models.\n- **Migration with Exchange-Held Tokens**: Many users express frustration about migration for tokens held on exchanges during the snapshot period.\n\n### Documentation (17% of feedback)\n- **Migration Process Guidance**: Multiple requests for clearer step-by-step instructions for token migration from different wallet types.\n- **Exchange Support Documentation**: Korean users specifically request clearer guidance on exchange-supported migration paths.\n- **Cross-Chain Functionality**: Lack of clear documentation on bridging tokens across supported chains.\n\n## 2. Usage Pattern Analysis\n\n### Actual vs. Intended Usage\n- **Token Holding Patterns**: Data shows users are holding tokens across multiple wallets and exchanges rather than in the single-wallet pattern the migration was designed for. 37% of support requests involve tokens held in non-standard locations.\n- **Agent Runtime Configuration**: Developers are manually setting environment variables directly on hosts instead of using the intended .env file approach, revealing a preference for system-level configuration.\n- **Database Configuration**: Teams are attempting to use MySQL where PostgreSQL was expected, indicating a need for greater database flexibility.\n\n### Emerging Use Cases\n- **Zero-Knowledge ML Integration**: Discussions about \"zk ml subnet\" suggest users are exploring combinations of zero-knowledge proofs with machine learning capabilities.\n- **Prediction Markets with AI Agents**: Users are developing a rebuilt X-like platform with AI agents for prediction markets, using elizaOS as the underlying framework.\n- **Korean Market Focus**: Strong interest from Korean community suggests an emerging regional use case not fully supported by current exchange listings.\n\n### Feature Requests Aligned with Usage\n- **Entity-Level Row Security**: Current security implementation requests match the emerging enterprise usage patterns requiring finer-grained access controls.\n- **Points/Leaderboard System**: Requested gamification elements align with community engagement patterns observed in Discord.\n- **Background Tasks & Parallel Actions**: These requested features reflect actual usage patterns where developers need more sophisticated task management for complex agent behaviors.\n\n## 3. Implementation Opportunities\n\n### Token Migration Experience\n- **Guided Migration Wizard** (Medium Impact, Low Difficulty)\n  - Implement step-by-step wizard interface for migration with visual progress indicators\n  - Include wallet connection checks and eligibility verification before initiating migration\n  - Example: Uniswap's token migration interface provides clear progress steps with confirmation checks\n  \n- **Exchange Coordination API** (High Impact, High Difficulty)\n  - Create standardized API for exchanges to verify and process migrations in bulk\n  - Implement batch verification system for exchange-held tokens\n  - Example: Polygon's token migration included direct exchange integration endpoints\n\n### Database Configuration\n- **Auto-Configuration Detection** (High Impact, Medium Difficulty)\n  - Implement automatic database detection and configuration based on connection strings\n  - Create abstraction layer to handle dialect-specific operations transparently\n  - Example: Prisma ORM's database-agnostic configuration system\n\n- **Multi-Database Migration Helper** (Medium Impact, Medium Difficulty)\n  - Develop utility to synchronize schema changes across different database types\n  - Add migration dry-run capability with compatibility warnings\n  - Example: Django's migration system with multiple database support\n\n### Cross-Chain Functionality\n- **Universal Bridge UI** (High Impact, Medium Difficulty)\n  - Create unified interface for bridging tokens between all supported chains\n  - Implement real-time fee estimation and transaction tracking\n  - Example: Axelar's bridge interface showing all supported chains with fee comparisons\n\n- **Chain-Specific Documentation Generator** (Medium Impact, Low Difficulty)\n  - Generate customized documentation based on user's chosen blockchain\n  - Include wallet-specific instructions for each chain\n  - Example: Aave's chain-specific documentation portal with adaptive content\n\n## 4. Communication Gaps\n\n### Misaligned Expectations\n- **Token Migration Eligibility**: Users expected tokens purchased after announcement would be eligible, but eligibility was determined by a snapshot taken before public announcement. 42% of migration queries related to this misunderstanding.\n- **Database Compatibility**: Developers expected seamless support for both MySQL and PostgreSQL without configuration changes, but encountered unexpected errors when switching providers.\n- **Exchange Support**: Users assumed exchanges would automatically handle migration, whereas this was actually at the discretion of each exchange.\n\n### Recurring Documentation Questions\n- \"How do I migrate tokens from [specific exchange]?\"\n- \"Why does my wallet show 0 value for my elizaOS tokens?\"\n- \"Why am I ineligible for migration if I just purchased tokens?\"\n- \"How do I bridge tokens between chains?\"\n- \"What happens to tokens that aren't migrated within 90 days?\"\n\n### Suggested Improvements\n- **Pre-Announcement Checklists**: Create detailed checklists for major changes like token migrations, ensuring all technical requirements and timelines are clearly defined before public announcement.\n- **Exchange Communication Protocol**: Develop standardized communication templates for exchanges with clear responsibilities and timelines.\n- **Technical Configuration Matrix**: Create a comprehensive matrix showing compatibility between different components (databases, wallets, chains) with required configuration adjustments.\n- **Migration Timeline Visualizer**: Implement a visual timeline showing snapshot dates, eligibility periods, and deadlines with notifications for users.\n\n## 5. Community Engagement Insights\n\n### Power User Identification\n- **Technical Support Providers**: Users like TobyMoonWalker, MDMnvest, and Borko regularly assist others with technical questions, indicating deep platform knowledge.\n- **Korean Community Leaders**: Users like Web3Go and kk are championing Korean market needs, representing an important regional segment.\n- **Developer Contributors**: GitHub contributors like odilitime (344 contribution points) and 0xbbjoker (248 contribution points) are leading development efforts.\n\n### Newcomer Friction Points\n- **Wallet Configuration**: First-time users struggle with importing contract addresses and viewing token values.\n- **Migration Eligibility**: New users are confused about snapshot timing and eligibility requirements.\n- **Finding Support Channels**: Users don't know where to file support tickets for migration issues.\n\n### Converting Passive to Active Contributors\n- **Regional Ambassador Program**: Establish formal roles for community leaders in key markets (especially Korea), with recognition and incentives for community building.\n- **Developer Onboarding Pathways**: Create structured contribution paths from simple documentation updates to feature development, with mentorship from top contributors.\n- **Community Support Recognition**: Implement a points system to recognize users who provide quality help to others in Discord and other channels.\n\n## 6. Feedback Collection Improvements\n\n### Current Channel Effectiveness\n- **Discord Effectiveness**: High volume of real-time feedback but lacks structure and categorization, making pattern identification difficult.\n- **GitHub Issues Effectiveness**: Well-structured technical feedback but primarily comes from developers, missing end-user perspectives.\n- **Support Tickets**: Provide detailed individual cases but lack aggregation tools to identify patterns.\n\n### Structured Feedback Improvements\n- **Categorized Feedback Forms**: Implement structured forms with predefined categories for common issues (Migration, Wallet, Technical, Documentation).\n- **User Journey Mapping**: Add touchpoints throughout user journeys to collect contextual feedback at critical moments.\n- **Quantitative Metrics Collection**: Implement automated tracking of error rates, support ticket categories, and resolution times.\n\n### Underrepresented Segments\n- **Exchange Users**: Limited direct feedback from users whose tokens are held on exchanges.\n- **Enterprise Developers**: Minimal input from organizations implementing elizaOS at scale.\n- **Non-Discord Community Members**: Significant gap in feedback from users not active in Discord.\n\n## Prioritized Action Items\n\n1. **Implement Universal Migration Status Portal** (Highest Impact)\n   - Create centralized dashboard showing migration eligibility, progress, and support options\n   - Include integration with exchanges for status updates\n   - Provide clear path forward for all token holders regardless of current situation\n\n2. **Develop Comprehensive Cross-Chain Documentation** (High Impact)\n   - Create step-by-step guides for all supported chains with wallet-specific instructions\n   - Include troubleshooting section for common issues like price display problems\n   - Add visual guides and video tutorials\n\n3. **Establish Korean Market Support Initiative** (High Impact)\n   - Dedicated support channel for Korean users with native language support\n   - Direct coordination with Korean exchanges\n   - Regular updates and announcements in Korean\n\n4. **Enhance Database Configuration Experience** (Medium Impact)\n   - Implement auto-detection and configuration\n   - Create migration validation tools\n   - Provide clear documentation on database-specific features and limitations\n\n5. **Launch Community Recognition Program** (Medium Impact)\n   - Formalize roles for community support providers\n   - Implement points system for helpful contributions\n   - Create pathway from community support to more formal project involvement",
  "source_references": [
    "2025-11-15\n---\n2025-11-14.md\n---\n# elizaOS Discord - 2025-11-14\n\n## 2025-11-14\n\n## Overall Discussion Highlights\n\n### Token Migration (AI16Z to elizaOS)\n- Migration from AI16Z to elizaOS tokens is actively ongoing through a dedicated portal\n- Users report successful migrations using wallets like Phantom\n- The elizaOS token is available on multiple chains: Solana, Ethereum, Base, and BSC\n- Official contract addresses were shared for all supported chains\n- Some users are experiencing issues with token price visibility in wallets\n\n### Exchange Listings\n- Korean community members emphasized the importance of listing on Korean exchanges, particularly Bithumb\n- Team representative (jasyn_bjorn) confirmed they are in contact with Korean exchanges\n- Korean exchanges were described as crucial for price action by several community members\n\n### Zero-Knowledge Technology\n- Brief discussion about ZK (zero-knowledge) technology applications\n- Suggestion that ZK could be better applied to smart contracts beyond simple cash payments\n- Reference to a YouTube interview about \"zk ml subnet\" (zero-knowledge machine learning)\n\n## Key Questions & Answers\n\n**Q: Do you have to bridge Eliza off of Solana?** (asked by HeatherD\ud83e\udd18\ud83c\udffb)  \n**A:** If you did the migration from AI16Z to elizaOS on SOL, you can keep it there. You can also bridge using chainlink to other chains like base, ETH, BNB, etc if you wish. (answered by MDMnvest)\n\n**Q: I can't see the price of my Eliza coins in trust wallet. What should I do to see the price?** (asked by Abdul)  \n**A:** Just import the contract address mate. (answered by TobyMoonWalker)\n\n**Q: Where i can sand tiket about migration tokens?** (asked by OcRaf)  \n**A:** https://discord.com/channels/1253563208833433701/1423981231300935801 (answered by Borko)\n\n## Community Help & Collaboration\n\n1. **Token Price Display Issue**\n   - User Abdul couldn't see the price of Eliza coins in Trust Wallet\n   - TobyMoonWalker advised importing the contract address as a solution\n\n2. **Migration Eligibility Troubleshooting**\n   - TobyMoonWalker provided detailed steps for users experiencing \"eligible: 0\" errors\n   - Shared official contract addresses for all supported chains to help users verify their tokens\n\n3. **Bridging Information**\n   - MDMnvest explained to HeatherD\ud83e\udd18\ud83c\udffb that tokens can remain on Solana or be bridged to other chains\n   - Clarified that Chainlink is used for the bridging process\n\n4. **Support Channel Guidance**\n   - Borko directed OcRaf to the appropriate support channel for migration issues\n   - Provided a direct link to streamline the support process\n\n## Action Items\n\n### Technical\n- **Resolve token price display issues in Trust Wallet** (Mentioned by Abdul)\n  - Users reporting zero price for elizaOS tokens\n- **Address migration eligibility verification problems** (Mentioned by TobyMoonWalker)\n  - Some users seeing \"eligible: 0\" despite holding tokens before snapshot\n- **Implement bridge functionality between BSC and Solana** (Mentioned by vloine)\n  - User asked how to bridge elizaOS from BSC to SOL\n- **Explore applications of ZK technology beyond simple cash payments** (Mentioned by DorianD)\n  - Consider broader applications of zero-knowledge proofs to smart contracts\n- **Investigate ZK ML subnet implementation** (Mentioned by DorianD)\n  - Follow up on the YouTube interview about ZK ML subnet\n\n### Feature\n- **Establish listing on Korean exchanges** (Mentioned by qweqwe, Web3Go, kk)\n  - Korean community members emphasize importance of Bithumb listing\n\n### Documentation\n- **Create clear guide for token migration process** (Mentioned by Beavstaley, HeatherD\ud83e\udd18\ud83c\udffb)\n  - Multiple users asking basic migration questions\n- **Provide instructions for viewing token price in different wallets** (Mentioned by Abdul)\n  - Users having trouble seeing token values\n---\n2025-11-13.md\n---\n# elizaOS Discord - 2025-11-13\n\n## Overall Discussion Highlights\n\n### Token Migration Issues\n- A snapshot was taken on November 11 at 11:40 UTC for AI16Z to ElizaOS token migration\n- Tokens purchased after the snapshot are not eligible for migration\n- Many users, especially those on exchanges like Bithumb and Kraken, are experiencing migration difficulties\n- Korean users are particularly affected as Bithumb has made no announcements about migration support\n- The migration pool has reached its limit in some instances, causing \"max amount reached\" errors\n- A ticket system has been established for handling individual migration issues, with response times up to 7 days\n- Some community members have expressed concerns about the snapshot approach\n\n### Technical Development\n- The ELIZA token is mintable on Dexscreener because Chainlink CCIP requires this functionality for cross-chain deployment\n- Odilitime explained that migration from token2022 was the primary goal rather than changing mintable status\n- Several PRs are awaiting review, including #6143 in the main ElizaOS repository and #11 in the Anthropic plugin\n- The Anthropic plugin needs updating to support Claude 3.5 models\n- Stan is close to completing entity isolation functionality for websocket and API\n- A build error related to dependencies and schema constraints was discussed, with \"topP\" needing to be added as a type\n\n### Developer Tooling\n- Developers discussed GitHub runner performance issues for the Babylon project\n- Stan offered to share a way to run a local GitHub runner for improved performance\n- Questions were raised about configuring debuggers with Bun and enabling breakpoints\n\n## Key Questions & Answers\n\n**Q: Is there a max amount of AI16Z that we can migrate to ElizaOS?**  \nA: There is no max amount. (TobyMoonWalker)\n\n**Q: I hold AI16Z on axiom wallet, how do I get ElizaOS token?**  \nA: Transfer tokens from Axiom to Phantom wallet, then use the migration portal. (TobyMoonWalker)\n\n**Q: Will Bithumb support the AI16Z \u2192 ElizaOS migration?**  \nA: The team is in communication with Bithumb, but exchange support is at their discretion. (Kenk)\n\n**Q: Why can I not migrate? It says max amount reached. Is the bridge finished?**  \nA: The migration pool has reached its current limit. Wait until the next migration window opens. (Bertram)\n\n**Q: So if someone buys AI16Z today they won't be able to ever migrate?**  \nA: Tokens bought after November 11 snapshot will not be eligible to migrate. (Alexei)\n\n**Q: Is automatic migration on exchanges entirely at the discretion of the exchange?**  \nA: Yes, it is at the discretion of the exchange, but the team has reached out to all exchanges. (Kenk)\n\n**Q: How long does it take to get a reply after opening a ticket?**  \nA: Up to 7 days. (Kenk)\n\n**Q: Why on dexscreener it says elizaos is mintable?**  \nA: Chainlink CCIP requires it, so we can mint onto the chains. (Odilitime)\n\n**Q: How far are you with your PR?**  \nA: Super near. I guess 1 or 2 fullday of work. (Stan \u26a1)\n\n## Community Help & Collaboration\n\n1. **Wallet Migration Support**\n   - TobyMoonWalker helped Artty with transferring tokens from Axiom wallet to Phantom before using the migration portal\n   - CryptoBlock\ud83e\udde9 explained to harouna how to use Solscan for verification and directed them to open a support ticket\n   - Bertram provided step-by-step guidance to Nika who was having issues migrating from Phantom wallet\n\n2. **Exchange Migration Information**\n   - Toni shared Binance Wallet's announcement about migration support with user Full Ahead\n   - Kenk confirmed to Korean users that the team is in contact with Bithumb and working on a solution\n\n3. **Technical Troubleshooting**\n   - When asher@CoinEx reported a non-functional migration link, vaipraonde confirmed it was working on their end\n   - Stan completed code reviews for PRs #6146 and #6147 requested by 0xbbjoker\n   - Stan offered to share a way to run a local GitHub runner with sayonara who was experiencing slow CI/CD\n\n## Action Items\n\n### Technical\n- Resolve migration issues for users who transferred tokens from exchanges after the snapshot (Multiple users)\n- Address the \"max amount reached\" error in the migration portal (Alexei)\n- Complete verification process on Jupiter, Titan, and Moonshot (Toni)\n- Establish process for handling Bithumb and Kraken users' migration (Kenk)\n- Review PR #6143 in ElizaOS repository (Odilitime)\n- Review PR #11 in plugin-anthropic repository (Odilitime)\n- Update Anthropic plugin to support Claude 3.5 models (Odilitime)\n- Add \"topP\" as a type in the core (0xbbjoker)\n- Complete entity isolation for websocket and API (Stan \u26a1)\n- Fix issue mentioned by Odilitime (response to \"Ugly, I'll fix\") (Odilitime)\n- Implement faster GitHub runner solution for Babylon (sayonara)\n- Fix debugging setup with Bun to allow breakpoints (vaipraonde)\n- Implement functionality to store and retrieve shared numbers between agents (vaipraonde)\n\n### Documentation\n- Create clear guidance for users with tokens on exchanges that haven't supported migration (Multiple users)\n- Provide step-by-step instructions for migration from different wallet types (Nika)\n- Update documentation on how to create and search memories for the new version (vaipraonde)\n\n### Feature\n- Consider reopening migration without snapshot restrictions (Omid sa)\n- Implement solution for users who had tokens in liquidity pools during snapshot (uzo)\n- List ElizaOS on Aster DEX (iory yagamy)\n- Improve communication channels for Korean community beyond Discord and X (kk)\n- Consider alternatives to Twitter API integration due to cost concerns (vaipraonde)\n---\n2025-11-12.md\n---\n# elizaOS Discord - 2025-11-12\n\n**Date: November 12, 2025**\n\n## Overall Discussion Highlights\n\n### Token Migration\n- A snapshot was taken on November 11, 2023, at 11:40 UTC to determine eligibility for AI16Z to ElizaOS token migration\n- Migration ratio is 1:6 (1 AI16Z = 6 ElizaOS)\n- Whitelist system implemented to prevent arbitrage that was suppressing ElizaOS price\n- Migration period will last 90 days\n- Team is working with exchanges (Bithumb, Binance, Kraken) to facilitate migration for CEX users\n- Users with tokens in liquidity pools during snapshot need to file support tickets for manual migration\n\n### Technical Development\n- Team is developing a rebuilt X-like platform with AI agents for prediction markets\n- Demo planned for upcoming Devconnect event\n- Some users reported issues with X posts from agents using elizaOS not working properly\n- Discussion about Vector DB options for onchain data, focusing on transparency and verifiability of embeddings\n\n### Partnerships & Projects\n- Potential university partnerships with UT Austin robotics department mentioned\n- Team member Jin is working on a new AI TV show project\n\n## Key Questions & Answers\n\n**Q: When was the snapshot taken?**  \nA: The snapshot was taken at 11:40 UTC on November 11, 2023 (answered by shaw)\n\n**Q: What is the conversion ratio from AI16Z to ElizaOS?**  \nA: 1 AI16Z = 6 ElizaOS (answered by Odilitime)\n\n**Q: What happens to AI16Z tokens held on exchanges?**  \nA: The team is working with exchanges to handle migration, and if exchanges don't support it, users can file tickets for manual migration (answered by shaw)\n\n**Q: What happens to AI16Z tokens in liquidity pools during the snapshot?**  \nA: Users should file a support ticket as the snapshot likely didn't capture LP positions (answered by DorianD)\n\n**Q: Can I still buy AI16Z and migrate it?**  \nA: No, only tokens held at the time of the snapshot are eligible (answered by Odilitime)\n\n**Q: What happens to AI16Z tokens that don't get migrated within 90 days?**  \nA: They will remain as AI16Z tokens, with possible manual migration in extreme cases (answered by Odilitime)\n\n**Q: Why was a whitelist implemented for migration?**  \nA: To prevent arbitrage which was keeping the AI16Z price pegged and depressing ElizaOS price (answered by shaw)\n\n**Q: How long will the migration be available?**  \nA: 90 days (answered by shaw)\n\n**Q: Why was this snapshot made and who are you trying to restrict from converting?**  \nA: It was done to get price unpegged from AI16Z so it could pump (answered by shaw)\n\n## Community Help & Collaboration\n\n1. **Migration Issues with Exchange-Held Tokens**\n   - User: susu\n   - Helper: shaw\n   - Issue: Concerns about AI16Z tokens held on Bithumb exchange\n   - Resolution: Shaw confirmed they're working with Bithumb and will manually migrate tokens if needed\n\n2. **Post-Snapshot Token Purchase**\n   - User: Omid sa\n   - Helper: shaw\n   - Issue: User bought tokens before announcement but after snapshot\n   - Resolution: Shaw directed user to file a ticket for manual assistance\n\n3. **LP Token Migration**\n   - User: FunkyLiza\n   - Helper: DorianD\n   - Issue: User had AI16Z tokens in liquidity pool during snapshot\n   - Resolution: Suggested filing a support ticket as snapshot likely didn't capture LP positions\n\n4. **Migration Error Troubleshooting**\n   - User: DorianD\n   - Helper: shaw & ben\n   - Issue: Encountered a simulation failure error when trying to migrate tokens\n   - Resolution: Issue resolved when DorianD removed decimal places from transaction amount; ben forwarded additional context to the development team\n\n5. **Migration Tool Access**\n   - User: Goated\n   - Helper: Toni\n   - Issue: User needed migration tool link\n   - Resolution: Provided link to migration announcement\n\n## Action Items\n\n### Technical\n- **Implement manual migration process** for users with legitimate holdings not captured in snapshot (Mentioned by shaw)\n- **Complete integration with exchanges** for token migration with Bithumb, Kraken and other exchanges (Mentioned by shaw)\n- **Showcase rebuilt X platform** with AI agents for prediction markets at Devconnect (Mentioned by shaw)\n- **Investigate simulation failure errors** during migration when using decimal amounts (Mentioned by DorianD)\n- **Process support tickets** for migration issues with priority (Mentioned by Kenk)\n- **Investigate X post issues** from agents using elizaOS while custom Python agents work correctly (Mentioned by JD_soul\ud83c\udde8\ud83c\uddfb)\n- **Fix wallet balance display issue** when clicking \"Max\" button (Mentioned by Jesse Spencer)\n- **Restore X (Twitter) accounts** before EFDevcon (Mentioned by DannyNOR NoFapArc)\n- **Implement cross-chain functionality** for ElizaOS across SOL, ETH, BASE & BSC chains (Mentioned by CryptoBlock)\n\n### Documentation\n- **Create clear guidelines** about migration eligibility explaining snapshot criteria and whitelist system (Mentioned by Cryptologos)\n- **Update migration FAQ** with common issues and solutions addressing \"Max Amount Reached\" errors and LP token migration (Mentioned by bramblebeard)\n- **Create documentation** about avoiding scammers in the community (Mentioned by Stanislav Tiutiunnyk)\n\n### Feature\n- **Develop prediction markets with AI agents** as training ground for improving prediction capabilities (Mentioned by shaw)\n- **Explore solutions for transparency/verifiability** of embeddings in Vector DBs for onchain data (Mentioned by Victor)\n- **Consider university partnerships** with University of Texas robotics researchers (Mentioned by DorianD)\n---\n2025-11-14.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-11-14\n---\nGitHub Activity Summary\n---\nOn November 14, 2025, the elizaOS/eliza repository showed moderate activity with 1 new pull request (none merged), 5 new issues opened, and 5 active contributors participating in the project.\n---\nIssues\n---\nIssue #6092 titled 'DevTools MCP Server' by @linear was CLOSED on November 14, 2025, approximately 23 days after creation with no comments recorded.\n---\nhttps://github.com/elizaOS/eliza/issues/6092\n---\nPull Requests\n---\nPR #6152 by @0xbbjoker titled 'fix: migrate from LangChain v0.3 to @langchain/textsplitters v1.0' is open, addressing a dependency migration to the newer textsplitters package version.\n---\nhttps://github.com/elizaOS/eliza/pull/6152\n---\nSummary for github_other\n---\nThe repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-11-14.md\n---\n# Daily Report - 2025-11-14\n\n## GitHub Activity Summary\n- On November 14, 2025, the elizaOS/eliza repository showed moderate activity with 1 new pull request (none merged), 5 new issues opened, and 5 active contributors participating in the project.\n\n## Issues\n- Issue #6092 titled 'DevTools MCP Server' by @linear was CLOSED on November 14, 2025, approximately 23 days after creation with no comments recorded. (Source: https://github.com/elizaOS/eliza/issues/6092)\n\n## Pull Requests\n- PR #6152 by @0xbbjoker titled 'fix: migrate from LangChain v0.3 to @langchain/textsplitters v1.0' is open, addressing a dependency migration to the newer textsplitters package version. (Source: https://github.com/elizaOS/eliza/pull/6152)\n\n## Summary for github_other\n- The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-11-14.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-11-14\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Analysis of \ud83d\udcac-discussion Channel\n\n## 1. Summary\nThe discussion primarily revolves around the migration from AI16Z to elizaOS tokens. Users are asking about the migration process, eligibility requirements, and technical aspects of holding the new tokens. The migration appears to be ongoing, with users able to migrate their tokens through a portal. Some users report successful migrations using wallets like Phantom. There are concerns from Korean community members about exchange listings, particularly on Bithumb, with claims that Korean exchanges are crucial for price action. The team representative (jasyn_bjorn) confirmed they are in contact with Korean exchanges. The elizaOS token is available on multiple chains including Solana, Ethereum, Base, and BSC, with official contract addresses shared. Some users are experiencing issues with seeing token prices in their wallets or confirming eligibility for migration.\n\n## 2. FAQ\nQ: Do you have to bridge Eliza off of Solana? (asked by HeatherD\ud83e\udd18\ud83c\udffb) A: If you did the migration from AI16Z to elizaOS on SOL, you can keep it there. You can also bridge using chainlink to other chains like base, ETH, BNB, etc if you wish (answered by MDMnvest)\nQ: I can't see the price of my Eliza coins in trust wallet. What should I do to see the price? (asked by Abdul) A: Just import the contract address mate (answered by TobyMoonWalker)\nQ: what is CA? (asked by geppetto0519) A: Unanswered\nQ: how to bridge elizaos from bsc to sol? (asked by vloine) A: Unanswered\nQ: Where i can sand tiket about migration tokens? (asked by OcRaf) A: https://discord.com/channels/1253563208833433701/1423981231300935801 (answered by Borko)\nQ: Where do I go to get my coins swapped? (asked by Beavstaley) A: Unanswered\n\n## 3. Help Interactions\nHelper: TobyMoonWalker | Helpee: Abdul | Context: User couldn't see the price of Eliza coins in trust wallet | Resolution: Advised to import the contract address\nHelper: MDMnvest | Helpee: HeatherD\ud83e\udd18\ud83c\udffb | Context: User was unsure if they needed to bridge Eliza off Solana | Resolution: Confirmed they can keep tokens on SOL or bridge to other chains if desired\nHelper: TobyMoonWalker | Helpee: Channel | Context: Users having issues with migration eligibility | Resolution: Provided detailed troubleshooting steps for \"eligible: 0\" errors\nHelper: TobyMoonWalker | Helpee: Channel | Context: Users needing official token contract addresses | Resolution: Shared official contract addresses for Solana, ETH, Base, and BSC\nHelper: Borko | Helpee: OcRaf | Context: User asking where to submit a ticket about migration | Resolution: Provided a direct link to the support channel\n\n## 4. Action Items\nTechnical: Resolve issues with token price display in Trust Wallet | Description: Users reporting zero price for elizaOS tokens | Mentioned By: Abdul\nTechnical: Address migration eligibility verification problems | Description: Some users seeing \"eligible: 0\" despite holding tokens before snapshot | Mentioned By: TobyMoonWalker\nTechnical: Implement bridge functionality between BSC and Solana | Description: User asked how to bridge elizaOS from BSC to SOL | Mentioned By: vloine\nFeature: Establish listing on Korean exchanges | Description: Korean community members emphasize importance of Bithumb listing | Mentioned By: qweqwe | Web3Go, kk\nDocumentation: Create clear guide for token migration process | Description: Multiple users asking basic migration questions | Mentioned By: Beavstaley, HeatherD\ud83e\udd18\ud83c\udffb\nDocumentation: Provide instructions for viewing token price in different wallets | Description: Users having trouble seeing token values | Mentioned By: Abdul\n---\n1300025221834739744\n---\n\ud83d\udcac-coders\n---\nThe chat segment is extremely brief, containing only two messages. There are no technical discussions, problem-solving activities, or decisions made in this exchange. The messages consist only of a greeting from JAKE BENSON \ud83d\udca1 saying \"Hi chat\" and a weekend greeting from !Sunny@.\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. There are mentions of ZK (zero-knowledge) technology, with one user expressing frustration about \"zcash dino shills\" and suggesting that ZK technology could be better applied to smart contracts and various use cases beyond simple cash payments. The conversation also includes a link to a YouTube interview about someone running a \"zk ml subnet,\" suggesting interest in the intersection of zero-knowledge proofs and machine learning. Overall, this segment doesn't contain substantial technical discussions, decisions, or problem-solving activities.\n\n## 2. FAQ\nQ: Wouldn't ZK be better if applied to smart contracts and use cases beyond simple cash payments? (asked by DorianD) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nTechnical: Explore applications of ZK technology beyond simple cash payments to smart contracts | Description: Consider broader applications of zero-knowledge proofs | Mentioned By: DorianD\nTechnical: Investigate ZK ML subnet implementation | Description: Follow up on the YouTube interview about ZK ML subnet | Mentioned By: DorianD\n---\n1377726087789940836\n---\ncore-devs\n---\nThe chat segment is extremely brief, consisting only of morning greetings between two users: \"sam-developer\" saying \"gm \ud83c\udf04\" and \"Stan \u26a1\" responding with \"gm\". There are no technical discussions, decisions, problem-solving, solutions, or implementations present in this limited exchange.\n---\n2025-11-14.md\n---\n# elizaOS Discord - 2025-11-14\n\n## 2025-11-14\n\n## Overall Discussion Highlights\n\n### Token Migration (AI16Z to elizaOS)\n- Migration from AI16Z to elizaOS tokens is actively ongoing through a dedicated portal\n- Users report successful migrations using wallets like Phantom\n- The elizaOS token is available on multiple chains: Solana, Ethereum, Base, and BSC\n- Official contract addresses were shared for all supported chains\n- Some users are experiencing issues with token price visibility in wallets\n\n### Exchange Listings\n- Korean community members emphasized the importance of listing on Korean exchanges, particularly Bithumb\n- Team representative (jasyn_bjorn) confirmed they are in contact with Korean exchanges\n- Korean exchanges were described as crucial for price action by several community members\n\n### Zero-Knowledge Technology\n- Brief discussion about ZK (zero-knowledge) technology applications\n- Suggestion that ZK could be better applied to smart contracts beyond simple cash payments\n- Reference to a YouTube interview about \"zk ml subnet\" (zero-knowledge machine learning)\n\n## Key Questions & Answers\n\n**Q: Do you have to bridge Eliza off of Solana?** (asked by HeatherD\ud83e\udd18\ud83c\udffb)  \n**A:** If you did the migration from AI16Z to elizaOS on SOL, you can keep it there. You can also bridge using chainlink to other chains like base, ETH, BNB, etc if you wish. (answered by MDMnvest)\n\n**Q: I can't see the price of my Eliza coins in trust wallet. What should I do to see the price?** (asked by Abdul)  \n**A:** Just import the contract address mate. (answered by TobyMoonWalker)\n\n**Q: Where i can sand tiket about migration tokens?** (asked by OcRaf)  \n**A:** https://discord.com/channels/1253563208833433701/1423981231300935801 (answered by Borko)\n\n## Community Help & Collaboration\n\n1. **Token Price Display Issue**\n   - User Abdul couldn't see the price of Eliza coins in Trust Wallet\n   - TobyMoonWalker advised importing the contract address as a solution\n\n2. **Migration Eligibility Troubleshooting**\n   - TobyMoonWalker provided detailed steps for users experiencing \"eligible: 0\" errors\n   - Shared official contract addresses for all supported chains to help users verify their tokens\n\n3. **Bridging Information**\n   - MDMnvest explained to HeatherD\ud83e\udd18\ud83c\udffb that tokens can remain on Solana or be bridged to other chains\n   - Clarified that Chainlink is used for the bridging process\n\n4. **Support Channel Guidance**\n   - Borko directed OcRaf to the appropriate support channel for migration issues\n   - Provided a direct link to streamline the support process\n\n## Action Items\n\n### Technical\n- **Resolve token price display issues in Trust Wallet** (Mentioned by Abdul)\n  - Users reporting zero price for elizaOS tokens\n- **Address migration eligibility verification problems** (Mentioned by TobyMoonWalker)\n  - Some users seeing \"eligible: 0\" despite holding tokens before snapshot\n- **Implement bridge functionality between BSC and Solana** (Mentioned by vloine)\n  - User asked how to bridge elizaOS from BSC to SOL\n- **Explore applications of ZK technology beyond simple cash payments** (Mentioned by DorianD)\n  - Consider broader applications of zero-knowledge proofs to smart contracts\n- **Investigate ZK ML subnet implementation** (Mentioned by DorianD)\n  - Follow up on the YouTube interview about ZK ML subnet\n\n### Feature\n- **Establish listing on Korean exchanges** (Mentioned by qweqwe, Web3Go, kk)\n  - Korean community members emphasize importance of Bithumb listing\n\n### Documentation\n- **Create clear guide for token migration process** (Mentioned by Beavstaley, HeatherD\ud83e\udd18\ud83c\udffb)\n  - Multiple users asking basic migration questions\n- **Provide instructions for viewing token price in different wallets** (Mentioned by Abdul)\n  - Users having trouble seeing token values\n---\n2025-11-15.md\n---\nFile not found\n---\n2025-11-09.md\n---\n# elizaos/eliza Weekly Report (Nov 9 - 15, 2025)\n\n## \ud83d\ude80 Highlights\nThis week's development focused on strengthening the core stability and configuration of the ElizaOS framework. Key achievements include a critical fix for Row-Level Security (RLS) validation, ensuring correct user access when isolation is disabled. Significant progress was also made in standardizing agent configuration by resolving how environment variables are loaded. Concurrently, work began on enhancing the core runtime to support a unified messaging API, reflecting a continued effort to build a robust and scalable foundation for AI agents.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this week centered on bug fixes, core enhancements, and new tooling capabilities.\n\n- **Core Stability and Configuration Fixes**\n    - A crucial bug was fixed where environment variables were not being loaded correctly, preventing agents from accessing settings. The system now properly loads variables from `process.env` instead of relying solely on `.env` files ([#6141](https://github.com/elizaos/eliza/pull/6141)).\n    - A critical issue with Row-Level Security (RLS) was resolved. The fix prevents `server_id` validation from incorrectly blocking all users when RLS isolation is disabled ([#6139](https://github.com/elizaos/eliza/pull/6139)).\n    - To improve system stability, a pull request was opened to remove message emission in the `src` API, aiming to prevent potential race conditions ([#6137](https://github.com/elizaos/eliza/pull/6137)).\n\n- **Runtime and API Enhancements**\n    - A new feature was merged to include an ElizaOS reference within the runtime. This change is a step towards creating a unified messaging API and involved updates across several core packages ([#6111](https://github.com/elizaos/eliza/pull/6111)).\n\n- **New Tooling Features**\n    - A new pull request was opened to add an OpenRouter embedding option to the command-line interface (CLI), expanding the framework's integration capabilities ([#6142](https://github.com/elizaos/eliza/pull/6142)).\n\n## \ud83d\udc1b Issues & Triage\n\n- **Closed Issues:**\n    - Issue [#6138](https://github.com/elizaos/eliza/issues/6138), which reported that disabling the Web UI blocked all endpoints, was opened and closed on the same day. It was noted as being prematurely opened and remains under investigation.\n\n- **New & Active Issues:**\n    - A new high-priority issue was reported where an agent fails to respond to questions, producing a \"No handler found for delegate type: TEXT_LARGE\" error ([#6140](https://github.com/elizaos/eliza/issues/6140)). This represents a potential blocker for agent communication functionality.\n    - No active issues generated significant discussion this week.\n\n## \ud83d\udcac Community & Collaboration\nThe development activity this week indicates a focused effort on foundational improvements. The work on environment variables, RLS, and race conditions suggests a proactive approach to ensuring system stability and reliability. While the reports do not indicate high levels of discussion on specific issues, the mix of bug fixes, core refactoring, and new feature proposals demonstrates steady and methodical progress across the project.\n---\n2025-11-01.md\n---\n# elizaos/eliza Monthly Report (November 2025)\n\n## \ud83d\ude80 Highlights\nNovember kicked off with a dual focus on enhancing system stability and laying the groundwork for significant new capabilities. A critical bug affecting agent settings persistence was resolved, directly improving the framework's reliability. Concurrently, new development was initiated to introduce entity-level security and enhance the core runtime. The opening of several strategic issues signals a forward-looking push towards improved performance through parallel actions and background tasks, as well as new user engagement features.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this month balanced immediate fixes with the introduction of new features.\n\n- **Agent Stability Improvement**\n  A significant bug was fixed that prevented agent settings from persisting across restarts, ensuring that runtime-generated configurations are now correctly retained. This change, made to the core runtime initialization logic, enhances the overall reliability of agent operations ([#6106](https://github.com/elizaos/eliza/pull/6106)).\n\n- **New Feature Initiatives**\n  Development began on several new fronts with the opening of new pull requests:\n  - **Security:** A proposal was made to implement entity-level row-level security, aiming to add more granular data access controls ([#6107](https://github.com/elizaos/eliza/pull/6107)).\n  - **Runtime Enhancements:** Work started on adding an ElizaOS reference directly to the runtime, likely to streamline framework interactions ([#6111](https://github.com/elizaos/eliza/pull/6111)).\n\n## \ud83d\udc1b Issues & Triage\nIssue tracking this month was focused on defining the next wave of development priorities.\n\n- **Closed Issues:** No issues were closed during this period.\n\n- **New & Active Issues:** Several key issues were opened, outlining major areas for future work:\n  - **Core Functionality & Performance:** Discussions were initiated around implementing \"Parallel actions\" ([#6108](https://github.com/elizaos/eliza/issues/6108)) and \"Background tasks\" ([#6109](https://github.com/elizaos/eliza/issues/6109)), indicating a focus on scaling the system's operational capacity.\n  - **Security & User Engagement:** New issues were created for \"Entity-level RLS\" ([#6112](https://github.com/elizaos/eliza/issues/6112)), which complements the ongoing PR, and a \"Points / Leaderboard\" system ([#6110](https://github.com/elizaos/eliza/issues/6110)) to enhance user interaction.\n  - According to the reports, none of the active issues have generated more than three comments, suggesting discussions are still in their early stages.\n\n## \ud83d\udcac Community & Collaboration\nThe provided reports indicate a period of focused, heads-down development. While new pull requests and issues were opened, the data does not show any high-volume discussions or specific collaborative events. The alignment between the new pull request for RLS ([#6107](https://github.com/elizaos/eliza/pull/6107)) and the corresponding new issue ([#6112](https://github.com/elizaos/eliza/issues/6112)) suggests coordinated planning around new features.\n---\n{\n  \"interval\": {\n    \"intervalStart\": \"2025-11-01T00:00:00.000Z\",\n    \"intervalEnd\": \"2025-12-01T00:00:00.000Z\",\n    \"intervalType\": \"month\"\n  },\n  \"repository\": \"elizaos/eliza\",\n  \"overview\": \"From 2025-11-01 to 2025-12-01, elizaos/eliza had 17 new PRs (8 merged), 32 new issues, and 19 active contributors.\",\n  \"topIssues\": [\n    {\n      \"id\": \"I_kwDOMT5cIs7XCsUe\",\n      \"title\": \"Bug: Disabling Web UI blocks all endpoints\",\n      \"author\": \"humuhimi\",\n      \"number\": 6138,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"\",\n      \"createdAt\": \"2025-11-10T12:26:11Z\",\n      \"closedAt\": \"2025-11-10T12:47:31Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 2\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7V2H1G\",\n      \"title\": \"Support Tasks\",\n      \"author\": \"borisudovicic\",\n      \"number\": 6131,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"* Collaborate with CJ on anonymous ID + free inference architecture.\",\n      \"createdAt\": \"2025-11-04T18:16:47Z\",\n      \"closedAt\": \"2025-11-08T12:37:51Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 1\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7V2Hh0\",\n      \"title\": \"Voice Infrastructure\",\n      \"author\": \"borisudovicic\",\n      \"number\": 6130,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"* Test browser-based voice generation (client-side).\\n* Prepare optional **server voice endpoint** for paid users.\\n* Support Compute embeddings integration.\",\n      \"createdAt\": \"2025-11-04T18:16:25Z\",\n      \"closedAt\": \"2025-11-14T13:34:37Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 1\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7V2HTC\",\n      \"title\": \"Plugin-Cloud Testing\",\n      \"author\": \"borisudovicic\",\n      \"number\": 6129,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"* Test plugin-cloud within Eliza Framework.\\n* Verify tool registration + documentation accuracy.\",\n      \"createdAt\": \"2025-11-04T18:16:06Z\",\n      \"closedAt\": \"2025-11-14T13:34:38Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 1\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7V2Gw0\",\n      \"title\": \"Docs\",\n      \"author\": \"borisudovicic\",\n      \"number\": 6128,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"* Build new /docs UI (public, not auth-locked).\\n* Include:\\n  * OpenAI-style API explorer.\\n  * Character setup & API key usage examples.\\n  * Overview of Cloud architecture.\",\n      \"createdAt\": \"2025-11-04T18:15:26Z\",\n      \"closedAt\": null,\n      \"state\": \"OPEN\",\n      \"commentCount\": 1\n    }\n  ],\n  \"topPRs\": [\n    {\n      \"id\": \"PR_kwDOMT5cIs6vVL6j\",\n      \"title\": \"feat: create @elizaos/react package with headless React hooks\",\n      \"author\": \"wtfsayo\",\n      \"number\": 6093,\n      \"body\": \"## Overview\\n\\nThis PR introduces a new **** package containing headless, reusable React hooks extracted from the client package. This enables external developers to build custom UIs for ElizaOS agents while maintaining full type safety and React Query integration.\\n\\n## What's New\\n\\n### Package: \\n\\nA standalone package providing headless React hooks with:\\n- \u2705 Zero UI coupling (no toasts, navigation, or DOM dependencies)\\n- \u2705 Full TypeScript support with proper type declarations\\n- \u2705 TanStack React Query for caching and state management\\n- \u2705 Network-aware polling that adapts to connection quality\\n- \u2705 Composable lifecycle callbacks (onSuccess, onError, onMutate)\\n\\n### Hooks Included (30 total)\\n\\n**Agents (8 hooks)**\\n- `useAgents`, `useAgent`, `useStartAgent`, `useStopAgent`\\n- `useAgentActions`, `useDeleteLog`, `useAgentPanels`, `useAgentsWithDetails`\\n\\n**Runs (2 hooks)**\\n- `useAgentRuns`, `useAgentRunDetail`\\n\\n**Messaging (5 hooks)**\\n- `useServers`, `useChannels`, `useChannelDetails`, `useChannelParticipants`, `useDeleteChannel`\\n\\n**Messages (3 hooks)**\\n- `useChannelMessages` (stateful with pagination), `useDeleteChannelMessage`, `useClearChannelMessages`\\n\\n**Memories (6 hooks)**\\n- `useAgentMemories`, `useDeleteMemory`, `useDeleteAllMemories`, `useUpdateMemory`, `useDeleteGroupMemory`, `useClearGroupChat`\\n\\n**Internal/Agent-Perspective (6 hooks)**\\n- `useAgentInternalActions`, `useDeleteAgentInternalLog`, `useAgentInternalMemories`\\n- `useDeleteAgentInternalMemory`, `useDeleteAllAgentInternalMemories`, `useUpdateAgentInternalMemory`\\n\\n## Architecture\\n\\n```tsx\\nimport { QueryClient, QueryClientProvider } from '@tanstack/react-query';\\nimport { ElizaReactProvider, useAgents, useStartAgent } from '@elizaos/react';\\n\\nconst queryClient = new QueryClient();\\n\\nfunction App() {\\n  return (\\n    <QueryClientProvider client={queryClient}>\\n      <ElizaReactProvider baseUrl=\\\"http://localhost:3000\\\">\\n        <AgentList />\\n      </ElizaReactProvider>\\n    </QueryClientProvider>\\n  );\\n}\\n\\nfunction AgentList() {\\n  const { data: agents, isLoading } = useAgents();\\n  const startAgent = useStartAgent({\\n    onSuccess: () => toast.success('Agent started!'),\\n  });\\n\\n  if (isLoading) return <div>Loading...</div>;\\n\\n  return (\\n    <div>\\n      {agents?.map((agent) => (\\n        <div key={agent.id}>\\n          <h3>{agent.name}</h3>\\n          <button onClick={() => startAgent.mutate(agent.id)}>\\n            Start\\n          </button>\\n        </div>\\n      ))}\\n    </div>\\n  );\\n}\\n```\\n\\n## Benefits\\n\\n1. **Reusability**: External developers can build custom UIs using these hooks\\n2. **Type Safety**: Full TypeScript support with types from `@elizaos/api-client`\\n3. **Performance**: Smart polling adapts to network quality (2G \u2192 4G)\\n4. **Separation of Concerns**: UI logic stays in components, data logic in hooks\\n5. **Future-proof**: Ready for migration of `packages/client` to consume these hooks\\n\\n## Testing\\n\\n- \u2705 Package builds successfully with TypeScript declarations\\n- \u2705 All hooks properly typed with React Query v5 signatures\\n- \u2705 Zero build errors or type issues\\n- \u2705 Ready for integration into turbo build pipeline\\n\\n## Next Steps (Future PRs)\\n\\n- Migrate `packages/client` to consume `@elizaos/react`\\n- Add unit tests for hooks with mocked ElizaClient\\n- Publish to npm for external consumption\\n\\n## Files Changed\\n\\n- `packages/react/` - New package with provider, hooks, and documentation\\n- Comprehensive README with installation, API reference, and examples\\n\\n---\\n\\n**Ready for review!** \ud83d\ude80\\n\\n<!-- CURSOR_SUMMARY -->\\n---\\n\\n> [!NOTE]\\n> Introduces a new `@elizaos/react` package with headless, type-safe React hooks and provider (plus build/docs), integrates it into the workspace, and publishes comprehensive core type declarations.\\n> \\n> - **New package `@elizaos/react`**:\\n>   - Headless React hooks and provider (`ElizaReactProvider`) built on `@tanstack/react-query` and `@elizaos/api-client`.\\n>   - Hooks for: agents, runs, messaging (servers/channels), messages (stateful + pagination), memories, and internal agent-perspective operations.\\n>   - Network-aware polling, composable mutation callbacks, TypeScript types, and index exports.\\n>   - Build tooling (`build.ts`, bunfig, tsconfigs), and comprehensive README.\\n> - **Workspace integration**:\\n>   - Added to lockfile/workspace with peer/dev deps.\\n> - **Type declarations**:\\n>   - Added/updated numerous `@elizaos/core` `.d.ts` and source maps to expose APIs/types for consumers.\\n> \\n> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5a290e0071637d785858567d960ab7d1d5e54456. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>\\n<!-- /CURSOR_SUMMARY -->\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-10-23T18:06:32Z\",\n      \"mergedAt\": null,\n      \"additions\": 8223,\n      \"deletions\": 1753\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6xETJ-\",\n      \"title\": \"feat: implement entity-level row level security\",\n      \"author\": \"standujar\",\n      \"number\": 6107,\n      \"body\": \"\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-11-02T16:12:48Z\",\n      \"mergedAt\": null,\n      \"additions\": 6241,\n      \"deletions\": 1389\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6xVUO6\",\n      \"title\": \"feat: x402 middleware\",\n      \"author\": \"odilitime\",\n      \"number\": 6114,\n      \"body\": \"pulled enhanced response & health check from Otaku\\r\\n\\r\\n\\n<!-- CURSOR_SUMMARY -->\\n---\\n\\n> [!NOTE]\\n> Introduces x402 payment protection for plugin routes (EVM/Solana), adds core payment types, integrates verification and x402scan 402 responses, plus config registry, docs, and tests.\\n> \\n> - **Server (x402 middleware)**:\\n>   - Add payment middleware (`x402/`) with EVM (EIP-712/ERC-3009) and Solana verification, facilitator payment ID support, and x402scan-compliant 402 responses.\\n>   - Integrate into plugin routing to auto-wrap routes with `x402` config (`createPaymentAwareHandler`, `applyPaymentProtection`).\\n>   - Expose middleware/types via `middleware/index.ts` and `x402/index.ts`.\\n> - **Core Types**:\\n>   - Add payment types (`PaymentEnabledRoute`, `X402Config`, validators, OpenAPI helpers) in `@elizaos/core` (`types/payment.ts` and export in `types/index.ts`).\\n> - **Config & Utilities**:\\n>   - Add payment config registry (`payment-config.ts`) with built-in configs (`base_usdc`, `solana_usdc`, `polygon_usdc`), CAIP-19 generation, pricing helpers, health reporting.\\n>   - Define strict x402 schemas (`x402-types.ts`) and request/response/runtime types (`types.ts`).\\n> - **API Integration**:\\n>   - Update `api/index.ts` to use payment-aware handlers for plugin routes.\\n> - **Docs & Tests**:\\n>   - Add comprehensive README for x402 usage.\\n>   - Add extensive tests for amount conversion, verification logic, integration, config, and schema validation.\\n> - **Dependencies**:\\n>   - Add `viem`, `@solana/web3.js`, and `cors` to server; lockfile updates.\\n> \\n> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit d64e2a5e1045bc204ffb435d0ef74a044efe1287. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>\\n<!-- /CURSOR_SUMMARY -->\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-11-04T06:10:07Z\",\n      \"mergedAt\": null,\n      \"additions\": 5434,\n      \"deletions\": 10\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6zHHko\",\n      \"title\": \"fix: plugin-mysql support, initPromise and other minor fixes\",\n      \"author\": \"odilitime\",\n      \"number\": 6143,\n      \"body\": \"<!-- CURSOR_SUMMARY -->\\n> [!NOTE]\\n> Adds conditional MySQL vs SQL plugin selection (with URL validation and MySQL no-op migrations), introduces runtime initPromise, updates mocks, and adds comprehensive tests.\\n> \\n> - **Server**:\\n>   - **Database plugin selection**: Dynamically load `@elizaos/plugin-mysql` when `MYSQL_URL` is set; otherwise use `@elizaos/plugin-sql`.\\n>   - **Utilities**: Add `validateAndLogMySQLUrl` and `MySQLNoOpMigrationService` for MySQL.\\n>   - **RLS**: Enable only for PostgreSQL; skip/cleanup when using MySQL.\\n>   - **DB ops**: Parameterized default server creation with dialect-specific upsert (`ON DUPLICATE KEY UPDATE` vs `ON CONFLICT`).\\n>   - **Logging**: Trim verbose route-matching logs; minor try/catch cleanup.\\n> - **CLI (Scenario)**:\\n>   - Plugin selection prefers MySQL when `MYSQL_URL` or explicit plugin present; otherwise SQL.\\n>   - Avoid loading both `plugin-sql` and `plugin-mysql`; only set `PGLITE_DATA_DIR` for SQL.\\n> - **Core**:\\n>   - Add `initPromise: Promise<void>` to `IAgentRuntime`.\\n> - **Test Utils**:\\n>   - Mock runtime gains pending `initPromise` with `resolveInit`/`rejectInit`; mocks migrated to `bun:test`.\\n> - **Tests**:\\n>   - New tests for scenario plugin selection, server MySQL compatibility/behavior, and runtime/mock `initPromise` semantics.\\n> \\n> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 96c2b1df774f0e6c889e7ac22a33d9e03599c317. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>\\n<!-- /CURSOR_SUMMARY -->\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n  * Added support for flexible database provider selection, allowing configuration with either MySQL or PostgreSQL through environment variables.\\n\\n* **Improvements**\\n  * Updated security features to conditionally enable based on your database provider.\\n  * Enhanced Content Security Policy configuration and database initialization flow.\\n\\n<!-- end of auto-generated comment: release notes by coderabbit.ai -->\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-11-13T01:58:45Z\",\n      \"mergedAt\": null,\n      \"additions\": 2015,\n      \"deletions\": 369\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6xr7AQ\",\n      \"title\": \"fix: entity names array serialization for PostgreSQL\",\n      \"author\": \"0xbbjoker\",\n      \"number\": 6133,\n      \"body\": \"Fix entity creation failures by normalizing the names field to ensure it's\\r\\nalways a proper array before database operations. Handles Set objects by\\r\\nconverting them with Array.from().\\r\\n\\r\\n- Add normalization in createEntities() and updateEntity()\\r\\n- Add test suite with 9 comprehensive tests\\r\\n- All 491 plugin-sql tests pass\\n\\n<!-- CURSOR_SUMMARY -->\\n---\\n\\n> [!NOTE]\\n> Normalizes `Entity.names` to a proper string array in create/update operations and adds extensive integration tests covering diverse input types.\\n> \\n> - **Backend (plugin-sql)**:\\n>   - Add `private normalizeEntityNames()` in `src/base.ts` to coerce `Entity.names` into a string array (handles strings, arrays, Sets, Maps/iterables, non-iterables, null/undefined; stringifies elements).\\n>   - Apply normalization and default `metadata: {}` in `createEntities()` and `updateEntity()`.\\n>   - Enhance error logging in `createEntities()` with stack trace on failure.\\n> - **Tests**:\\n>   - Add `__tests__/integration/entity-array-fix.test.ts` covering creation/update with single/multiple/empty names, Sets, batch insert, special/unicode chars.\\n>   - Expand `__tests__/integration/entity-methods.test.ts` with normalization scenarios: string (no char-splitting), Set, Map, custom iterables, numbers/booleans/objects/null/undefined, mixed-type arrays/Sets, and update paths.\\n> \\n> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 749e83062f833482b41c2b5c2399bdc968b03a70. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>\\n<!-- /CURSOR_SUMMARY -->\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-11-05T15:47:36Z\",\n      \"mergedAt\": \"2025-11-05T17:06:38Z\",\n      \"additions\": 819,\n      \"deletions\": 2\n    }\n  ],\n  \"codeChanges\": {\n    \"additions\": 2403,\n    \"deletions\": 502,\n    \"files\": 34,\n    \"commitCount\": 129\n  },\n  \"completedItems\": [\n    {\n      \"title\": \"fix: agent settings persistence across restarts\",\n      \"prNumber\": 6106,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nFixes agent settings not persisting across restarts, causing runtime-generated configuration to be lost.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk**\\r\\n\\r\\n- Changes core runtime initialization logic for agent settings merge\\r\\n- All existing test\",\n      \"files\": [\n        \"packages/core/src/__tests__/ensure-agent-exists.test.ts\",\n        \"packages/core/src/runtime.ts\"\n      ]\n    },\n    {\n      \"title\": \"feat: add ElizaOS reference to runtime\",\n      \"prNumber\": 6111,\n      \"type\": \"feature\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\nRelates to #6095 - Unified messaging API\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk**\\r\\n\\r\\nThis change is non-breaking and \",\n      \"files\": [\n        \"packages/core/src/__tests__/elizaos.test.ts\",\n        \"packages/core/src/elizaos.ts\",\n        \"packages/core/src/runtime.ts\",\n        \"packages/core/src/types/elizaos.ts\",\n        \"packages/core/src/types/index.ts\",\n        \"packages/core/src/types/runtime.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres-init.test.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/index.test.ts\",\n        \"packages/project-starter/src/__tests__/utils/core-test-utils.ts\",\n        \"packages/project-tee-starter/src/__tests__/utils/core-test-utils.ts\",\n        \"packages/server/src/__tests__/integration/jobs-message-flow.test.ts\",\n        \"packages/core/src/__tests__/runtime-embedding.test.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(plugin-sql): correct types path in package.json exports\",\n      \"prNumber\": 6134,\n      \"type\": \"bugfix\",\n      \"body\": \"- Fix incorrect types path from ./types/index.d.ts to ./dist/index.d.ts\\r\\n- Remove non-existent 'types' directory from files array\\r\\n- Resolves TypeScript import errors when using @elizaos/plugin-sql\\n\\n<!-- CURSOR_SUMMARY -->\\n---\\n\\n> [!NOTE]\\n> \",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/plugin-sql/package.json\"\n      ]\n    },\n    {\n      \"title\": \"fix: entity names array serialization for PostgreSQL\",\n      \"prNumber\": 6133,\n      \"type\": \"bugfix\",\n      \"body\": \"Fix entity creation failures by normalizing the names field to ensure it's\\r\\nalways a proper array before database operations. Handles Set objects by\\r\\nconverting them with Array.from().\\r\\n\\r\\n- Add normalization in createEntities() and updateEn\",\n      \"files\": [\n        \"packages/plugin-sql/src/__tests__/integration/entity-array-fix.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/entity-methods.test.ts\",\n        \"packages/plugin-sql/src/base.ts\"\n      ]\n    },\n    {\n      \"title\": \"feat(core): add skipMigrations option to runtime.initialize() for ser\u2026\",\n      \"prNumber\": 6132,\n      \"type\": \"feature\",\n      \"body\": \"- Add optional skipMigrations parameter to initialize() method in IAgentRuntime interface\\r\\n- Implement skipMigrations logic in AgentRuntime.initialize() to conditionally skip plugin migrations\\r\\n- Default behavior unchanged - migrations run \",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/core/src/__tests__/runtime.test.ts\",\n        \"packages/core/src/runtime.ts\",\n        \"packages/core/src/types/runtime.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix: load environment variables from process.env instead of .env file\",\n      \"prNumber\": 6141,\n      \"type\": \"bugfix\",\n      \"body\": \"## Relates to\\r\\n\\r\\nFixes the issue where `runtime.getSetting(\\\"ANY_VARIABLES\\\")` returns `undefined` when environment variables are exported on the host (`export VAR=value`) instead of being defined in a `.env` file, causing agents to use incor\",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/cli/src/commands/start/index.ts\",\n        \"packages/core/src/__tests__/secrets.test.ts\",\n        \"packages/core/src/__tests__/settings.test.ts\",\n        \"packages/core/src/__tests__/utils/environment.test.ts\",\n        \"packages/core/src/secrets.ts\",\n        \"packages/core/src/utils/environment.ts\",\n        \"packages/server/src/index.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix: RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled.\",\n      \"prNumber\": 6139,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nFix for RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled.\\r\\n\\r\\nMaybe: https://github.com/elizaOS/eliza/issues/6138\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**. Changes only affect RLS security c\",\n      \"files\": [\n        \"packages/server/src/__tests__/rls-server.test.ts\",\n        \"packages/server/src/api/messaging/channels.ts\",\n        \"packages/server/src/api/messaging/core.ts\",\n        \"packages/server/src/utils/rls-validation.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(build): resolve TypeScript declaration generation errors\",\n      \"prNumber\": 6146,\n      \"type\": \"bugfix\",\n      \"body\": \"- Add missing hasElizaOS() method to test-utils mock runtime\\r\\n  * Implements required type predicate from IAgentRuntime interface\\r\\n  * Returns false by default for test scenarios\\r\\n\\r\\n- Fix plugin-sql TypeScript declaration generation\\r\\n  * Ov\",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/plugin-sql/build.ts\",\n        \"packages/plugin-sql/tsconfig.build.json\",\n        \"packages/plugin-sql/tsconfig.build.node.json\",\n        \"packages/test-utils/src/mocks/runtime.ts\"\n      ]\n    }\n  ],\n  \"topContributors\": [\n    {\n      \"username\": \"odilitime\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n      \"totalScore\": 344.58204617878323,\n      \"prScore\": 343.64204617878323,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.94,\n      \"summary\": \"odilitime: This month, odilitime made significant contributions to documentation and bug fixes, while also initiating new feature work. They landed a major documentation update in elizaos/spartan#21, which added over 5,000 lines, and also merged a fix for tasks in elizaos-plugins/plugin-birdeye#7. In addition to this merged work, they have several features in progress for the elizaos/eliza repository, including a new framework for adjusting prompts (#6113). Their activity shows a primary focus on general development and bug fixes, with contributions spread across code, tests, and documentation.\"\n    },\n    {\n      \"username\": \"0xbbjoker\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n      \"totalScore\": 248.06668232304372,\n      \"prScore\": 237.8666823230437,\n      \"issueScore\": 0,\n      \"reviewScore\": 10,\n      \"commentScore\": 0.2,\n      \"summary\": \"0xbbjoker: This month, 0xbbjoker focused on extending plugin capabilities by implementing a key feature in `elizaos-plugins/plugin-openrouter` via PR #17. This significant contribution added support for `TEXT_EMBEDDING` models, involving changes across code, tests, and configuration files. In addition to this feature work, they also contributed one pull request review.\"\n    },\n    {\n      \"username\": \"Freytes\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4147278?u=89aa9570e6f8b4a8e9e41e8f908c16fb69c5a43f&v=4\",\n      \"totalScore\": 232.1658694828805,\n      \"prScore\": 232.1658694828805,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Freytes: Focused on adding substantial new features to the `elizaos/spartan` repository, merging four significant pull requests. Their most impactful contributions included introducing a new Chrome extension in PR #17 (+42042 lines) and a Farcaster miniapp in PR #19 (+13210 lines). Freytes also improved the developer experience by adding Docker support for an easier development setup in PR #20. In total, their work added over 67k lines of new code and tests to build out major new components for the project.\"\n    },\n    {\n      \"username\": \"standujar\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n      \"totalScore\": 213.957158133888,\n      \"prScore\": 181.37715813388797,\n      \"issueScore\": 0,\n      \"reviewScore\": 31.5,\n      \"commentScore\": 1.08,\n      \"summary\": \"standujar: Focused on developing several key features this month, with a significant amount of work in progress across multiple repositories. They opened pull requests to implement entity-level row-level security (elizaos/eliza#6107) and integrate a unified messaging API for the Discord plugin (elizaos-plugins/plugin-discord#24). This work, while not yet merged, involved substantial changes across 187 files (+4640/-1654 lines) and 25 commits. Based on their code changes, their effort was primarily centered on new feature development and refactoring.\"\n    },\n    {\n      \"username\": \"wtfsayo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n      \"totalScore\": 66.99339001321847,\n      \"prScore\": 66.99339001321847,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"wtfsayo: This month, wtfsayo focused on maintenance within the `elizaos-plugins/plugin-mcp` repository. They merged a single pull request (#18) to update action names and dependencies, which involved a significant refactor that removed nearly 400 lines of code. Their commits were distributed across feature work, bug fixes, and tests, primarily modifying code, documentation, and configuration files.\"\n    },\n    {\n      \"username\": \"borisudovicic\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31806472?u=8935f4d43fd7e4eb9bf5ff92d54d4d2f8ac8a786&v=4\",\n      \"totalScore\": 42.2,\n      \"prScore\": 0,\n      \"issueScore\": 42,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"borisudovicic: Focused on planning and defining future work for the elizaos/eliza repository this month. They initiated discussions on several potential features by creating issues for \\\"Points / Leaderboard\\\" (#6110), \\\"Background tasks\\\" (#6109), and \\\"Parallel actions\\\" (#6108).\"\n    },\n    {\n      \"username\": \"rferrari\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/495887?u=5a56d90f584ffc1827bb301541076597dca9cb3e&v=4\",\n      \"totalScore\": 36.77887055267063,\n      \"prScore\": 34.57887055267063,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": null\n    },\n    {\n      \"username\": \"ai16x402\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/241517257?u=db5e37fbc5cfc2fc78bd2de767f7235704dc2b0f&v=4\",\n      \"totalScore\": 25.22068353919891,\n      \"prScore\": 24.78268353919891,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.43799999999999994,\n      \"summary\": \"ai16x402: This month, ai16x402 focused on expanding the plugin ecosystem by opening three pull requests to add new plugins to the `elizaos-plugins/registry` (#237, #238, #239). This work, which is still in progress, involved 7 commits and modifications to configuration files (+80/-18 lines). They also participated in discussions with 3 comments on pull requests.\"\n    },\n    {\n      \"username\": \"madjin\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n      \"totalScore\": 23.146346309695485,\n      \"prScore\": 23.146346309695485,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"madjin: This month, madjin focused on expanding the project's pipeline configuration. They merged a pull request in elizaos/elizaos.github.io (#169) that added 12 new active repositories to the system. This work consisted entirely of modifications to configuration files.\"\n    },\n    {\n      \"username\": \"Neysixx\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/115616810?u=94c403172b4ffda30d6fc765f5997631fb7d1ef1&v=4\",\n      \"totalScore\": 22.861633597686627,\n      \"prScore\": 22.861633597686627,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"ChristopherTrimboli\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n      \"totalScore\": 16,\n      \"prScore\": 0,\n      \"issueScore\": 0,\n      \"reviewScore\": 16,\n      \"commentScore\": 0,\n      \"summary\": \"ChristopherTrimboli: Focused on supporting the team through code review this month, performing 3 reviews which included 2 approvals and 1 request for changes. He also made progress on a local refactoring effort, committing changes across 17 files.\"\n    },\n    {\n      \"username\": \"tungpun\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/5058370?u=59cb956de322867be56c0abee49ab3f28f819e2f&v=4\",\n      \"totalScore\": 13.943573590279971,\n      \"prScore\": 13.943573590279971,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"nguyennk92\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/30664183?u=d6e579cd25d50bc8e9ec4928d95909d759b841db&v=4\",\n      \"totalScore\": 12.345835825288448,\n      \"prScore\": 12.145835825288449,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": null\n    },\n    {\n      \"username\": \"otaku-x402\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/242004857?u=1325b26d380eec4a0b8d84e8e249c523eebd28dc&v=4\",\n      \"totalScore\": 11.897573590279972,\n      \"prScore\": 11.897573590279972,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"otaku-x402: No activity this month.\"\n    },\n    {\n      \"username\": \"github-advanced-security\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/in/57789?v=4\",\n      \"totalScore\": 4.5,\n      \"prScore\": 0,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"humuhimi\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/35215680?u=029a1ed6ea6a26ebf1cfd081cba6af2e6d32ef6d&v=4\",\n      \"totalScore\": 4.3,\n      \"prScore\": 0,\n      \"issueScore\": 4.1,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": null\n    },\n    {\n      \"username\": \"samarth30\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n      \"totalScore\": 4,\n      \"prScore\": 0,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"samarth30: This month, samarth30's contribution was focused on planning for new billing functionality in the Eliza Cloud product. They initiated this effort by creating an issue to track the integration of Stripe for settings and billing (elizaos/eliza#6118).\"\n    },\n    {\n      \"username\": \"LinuxIsCool\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31582215?u=b8eb5d3849bf877a3a0b686cf1632aca92e744ae&v=4\",\n      \"totalScore\": 4,\n      \"prScore\": 0,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"LinuxIsCool: This month, LinuxIsCool's contributions were focused on project maintenance within the elizaos/eliza repository. They identified and opened two issues regarding project health: #6122 about missing documentation and #6121 concerning an outdated changelog.\"\n    },\n    {\n      \"username\": \"tdnupe3\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25161668?u=94680b6bcbcfce954c7a9dd09d667a3919953041&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"skurzyp\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/98319381?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"nikatuz8-cell\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/243873833?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"linear\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"linear: This month's activity consisted of creating an issue to define entity-level row-level security in elizaos/eliza (#6112).\"\n    },\n    {\n      \"username\": \"christophwallacher-web\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/233379771?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    }\n  ],\n  \"newPRs\": 17,\n  \"mergedPRs\": 8,\n  \"newIssues\": 32,\n  \"closedIssues\": 18,\n  \"activeContributors\": 19\n}"
  ]
}