{
"prompt_name": "developer-update",
"category": "dev",
"date": "2025-11-12",
"generated_text": "# ElizaOS Developer Update - Nov 12, 2025\n\n## Core Framework\nThe ElizaOS runtime has received significant updates to improve stability and security:\n\n- **Entity-level Row-Level Security (RLS)**: Significant progress on implementing fine-grained data access controls (#6107). This enables restricting data access at the entity level rather than just server level.\n\n- **Performance Optimization**: The framework now supports skipping migrations during runtime initialization via a new `skipMigrations` parameter to `runtime.initialize()` (#6132). This is particularly useful for serverless and ephemeral environments where migration checks add unnecessary overhead.\n\n- **Bug Fix**: Fixed critical issue with RLS server_id validation that was blocking all users when RLS isolation was disabled (#6139). This resolves a critical authentication problem reported in issue #6138.\n\n- **Agent Settings Persistence**: Fixed an important bug (#6106) where agent settings would not persist across restarts, causing runtime-generated configurations to be lost.\n\n```typescript\n// Now supports optional migration skipping\nawait runtime.initialize({\n skipMigrations: process.env.SKIP_MIGRATIONS === 'true'\n});\n```\n\n## New Features\n\n### Dynamic Prompt Execution System\nA new schema-based dynamic prompt executor (#6113) has been implemented to optimize prompt handling for different model context sizes:\n\n```typescript\nconst result = await runtime.dynamicPromptExecFromState({\n state,\n schema: {\n thought: \"string\",\n actions: \"array\"\n },\n prompt: promptTemplate, // Handlebars template\n validationLevel: process.env.VALIDATION_LEVEL || \"strict\"\n});\n```\n\nKey capabilities:\n- Automatic XML/JSON parsing with validation codes\n- Handlebars state injection\n- Token estimation and retry handling\n- Execution metrics tracking via `modelSchemaMetrics`\n- Configurable validation levels and cache size via `DYNAMIC_PROMPT_MAX_ENTRIES`\n\n### Payment Middleware for Plugins\nA new x402 payment middleware (#6114) has been implemented to protect plugin routes with EVM and Solana payment verification:\n\n```typescript\napp.use('/api/plugins/:pluginId/*', applyPaymentProtection({\n config: 'base_usdc', // Or 'solana_usdc', 'polygon_usdc'\n amount: '0.01', // In USD\n facilityPaymentId: 'plugin:example:feature'\n}));\n```\n\n## Bug Fixes\n\n### Entity Names Array Serialization\nFixed critical entity creation failures (#6133) by normalizing the `names` field for PostgreSQL:\n\n```typescript\n// Before: These could fail depending on input type\nconst entity1 = await storage.createEntity({ names: new Set(['name1', 'name2']) });\nconst entity2 = await storage.createEntity({ names: 'single-name' });\n\n// Now: All formats are normalized properly before database operations\n```\n\nThe fix includes extensive test coverage for various input formats including Sets, Maps, strings, and mixed-type arrays.\n\n### Technical details:\n- Added `normalizeEntityNames()` in `plugin-sql/src/base.ts`\n- Applied normalization in `createEntities()` and `updateEntity()`\n- Enhanced error logging with stack traces\n- Added 9 comprehensive test cases covering edge cases\n\n## API Changes\n\n### @elizaOS/react Package\nA new headless React hooks package is in development (#6093) to enable external developers to build custom UIs with full type safety:\n\n```tsx\nimport { QueryClient, QueryClientProvider } from '@tanstack/react-query';\nimport { ElizaReactProvider, useAgents, useStartAgent } from '@elizaOS/react';\n\nfunction AgentList() {\n const { data: agents, isLoading } = useAgents();\n const startAgent = useStartAgent({\n onSuccess: () => console.log('Agent started!'),\n });\n\n return (\n
\n {agents?.map((agent) => (\n
\n \n
\n ))}\n
\n );\n}\n```\n\n### Runtime API Extensions\nThe `IAgentRuntime` interface has been extended with:\n- `dynamicPromptExecFromState`: For schema-driven prompt execution\n- `skipMigrations`: Optional parameter for `initialize()`\n\n## Social Media Integrations\n\n### Farcaster Plugin\nUsers are reporting issues with the Farcaster plugin when reading FID from environment files. This is being investigated with priority as part of our social media integrations overhaul. A fix is expected in the next release.\n\n### Discord Plugin\nWork is ongoing to implement a unified messaging API for the Discord plugin (#24 in elizaos-plugins/plugin-discord). This refactoring will align the Discord plugin with the standardized messaging interface used by other social connectors.\n\n## Model Provider Updates\n\n### OpenRouter Integration\nA new PR (#6142) adds OpenRouter embedding options to the CLI, extending our model provider support:\n\n```bash\n# New CLI option\neliza embed --provider openrouter --model=openrouter/whatever/embedding \"Your text to embed\"\n```\n\n### Eleven Labs Integration\nThe Scribe v2 API with Voice Activity Detection is now supported, providing automatic speech segmentation based on silence detection. This significantly improves the voice experience in ElizaOS agents.\n\n## Breaking Changes\n\n### Event Handling Changes\n`EventType.MESSAGE_RECEIVED` has been removed from bootstrap. Plugins using this event type need to be updated to use the service approach instead:\n\n```typescript\n// Before (no longer works)\nthis.events.on(EventType.MESSAGE_RECEIVED, this.handleMessage);\n\n// After (recommended approach)\nthis.registerHandler({\n service: 'messaging',\n method: 'onMessage',\n handler: this.handleMessage\n});\n```\n\n### Migration Guide for x402 Implementation\nFor plugins implementing the new payment middleware, you'll need to:\n\n1. Define payment configurations in your plugin's `payment-config.ts`\n2. Use `createPaymentAwareHandler` for routes requiring payment\n3. Set up verification for either EVM (EIP-712/ERC-3009) or Solana depending on your target chain\n\nSee the comprehensive README in the x402 folder for detailed implementation guidelines.\n\n---\n\nThe team is actively working on the upcoming ElizaCloud release (confirmed for year-end) and the Babylon release which is expected \"much sooner.\" Development of an agent game for the Devconnect event is also underway.\n\nPlease direct any questions to the #core-devs channel on Discord.",
"source_references": [
"2025-11-12\n---\n2025-11-11.md\n---\n# elizaOS Discord - 2025-11-11\n\n## Overall Discussion Highlights\n\n### Token Migration\n- Migration from AI16Z tokens to ElizaOS tokens is in full swing\n- A snapshot is scheduled for November 11, 2023, at 11:40 UTC, after which no new AI16Z purchases can be migrated\n- Users reported technical issues with the migration portal, including \"max amount reached\" errors\n- Cross-chain bridging functionality exists to move ElizaOS tokens from Solana to Base network\n- Some users experiencing difficulties with wallet connectivity during migration process\n\n### Exchange Listings & Tokenomics\n- Gate.io trading starting soon with ElizaOS\n- Bybit listing mentioned for November 12\n- The token has a large supply (11B) which some users questioned\n- No single-sided staking is currently available, but liquidity providing (LP) is an option\n\n### Development Updates\n- ElizaOS is an open-source project hosted on GitHub (https://github.com/elizaos/eliza) where anyone can contribute\n- R0am deployed an OTC agent to Vercel with database assistance from cjft\n- Discussion about Eleven Labs' Scribe v2 API with Voice Activity Detection capabilities\n- Technical issue raised regarding EventType.MESSAGE_RECEIVED being removed from bootstrap\n- Successful plugin conversion to use service approach rather than relying on removed event type\n\n## Key Questions & Answers\n\n**Q: Can I contribute to this framework?** (Momotaro) \nA: \"It's open source, anyone can work on it\" (Odilitime)\n\n**Q: Are there any plans for elizaos to enter the cex spot market?** (Noryfy) \nA: \"ElizaOS listed tomorrow in Gate io\" (bct)\n\n**Q: Any plan for this huge supply?** (iory yagamy) \nA: \"It just felt right\" (Kenk)\n\n**Q: Is there any staking for ElizaOS?** (WatermelonSugar) \nA: \"You can LP, no single sided staking atm\" (Kenk)\n\n**Q: How can I convert AI16Z tokens in Trust Wallet to ElizaOS?** (Jesse Spencer) \nA: \"You'll have to move your tokens to one of the supported wallets to do the migration\" (Borko)\n\n**Q: EventType.MESSAGE_RECEIVED was removed from bootstrap but I think we need it back** (Odilitime) \nA: \"We do not use it for message handling anymore, but it can be usefull for other plugin to listen it, true.\" (Stan \u26a1)\n\n## Community Help & Collaboration\n\n1. **Migration Support**\n - Kenk helped ole with bridging elizaOS from Solana to Base, suggesting creating a support ticket and manually adding the Base contract address to wallet\n - Omid sa clarified migration timeline and snapshot details for wuming\n - Borko suggested typing in the exact amount instead of using \"max\" button to resolve migration errors\n\n2. **Development Assistance**\n - cjft provided R0am with Neon database credentials for OTC agent deployment\n - Stan \u26a1 helped Odilitime understand current usage patterns for event handling, leading to successful plugin conversion\n\n3. **Technical Guidance**\n - Borko advised Jesse Spencer to move AI16Z tokens to supported wallets for migration\n - Odilitime provided GitHub link and confirmed anyone can work on the ElizaOS framework\n\n## Action Items\n\n### Technical\n- Fix the \"max amount reached\" error in the migration portal (Rocket Hamster)\n- Resolve bridging issues from Solana to Base (ole)\n- Add PostgreSQL database to OTC agent deployment (R0am)\n- Convert plugin to use service instead of EventType.MESSAGE_RECEIVED (Odilitime)\n- Resolve issue with reading FID from env file when using Farcaster plugin with Eliza (Pr\u2b55f. J)\n\n### Documentation\n- Create clear migration instructions for Coinbase wallet users (terrapin)\n- Update and align communication across platforms regarding snapshot timing (wuming)\n- Document Voice Activity Detection features in Eleven Labs Scribe v2 API (cjft)\n\n### Feature\n- Implement single-sided staking for ElizaOS (WatermelonSugar)\n- Address concerns about token supply size (iory yagamy)\n- Create or provide a 3D model of Eliza for use as referee/validator agent in neural fight games (Amir)\n---\n2025-11-10.md\n---\n# elizaOS Discord - 2025-11-10\n\n**Date: November 10, 2025**\n\n## Overall Discussion Highlights\n\n### Token Migration Progress\n- **Exchange Status**: Kucoin is actively working on the migration while Gate.io is awaiting feedback but expected to complete \"this week\"\n- **Withdrawal Status**: Gate.io has paused withdrawals, indicating migration is underway\n- **Team Confirmation**: Borko and Kenk confirmed that Gate.io has received all necessary information for the swap\n- **Exchange Timeline**: Most exchanges are expected to address the migration this week\n- **Non-Supporting Exchanges**: Users on platforms like Kraken Pro may need to withdraw to EOA wallets and follow migration portal steps\n\n### Tokenomics Concerns\n- **Supply Increase**: Community members expressed concern about the increased token supply (from 1B to 11B)\n- **Team Clarification**: Only 13% is initially added to circulation, with team tokens locked for one year\n- **Price Discussion**: Some users noted declining price despite broader market uptrend\n- **Long-term Outlook**: Others remain optimistic, pointing to active GitHub development\n\n### Product Development\n- **ElizaCloud Timeline**: Borko confirmed release by year-end\n- **Babylon Release**: Coming \"much sooner\" than ElizaCloud\n- **Agent Game**: Team focused on developing an \"agent game\" for upcoming Devconnect event\n- **OTC Agent**: Development team working on deploying an OTC agent, requiring PostgreSQL database\n- **Next.js Application**: Team using Vercel for hosting but experiencing build errors\n\n### Community Initiatives\n- **Content Creation**: Lopez working on new videos about the migration process\n- **Competition Ideas**: DorianD suggested implementing competitions for ElizaCloud with rewards for agents generating highest payments or reputation scores\n- **Youth Entrepreneurship**: Discussion about creating opportunities for young entrepreneurs to generate income through AI agents by summer 2026\n\n## Key Questions & Answers\n\n**Q: When will Gate.io complete the token swap?** \nA: Gate should be completing the migration this week (Borko)\n\n**Q: What benefits did the community get from this migration?** \nA: See the mirror article; only 10% adds to circulation, team tokens locked for one year (Kenk and Omid sa)\n\n**Q: How to migrate/convert AI16Z to ElizaOS on Kraken Pro?** \nA: Kraken Pro likely isn't supporting the migration; users may need to withdraw to EOA wallet and follow migration portal steps (Kenk)\n\n**Q: When will ElizaCloud and Babylon be released?** \nA: Cloud by end of year, Babylon much sooner (Borko)\n\n**Q: What's the status of exchange migrations?** \nA: Kucoin is working on it, Gate is waiting to hear back, and most exchanges are addressing it this week (Shaw)\n\n## Community Help & Collaboration\n\n1. **Token Migration Support**\n - **Helper**: The Light\n - **Helpee**: Tenjoao\n - **Issue**: Unable to add wallet for token swap on website\n - **Resolution**: Suggested toggling web2 settings\n\n2. **Contract Address Assistance**\n - **Helper**: 0xTDL \u26a1\n - **Helpee**: Phobia \ud83e\ude96\n - **Issue**: Needed new contract address for Base ElizaOS\n - **Resolution**: Provided the contract address\n\n3. **Exchange Migration Clarification**\n - **Helper**: \u043d\u0438\u043a\u0438\u0442\u0430\n - **Helpee**: Numerical Methods\n - **Issue**: AI16Z tokens disappeared from Bybit exchange\n - **Resolution**: Explained tokens should convert automatically when ElizaOS spot trading becomes available\n\n4. **Scam Warning**\n - **Helper**: Kenk\n - **Helpee**: Stanislav Tiutiunnyk\n - **Issue**: User appeared distressed about Binance not exchanging tokens\n - **Resolution**: Warned that the situation described was likely a scam and advised against following shared links\n\n5. **Development Assistance**\n - **Helper**: cjft\n - **Helpee**: R0am | tip.md\n - **Issue**: Needed hosting for Next.js app and database\n - **Resolution**: Offered Vercel hosting and identified build errors preventing deployment\n\n## Action Items\n\n### Technical Tasks\n1. **Fix broken \"Partners\" link in migration page** (Mentioned by Dontrage)\n - The link from \"read more about migration\" to Partners page returns 404\n\n2. **Complete exchange migrations** (Mentioned by Multiple users)\n - Finalize token migration on Gate.io and other exchanges\n\n3. **Add contract addresses to foundation site** (Mentioned by Odilitime)\n - Team waiting for community to add CAs to foundation site\n\n4. **Implement solution for partner badge validation** (Mentioned by Kenk)\n - Current Collab.land verification tool only supports Solana and Base, causing problems for partners who migrated to BNB or ETH\n\n5. **Fix build errors in Next.js application** (Mentioned by cjft)\n - npm run build failing, preventing deployment\n\n6. **Review pull requests #6139 and #6141** (Mentioned by Stan \u26a1)\n - PRs need review from team members\n\n7. **Provide PostgreSQL database connection string** (Mentioned by R0am | tip.md)\n - Need Supabase or Neon DB for deployment\n\n### Documentation Needs\n1. **Create migration guide for non-supporting exchanges** (Mentioned by Kenk)\n - Instructions for users on exchanges not supporting automatic migration\n\n2. **Update CoinGecko information** (Mentioned by linkupeithme)\n - Add link to ElizaOS website on CoinGecko\n\n### Feature Requests\n1. **Create video content about migration** (Mentioned by Lopez)\n - Develop educational content explaining the migration process and its importance\n\n2. **Organize community spaces** (Mentioned by Kenk)\n - Set up informal community spaces for discussion\n\n3. **Complete agent game development** (Mentioned by Shaw)\n - Finish development in time for Devconnect event\n\n4. **Create competitions for ElizaCloud** (Mentioned by DorianD)\n - Implement contests for agents with highest x402 payments and 8004 reputation scores\n\n5. **Implement token snapshot and airdrop mechanism** (Mentioned by DorianD)\n - Create incentives for users to migrate tokens through airdrops\n\n6. **Develop showcase of young entrepreneurs using AI agents** (Mentioned by DorianD)\n - Goal to have dozen GenZ users earning income through Eliza agents by summer 2026\n\n7. **Improve agent and feed generation quality** (Mentioned by Shaw)\n - Need additional person to assist with quality improvements\n---\n2025-11-09.md\n---\n# elizaOS Discord - 2025-11-09\n\n## Overall Discussion Highlights\n\n### Token Migration\n- The community is experiencing confusion and frustration regarding the AI16z to ElizaOS token migration\n- Users report tokens being frozen on centralized exchanges (KuCoin, Gate.io, Bybit) with limited communication\n- Team member Borko confirmed migrations on KuCoin and Gate should be completed \"this week\"\n- Bybit is expected to list ElizaOS on November 12th\n- There's a plan to address arbitrage issues affecting the token price chart, though details are being kept private for strategic reasons\n- The team is waiting for exchanges to come back online, with delays partly attributed to the weekend\n\n### Technical Discussions\n- Jin shared information about affordable mini PCs with 128GB memory (now around $2k, down from $6k) for running large LLMs locally\n- Specific product links were shared for GMKtec, Minisforum, and Bosgame mini PCs\n- Discussion about monitoring smart contract events and broadcasting them on social media platforms\n- DorianD explored potential future wearable technology form factors, including device-to-device communication via Bluetooth/infrared\n- Concept of agent-to-agent encrypted communications was discussed\n\n### Project Direction\n- Shaw initiated a discussion about repositioning Eliza's character in official content to be taken more seriously and respected\n- Team members agreed to avoid sexualization of Eliza in official materials\n- There was mention of a cryptocurrency project (ICP) that recovered after announcing reduced inflation and deflationary cloud nodes\n\n## Key Questions & Answers\n\n**Q: Can AI16z be changed for ElizaOS directly through Jupiter?** \nA: No, you can't swap AI16z to ElizaOS directly on Jupiter. You'll need to bridge/migrate first, then swap on the supported chain where ElizaOS is listed. (Bertram)\n\n**Q: When will KuCoin and Gate.io migrations be completed?** \nA: Kucoin and Gate migrations should be done this week. (Borko)\n\n**Q: When will Bybit list ElizaOS?** \nA: ElizaOS will be listed on Bybit on November 12. (Omid sa)\n\n**Q: What's the hold up with the exchanges?** \nA: Weekend mostly. (Shaw)\n\n**Q: What's the best practice to monitor a smart contract event and broadcast it on Farcaster and Twitter?** \nA: Set up a custom event that fires, then handle the custom event with a function that uses the Twitter or Farcaster features. (TH3H4RM1N4T0R)\n\n**Q: Should we avoid sexualizing Eliza in official content?** \nA: Yes. (Agreed by multiple team members including Odilitime and Stan)\n\n## Community Help & Collaboration\n\n- **Hardware Recommendations**: Jin shared detailed information about affordable mini PCs for running large language models locally, providing specific product links and noting the significant price drops from $6k to around $2k\n \n- **Migration Guidance**: Bertram explained to Leandro Corazza that direct swapping of AI16z to ElizaOS on Jupiter isn't possible, clarifying that users need to bridge/migrate first\n\n- **Technical Solution**: TH3H4RM1N4T0R suggested using custom events and handlers to rferrari for monitoring smart contract events and broadcasting them on social media\n\n- **Exchange Updates**: Omid sa provided a specific date (November 12) for ElizaOS listing on Bybit, helping to address community uncertainty\n\n- **Migration Status**: Borko addressed multiple users' concerns about frozen tokens on exchanges, confirming migrations should be completed \"this week\" and acknowledging they are \"technically challenging\"\n\n## Action Items\n\n### Technical\n- **Stop arbitrage affecting token price** (Mentioned by Shaw)\n - Implement undisclosed plan to address arbitrage issues impacting the token's price chart\n \n- **Exchange relisting** (Mentioned by Shaw)\n - Work to get exchanges back online for the token\n \n- **Remove inappropriate content** (Mentioned by cjft)\n - Remove inappropriate content while ensuring payments to commenters are completed first to avoid scamming accusations\n \n- **Explore custom event handling** (Mentioned by TH3H4RM1N4T0R)\n - Set up a system that fires custom events when smart contract events occur and handles them with functions that use Twitter/Farcaster features\n \n- **Research mini PCs for LLM deployment** (Mentioned by Jin)\n - Investigate affordable options like GMKtec, Minisforum, and Bosgame mini PCs for running large language models locally\n\n### Documentation\n- **Create migration documentation** (Mentioned by Multiple users)\n - Develop clear documentation about the CEX migration process and timelines\n \n- **Improve communication channels** (Mentioned by iory yagamy, AlexZ)\n - Enhance communication channels for migration updates\n \n- **Reposition Eliza's character** (Mentioned by Shaw)\n - Update official content to present Eliza's character in a more serious and respected manner\n\n### Feature\n- **Implement agent-to-agent encrypted communications** (Mentioned by DorianD)\n - Develop a system where agents can exchange public keys to enable encrypted communications regardless of the messaging platform's security\n \n- **Migration support** (Mentioned by DorianD)\n - Ensure CollabLAMD works for new coins to facilitate migration\n \n- **\"Relaunch\" execution** (Mentioned by DannyNOR NoFapArc)\n - Successfully execute the project relaunch with fixed liquidity and solid announcements\n---\n2025-11-11.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-11-11\n---\nGitHub Activity Summary\n---\nFrom November 11, 2025 to November 12, 2025, the elizaOS/eliza repository showed moderate activity with 1 new pull request that was successfully merged. There were no new issues reported during this period. The repository maintained an active contributor base with 5 contributors participating in development activities.\n---\nPull Requests\n---\nPR #6142 titled 'fix: Add openrouter embedding option in CLI' by @Neysixx is open\n---\nhttps://github.com/elizaOS/eliza/pull/6142\n---\nPR #6139 titled 'fix: RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled' is merged\n---\nhttps://github.com/elizaOS/eliza/pull/6139\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-11.md\n---\n# Daily Report - 2025-11-11\n\n## GitHub Activity Summary\n- From November 11, 2025 to November 12, 2025, the elizaOS/eliza repository showed moderate activity with 1 new pull request that was successfully merged. There were no new issues reported during this period. The repository maintained an active contributor base with 5 contributors participating in development activities.\n\n## Pull Requests\n- PR #6142 titled 'fix: Add openrouter embedding option in CLI' by @Neysixx is open (Source: [https://github.com/elizaOS/eliza/pull/6142](https://github.com/elizaOS/eliza/pull/6142))\n- PR #6139 titled 'fix: RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled' is merged (Source: [https://github.com/elizaOS/eliza/pull/6139](https://github.com/elizaOS/eliza/pull/6139))\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-11.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-11-11\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Discord Chat Analysis for \ud83d\udcac-discussion\n\n## 1. Summary\nThe discussion primarily revolves around the migration from AI16Z tokens to the new ElizaOS tokens. Users are asking about the migration process, timelines, and technical issues they're encountering. Key technical points include:\n\n- ElizaOS is an open-source project hosted on GitHub (https://github.com/elizaos/eliza) where anyone can contribute\n- A migration portal is being used to convert AI16Z tokens to ElizaOS tokens\n- There's a snapshot scheduled for November 11, 2023, at 11:40 UTC, after which no new AI16Z purchases can be migrated\n- Some users reported technical issues with the migration portal, including \"max amount reached\" errors\n- Cross-chain bridging functionality exists to move ElizaOS tokens from Solana to Base network\n- Exchange listings are occurring, with Gate.io trading starting soon and mentions of Bybit listing on November 12\n- The token has a large supply (11B) which some users questioned\n- No single-sided staking is currently available, but liquidity providing (LP) is an option\n\nThe community appears to be transitioning from the old token to the new one while dealing with various technical challenges and market concerns.\n\n## 2. FAQ\nQ: Can I contribute to this framework? (asked by Momotaro) A: It's open source, anyone can work on it (answered by Odilitime)\nQ: Do I need to create a new issue or find an issue? (asked by Momotaro) A: Either (answered by Odilitime)\nQ: Why keep dumping? (asked by yourloyalboi) A: Unanswered\nQ: Does it matter if I swap old token with new one without migrating? (asked by chomppp) A: Unanswered\nQ: Is there a fee to convert tokens? (asked by Maziyar1982) A: Unanswered\nQ: Are there any plans for elizaos to enter the cex spot market? (asked by Noryfy) A: ElizaOS listed tomorrow in Gate io (answered by bct)\nQ: Why is the price going down and down? (asked by tarotaro) A: Unanswered\nQ: When bidget migration? (asked by Weth) A: It's underway from what we can see (answered by Kenk)\nQ: Any plan for this huge supply? (asked by iory yagamy) A: It just felt right (answered by Kenk)\nQ: Is there any staking for ElizaOS? (asked by WatermelonSugar) A: You can LP, no single sided staking atm (answered by Kenk)\nQ: What does \"max amount reached\" error mean when migrating? (asked by Rocket Hamster) A: Unanswered\nQ: Will Bithumb and Coinone provide migration support? (asked by mykn22) A: Ask in #exchange-support (answered by Kenk)\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: Momotaro | Context: Asking about contributing to the ElizaOS framework | Resolution: Provided GitHub link and confirmed anyone can work on it\nHelper: Kenk | Helpee: ole | Context: Issue bridging elizaOS from Solana to Base with error \"low amount of tokens to complete transfer\" | Resolution: Suggested creating a support ticket and manually adding the Base contract address to wallet\nHelper: Kenk | Helpee: WatermelonSugar | Context: Asking about staking options for ElizaOS | Resolution: Informed that LP is available but no single-sided staking currently\nHelper: Omid sa | Helpee: wuming | Context: Confusion about migration timeline and snapshot | Resolution: Explained the snapshot timing and migration cutoff details\nHelper: Borko | Helpee: Rocket Hamster | Context: Error when trying to migrate tokens | Resolution: Suggested typing in the exact amount instead of using \"max\" button\n\n## 4. Action Items\nTechnical: Fix the \"max amount reached\" error in the migration portal | Description: Multiple users reporting this error when trying to migrate tokens | Mentioned By: Rocket Hamster\nTechnical: Resolve bridging issues from Solana to Base | Description: User experienced tokens being withdrawn but not received on Base | Mentioned By: ole\nDocumentation: Create clear migration instructions for Coinbase wallet users | Description: User unable to find Coinbase wallet option when connecting | Mentioned By: terrapin\nDocumentation: Update and align communication across platforms | Description: Discrepancy between Discord and Twitter announcements about snapshot | Mentioned By: wuming\nFeature: Implement single-sided staking for ElizaOS | Description: Users want staking options without LP risk exposure | Mentioned By: WatermelonSugar\nTechnical: Address concerns about token supply size | Description: Questions about the large 11B supply and its impact on value | Mentioned By: iory yagamy\n---\n1300025221834739744\n---\n\ud83d\udcac-coders\n---\n# Discord Chat Analysis for \ud83d\udcac-coders Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation includes brief exchanges about wallet connectivity issues for token migration, a question about using the Farcaster plugin with Eliza and reading FID from an environment file, and an inquiry about a 3D model of Eliza for use in neural fight games. There's also discussion about a mini PC purchase (GMKtec Ryzen AI mini PC) that's compared to a \"dgx spark\" at half the cost. The chat lacks detailed technical problem-solving or implementation discussions, with most messages being brief inquiries or comments without extensive follow-up.\n\n## 2. FAQ\nQ: How can I convert AI16Z tokens in Trust Wallet to ElizaOS? (asked by Jesse Spencer) A: You'll have to move your tokens to one of the supported wallets to do the migration (answered by Borko)\nQ: Anyone using Farcaster plugin with Eliza? Having trouble reading my fid from env file. (asked by Pr\u2b55f. J) A: Unanswered\nQ: Anyone got a 3D model of eliza? I want to use it as referee (validator agent) in neural fight games. (asked by Amir) A: Unanswered\n\n## 3. Help Interactions\nHelper: Borko | Helpee: Jesse Spencer | Context: User had AI16Z tokens in Trust Wallet and couldn't connect wallet on main website to convert to ElizaOS | Resolution: Advised to move tokens to supported wallets for migration\nHelper: pnxzy | Helpee: User with ID 1237830763492151428 | Context: Following up on a previous unresolved issue | Resolution: Unknown (no response in transcript)\n\n## 4. Action Items\nTechnical: Resolve issue with reading FID from env file when using Farcaster plugin with Eliza | Mentioned By: Pr\u2b55f. J\nFeature: Create or provide a 3D model of Eliza for use as referee/validator agent in neural fight games | Mentioned By: Amir\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe chat segment is extremely brief, containing only a single message from user Broccolex who shared a Twitter/X link from the Ethereum account. The link format suggests it's a post from the official Ethereum account, but no discussion, technical content, or problem-solving occurred in this segment. The timestamp indicates the message was sent at 17:51, but there was no follow-up conversation or engagement from other users in the provided transcript.\n\n## 2. FAQ\nNo questions were asked in this chat segment.\n\n## 3. Help Interactions\nNo help interactions occurred in this chat segment.\n\n## 4. Action Items\nNo action items were identified in this chat segment.\n---\n1377726087789940836\n---\ncore-devs\n---\n# Discord Chat Analysis - \"core-devs\" Channel\n\n## 1. Summary\nThe chat segment covers a brief period of developer interactions focused on deployment and technical implementation details. R0am deployed an OTC agent to Vercel and requested database setup assistance from another developer, who responded by providing a Neon database. There was also discussion about Eleven Labs' Scribe v2 API, which offers Voice Activity Detection with automatic speech segmentation based on silence detection, providing a streamlined developer experience. Additionally, Odilitime raised an issue about EventType.MESSAGE_RECEIVED being removed from bootstrap, which led to a discussion about plugin conversion. Odilitime successfully converted the plugin to use a service approach rather than relying on the removed event type, confirming that moving forward with newer patterns was more effective than maintaining backward compatibility.\n\n## 2. FAQ\nQ: Can you check to add the PG DB? (asked by R0am | tip.md) A: nice, DMed neon db (answered by cjft)\nQ: EventType.MESSAGE_RECEIVED was removed from bootstrap but I think we need it back (asked by Odilitime) A: We do not use it for message handling anymore, but it can be usefull for other plugin to listen it, true. (answered by Stan \u26a1)\n\n## 3. Help Interactions\nHelper: cjft | Helpee: R0am | tip.md | Context: Needed a PostgreSQL database for OTC agent deployment | Resolution: Provided Neon database credentials via DM\nHelper: Stan \u26a1 | Helpee: Odilitime | Context: Dealing with removed EventType.MESSAGE_RECEIVED from bootstrap | Resolution: Explained current usage patterns, leading Odilitime to successfully convert plugin to use service approach\n\n## 4. Action Items\nType: Technical | Description: Add PostgreSQL database to OTC agent deployment | Mentioned By: R0am | tip.md\nType: Technical | Description: Convert plugin to use service instead of EventType.MESSAGE_RECEIVED | Mentioned By: Odilitime\nType: Documentation | Description: Document Voice Activity Detection features in Eleven Labs Scribe v2 API | Mentioned By: cjft\n---\n2025-11-11.md\n---\n# elizaOS Discord - 2025-11-11\n\n## Overall Discussion Highlights\n\n### Token Migration\n- Migration from AI16Z tokens to ElizaOS tokens is in full swing\n- A snapshot is scheduled for November 11, 2023, at 11:40 UTC, after which no new AI16Z purchases can be migrated\n- Users reported technical issues with the migration portal, including \"max amount reached\" errors\n- Cross-chain bridging functionality exists to move ElizaOS tokens from Solana to Base network\n- Some users experiencing difficulties with wallet connectivity during migration process\n\n### Exchange Listings & Tokenomics\n- Gate.io trading starting soon with ElizaOS\n- Bybit listing mentioned for November 12\n- The token has a large supply (11B) which some users questioned\n- No single-sided staking is currently available, but liquidity providing (LP) is an option\n\n### Development Updates\n- ElizaOS is an open-source project hosted on GitHub (https://github.com/elizaos/eliza) where anyone can contribute\n- R0am deployed an OTC agent to Vercel with database assistance from cjft\n- Discussion about Eleven Labs' Scribe v2 API with Voice Activity Detection capabilities\n- Technical issue raised regarding EventType.MESSAGE_RECEIVED being removed from bootstrap\n- Successful plugin conversion to use service approach rather than relying on removed event type\n\n## Key Questions & Answers\n\n**Q: Can I contribute to this framework?** (Momotaro) \nA: \"It's open source, anyone can work on it\" (Odilitime)\n\n**Q: Are there any plans for elizaos to enter the cex spot market?** (Noryfy) \nA: \"ElizaOS listed tomorrow in Gate io\" (bct)\n\n**Q: Any plan for this huge supply?** (iory yagamy) \nA: \"It just felt right\" (Kenk)\n\n**Q: Is there any staking for ElizaOS?** (WatermelonSugar) \nA: \"You can LP, no single sided staking atm\" (Kenk)\n\n**Q: How can I convert AI16Z tokens in Trust Wallet to ElizaOS?** (Jesse Spencer) \nA: \"You'll have to move your tokens to one of the supported wallets to do the migration\" (Borko)\n\n**Q: EventType.MESSAGE_RECEIVED was removed from bootstrap but I think we need it back** (Odilitime) \nA: \"We do not use it for message handling anymore, but it can be usefull for other plugin to listen it, true.\" (Stan \u26a1)\n\n## Community Help & Collaboration\n\n1. **Migration Support**\n - Kenk helped ole with bridging elizaOS from Solana to Base, suggesting creating a support ticket and manually adding the Base contract address to wallet\n - Omid sa clarified migration timeline and snapshot details for wuming\n - Borko suggested typing in the exact amount instead of using \"max\" button to resolve migration errors\n\n2. **Development Assistance**\n - cjft provided R0am with Neon database credentials for OTC agent deployment\n - Stan \u26a1 helped Odilitime understand current usage patterns for event handling, leading to successful plugin conversion\n\n3. **Technical Guidance**\n - Borko advised Jesse Spencer to move AI16Z tokens to supported wallets for migration\n - Odilitime provided GitHub link and confirmed anyone can work on the ElizaOS framework\n\n## Action Items\n\n### Technical\n- Fix the \"max amount reached\" error in the migration portal (Rocket Hamster)\n- Resolve bridging issues from Solana to Base (ole)\n- Add PostgreSQL database to OTC agent deployment (R0am)\n- Convert plugin to use service instead of EventType.MESSAGE_RECEIVED (Odilitime)\n- Resolve issue with reading FID from env file when using Farcaster plugin with Eliza (Pr\u2b55f. J)\n\n### Documentation\n- Create clear migration instructions for Coinbase wallet users (terrapin)\n- Update and align communication across platforms regarding snapshot timing (wuming)\n- Document Voice Activity Detection features in Eleven Labs Scribe v2 API (cjft)\n\n### Feature\n- Implement single-sided staking for ElizaOS (WatermelonSugar)\n- Address concerns about token supply size (iory yagamy)\n- Create or provide a 3D model of Eliza for use as referee/validator agent in neural fight games (Amir)\n---\n2025-11-12.md\n---\nFile not found\n---\n2025-11-02.md\n---\n# elizaos/eliza Weekly Report (Nov 2 - 8, 2025)\n\n## \ud83d\ude80 Highlights\nThis week's activity focused on initiating new features and planning for future enhancements. Development began on core security and runtime improvements, with new pull requests opened to implement entity-level row-level security and to add an ElizaOS reference to the runtime. Concurrently, several new issues were created to guide future work, focusing on core performance through parallel actions and background tasks, as well as user engagement with a points and leaderboard system. The period was characterized by laying the groundwork for upcoming features rather than completing existing ones.\n\n## \ud83d\udee0\ufe0f Key Developments\nWhile no major features were completed this period, work was initiated on two key fronts through new pull requests:\n\n- **Security Framework:** A new pull request, [#6107](https://github.com/elizaos/eliza/pull/6107), was opened to begin the implementation of entity-level row-level security (RLS). This work is complemented by a new issue, [#6112](https://github.com/elizaos/eliza/issues/6112), opened for discussion on the same topic.\n- **Runtime Enhancements:** To improve the runtime environment, work was started in [#6111](https://github.com/elizaos/eliza/pull/6111) to add an ElizaOS reference, a foundational step for future runtime capabilities.\n\n## \ud83d\udc1b Issues & Triage\nNo issues were closed this week. The focus was on opening new discussions to shape the project's direction.\n\n- **New & Active Issues:** Four significant new issues were opened, outlining key areas for future development:\n - **Core Functionality & Performance:** Discussions were started around improving the system's operational capabilities with proposals for \"Parallel actions\" ([#6108](https://github.com/elizaos/eliza/issues/6108)) and \"Background tasks\" ([#6109](https://github.com/elizaos/eliza/issues/6109)).\n - **User Engagement & Security:** Future enhancements were proposed for user interaction via a \"Points / Leaderboard\" system ([#6110](https://github.com/elizaos/eliza/issues/6110)) and for data security with \"Entity-level RLS\" ([#6112](https://github.com/elizaos/eliza/issues/6112)).\n\n## \ud83d\udcac Community & Collaboration\nThe provided reports indicate a focus on initiating new work streams through the opening of pull requests and issues. There were no specific details in the reports regarding high-volume discussions or collaborative reviews during this period.\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 12 new PRs (4 merged), 24 new issues, and 14 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\": null,\n \"state\": \"OPEN\",\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\": null,\n \"state\": \"OPEN\",\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 \\n \\n \\n \\n \\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
Loading...
;\\n\\n return (\\n
\\n {agents?.map((agent) => (\\n
\\n
{agent.name}
\\n \\n
\\n ))}\\n
\\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\\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> 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).\\n\",\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\\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> 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).\\n\",\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_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\\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> 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).\\n\",\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 \"id\": \"PR_kwDOMT5cIs6xVNKQ\",\n \"title\": \"feat: Framework for adjusting prompts to best fix model contexts\",\n \"author\": \"odilitime\",\n \"number\": 6113,\n \"body\": \"# Risks\\r\\n\\r\\nLow, new feature, uses some memory but I put configurable limit on it\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nIt add a dynamic prompt execution system\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\n\\r\\nPeople may use models with lower context and get hallucination, this helps detect when the context is blown out.\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\nMy changes require a change to the project documentation.\\n\\n\\n---\\n\\n> [!NOTE]\\n> Introduces a schema-based dynamic prompt executor with validation/retries/metrics and replaces ad-hoc prompting in message flows, plus supporting types/utils and test updates.\\n> \\n> - **Core Runtime**:\\n> - Add `runtime.dynamicPromptExecFromState(...)` for schema-driven prompt execution (XML/JSON parsing, UUID validation codes, retries, Handlebars state injection, token estimations).\\n> - Track execution metrics via `modelSchemaMetrics` and `modelMetrics` with optional LRU eviction (`DYNAMIC_PROMPT_MAX_ENTRIES`) and retry policy (`VALIDATION_LEVEL`).\\n> - Expose metrics getters/clearers; helper methods for cache/keys; minor logging adjustments.\\n> - **Message Service**:\\n> - Replace manual `useModel` + XML parsing with `dynamicPromptExecFromState` in:\\n> - `shouldRespond` evaluation (small model).\\n> - Single-shot handler (requires `thought`, `actions`).\\n> - Multi-step decision loop and final summary.\\n> - Improve error logging and minor flow tweaks.\\n> - **Types/Utils**:\\n> - Export `SchemaRow` and `State` from `types`; extend `IAgentRuntime` with `dynamicPromptExecFromState`.\\n> - Export `upgradeDoubleToTriple` and `composeRandomUser` from `utils`.\\n> - **Tests/Test Utils**:\\n> - Update `message-service` tests to mock `dynamicPromptExecFromState` responses.\\n> - Add mock implementation in test runtime; minor logger formatting changes.\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5905b5f9ab86dd7b7d727d92060575f42a8fc707. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-11-04T05:53:02Z\",\n \"mergedAt\": null,\n \"additions\": 807,\n \"deletions\": 87\n }\n ],\n \"codeChanges\": {\n \"additions\": 1648,\n \"deletions\": 61,\n \"files\": 12,\n \"commitCount\": 93\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\": \"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: 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 \"topContributors\": [\n {\n \"username\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 304.32927228220717,\n \"prScore\": 303.78927228220715,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.54,\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\": \"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\": 196.417158133888,\n \"prScore\": 181.37715813388797,\n \"issueScore\": 0,\n \"reviewScore\": 14.5,\n \"commentScore\": 0.54,\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\": \"0xbbjoker\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n \"totalScore\": 163.80804915829833,\n \"prScore\": 153.80804915829833,\n \"issueScore\": 0,\n \"reviewScore\": 10,\n \"commentScore\": 0,\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\": \"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\": 36,\n \"prScore\": 0,\n \"issueScore\": 36,\n \"reviewScore\": 0,\n \"commentScore\": 0,\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\": 34.77887055267063,\n \"prScore\": 34.57887055267063,\n \"issueScore\": 0,\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\": \"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\": \"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\": \"samarth30\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\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\": \"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\": 12,\n \"mergedPRs\": 4,\n \"newIssues\": 24,\n \"closedIssues\": 4,\n \"activeContributors\": 14\n}\n---\n[\"standujar_day_2025-11-06\", \"standujar\", \"day\", \"2025-11-06\", \"standujar: No activity today.\", \"2025-11-09T23:14:15.389Z\"]\n[\"borisudovicic_day_2025-11-06\", \"borisudovicic\", \"day\", \"2025-11-06\", \"borisudovicic: Today, borisudovicic initiated a new feature development by creating an issue for a \\\"Polymarket Plugin\\\" in elizaos/eliza (#6136), indicating a focus on expanding plugin capabilities.\", \"2025-11-09T23:14:15.927Z\"]\n[\"odilitime_day_2025-11-06\", \"odilitime\", \"day\", \"2025-11-06\", \"odilitime: Focused on bug fixes and test alignment, merging a PR to fix tasks in `elizaos-plugins/plugin-birdeye` (#7) and opening a PR to align server tests with ElizaOS API changes in `elizaos/eliza` (#6135), with their code changes primarily focused on other work, bug fixes, and tests.\", \"2025-11-09T23:14:16.228Z\"]\n[\"0xbbjoker_day_2025-11-07\", \"0xbbjoker\", \"day\", \"2025-11-07\", \"0xbbjoker: Initiated significant feature work by opening PR elizaos-plugins/plugin-knowledge#46, which aims to migrate a core dependency for PDF processing, demonstrating a focus on enhancing plugin capabilities. This work involved modifying 2 files with a net change of -25 lines across code and configuration files.\", \"2025-11-09T23:14:16.465Z\"]"
]
}