# Issue Triage Document - 2025-11-20 ## Issue #6161: Add Farcaster + Base app support **Current Status**: OPEN **Impact Assessment**: - User Impact: Medium (Affects users wanting to use the platform with Farcaster ecosystem) - Functional Impact: No (Additional feature, not core functionality) - Brand Impact: Medium (Integration with popular decentralized social platforms enhances perception) **Technical Classification**: - Issue Category: Feature Request - Component Affected: Integration Layer, API - Complexity: Moderate effort **Resource Allocation Factors**: - Required Expertise: Farcaster API, Base blockchain integration, elizaOS integration patterns - Dependencies: Might depend on hyperlink issue #6160 - Estimated Effort: 3 **Recommended Priority**: P2 **Actionable Next Steps**: 1. Verify technical requirements for Farcaster API integration 2. Outline integration approach with Base blockchain 3. Create technical specification document 4. Implement proof of concept **Potential Assignees**: borisudovicic (issue reporter), Freytes (experience with Farcaster miniapp) --- ## Issue #6160: Addresses (account + transaction) should be hyperlinks **Current Status**: OPEN **Impact Assessment**: - User Impact: Medium (Improves UX for all users interacting with addresses) - Functional Impact: Partial (Enhances usability but doesn't block core functionality) - Brand Impact: Medium (Affects perceived quality of the interface) **Technical Classification**: - Issue Category: UX - Component Affected: UI Components - Complexity: Simple fix **Resource Allocation Factors**: - Required Expertise: Frontend development, React - Dependencies: None - Estimated Effort: 1 **Recommended Priority**: P2 **Actionable Next Steps**: 1. Identify all components displaying addresses 2. Create a shared component for displaying addresses as hyperlinks 3. Implement linking to appropriate block explorers 4. Add tests to ensure proper rendering **Potential Assignees**: borisudovicic (issue reporter), wtfsayo (React experience) --- ## Issue #6158: Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported **Current Status**: OPEN **Impact Assessment**: - User Impact: High (Directly affects token migration for specific wallet users) - Functional Impact: Yes (Blocks migration process for affected users) - Brand Impact: High (Creates frustration during critical token migration) **Technical Classification**: - Issue Category: Bug - Component Affected: Migration Portal, Wallet Integration - Complexity: Moderate effort **Resource Allocation Factors**: - Required Expertise: Wallet connectivity, Token migration process - Dependencies: Existing migration infrastructure - Estimated Effort: 3 **Recommended Priority**: P1 **Actionable Next Steps**: 1. Verify reported snapshot eligibility issues 2. Test Tangem wallet connection problems 3. Add support for Tangem wallet or document migration workarounds 4. Investigate reported Discord support compromise **Potential Assignees**: Odilitime (token migration expertise), Kenk (security priorities) --- ## PR #6159: Fix markdown spacing compact **Current Status**: No state information provided **Impact Assessment**: - User Impact: Low (Documentation formatting issue) - Functional Impact: No (Doesn't affect functionality) - Brand Impact: Low (Minor documentation improvement) **Technical Classification**: - Issue Category: Documentation - Component Affected: Documentation - Complexity: Simple fix **Resource Allocation Factors**: - Required Expertise: Markdown formatting - Dependencies: None - Estimated Effort: 1 **Recommended Priority**: P3 **Actionable Next Steps**: 1. Review the proposed markdown formatting changes 2. Test rendering in GitHub and project documentation site 3. Approve and merge if changes improve readability **Potential Assignees**: LinuxIsCool (PR author) --- ## PR #6143: Fix plugin-mysql support, initPromise and other minor fixes **Current Status**: Open (not merged) **Impact Assessment**: - User Impact: Medium (Improves database options for users) - Functional Impact: Partial (Enhances database flexibility) - Brand Impact: Medium (Shows commitment to multiple database support) **Technical Classification**: - Issue Category: Feature/Bug - Component Affected: Database Integration - Complexity: Moderate effort **Resource Allocation Factors**: - Required Expertise: Database integration, MySQL, PostgreSQL - Dependencies: Existing database plugins - Estimated Effort: 4 **Recommended Priority**: P1 **Actionable Next Steps**: 1. Complete code review (requested by Stan) 2. Test MySQL integration paths 3. Verify proper handling of RLS differences between databases 4. Merge after validation **Potential Assignees**: Odilitime (author), Stan (reviewing) --- ## Issue related to plugin-twitter functionality **Current Status**: Mentioned in Discord, no formal issue **Impact Assessment**: - User Impact: Medium (Users relying on Twitter integration affected) - Functional Impact: Partial (Specific plugin not functioning) - Brand Impact: Medium (Integration with popular platform not working) **Technical Classification**: - Issue Category: Bug - Component Affected: Plugin System, Twitter Integration - Complexity: Moderate effort **Resource Allocation Factors**: - Required Expertise: Twitter API, Plugin system - Dependencies: Twitter API changes - Estimated Effort: 3 **Recommended Priority**: P2 **Actionable Next Steps**: 1. Create formal issue for tracking 2. Investigate specific Twitter plugin failures 3. Determine if issue is related to Twitter API changes 4. Develop fix and test across different use cases **Potential Assignees**: Odilitime (mentioned issue), cjft (plugin system knowledge) --- ## Migration Portal Issues (mentioned across Discord) **Current Status**: Mentioned in Discord, no formal consolidated issue **Impact Assessment**: - User Impact: High (Affects all users trying to migrate tokens) - Functional Impact: Yes (Blocks critical token migration) - Brand Impact: High (Creates frustration during key ecosystem transition) **Technical Classification**: - Issue Category: Bug - Component Affected: Migration Portal, Wallet Integration - Complexity: Moderate effort **Resource Allocation Factors**: - Required Expertise: Wallet connectivity, Token migration process - Dependencies: Existing migration infrastructure - Estimated Effort: 4 **Recommended Priority**: P0 **Actionable Next Steps**: 1. Consolidate all migration-related issues into a tracking issue 2. Address indefinite loading issue on portal 3. Fix issues with tokens not appearing after wallet connection 4. Improve error reporting for better user feedback 5. Document manual migration process more clearly **Potential Assignees**: Odilitime, jasyn_bjorn, Toni (migration support in Discord) --- ## Browser-based TEEs for iOS Implementation **Current Status**: Discussion phase in Discord **Impact Assessment**: - User Impact: High (Opens platform to iOS users) - Functional Impact: No (New capability, not existing functionality) - Brand Impact: High (Expands platform reach to iOS ecosystem) **Technical Classification**: - Issue Category: Feature Request - Component Affected: Core Framework, Runtime - Complexity: Complex solution **Resource Allocation Factors**: - Required Expertise: iOS development, TEE implementation, Browser runtime - Dependencies: Existing browser-compatible components - Estimated Effort: 5 **Recommended Priority**: P2 **Actionable Next Steps**: 1. Create a formal issue for tracking 2. Research browser-based TEE capabilities on iOS 3. Develop proof-of-concept implementation 4. Identify which plugins need browser compatibility updates **Potential Assignees**: DorianD (suggested idea), cjft (confirmed browser runtime capability) --- ## EIP-8004 Support in Babylon **Current Status**: Discussion phase in Discord **Impact Assessment**: - User Impact: Medium (Affects users wanting cross-chain capability) - Functional Impact: No (Additional integration, not core functionality) - Brand Impact: Medium (Enhances interoperability perception) **Technical Classification**: - Issue Category: Feature Request - Component Affected: Blockchain Integration - Complexity: Complex solution **Resource Allocation Factors**: - Required Expertise: Ethereum standards, Babylon implementation, agent0 integration - Dependencies: Babylon project progress - Estimated Effort: 4 **Recommended Priority**: P2 **Actionable Next Steps**: 1. Create formal issue for tracking 2. Clarify requirements for EIP-8004 support 3. Assess integration approach with agent0 on Ethereum+Filecoin 4. Design integration architecture **Potential Assignees**: DorianD (raised question) --- ## PR #6135: (Ongoing work, no title provided) **Current Status**: In Progress **Impact Assessment**: - User Impact: Unknown (insufficient details) - Functional Impact: Unknown (insufficient details) - Brand Impact: Unknown (insufficient details) **Technical Classification**: - Issue Category: Unknown (likely feature/enhancement based on context) - Component Affected: Unknown - Complexity: Complex solution (based on comment "took a long time") **Resource Allocation Factors**: - Required Expertise: Unknown - Dependencies: Unknown - Estimated Effort: 4 (estimated based on "took a long time" comment) **Recommended Priority**: P1 (based on Stan taking it over) **Actionable Next Steps**: 1. Ensure Stan has all context from Odilitime 2. Continue development based on existing work 3. Create test plan for validating the implementation 4. Prepare comprehensive PR description for eventual review **Potential Assignees**: Stan (continuing work), Odilitime (original author) --- ## Summary of Top Priority Issues 1. **Migration Portal Issues (P0)**: Critical bugs in the token migration process affecting multiple users. Needs immediate attention due to impact on user experience during a crucial ecosystem transition. 2. **PR #6143: Fix plugin-mysql support (P1)**: Important enhancement adding MySQL support and fixing database-related issues. Directly impacts database flexibility and should be merged soon. 3. **Issue #6158: Snapshot Eligibility Issue + Tangem Wallet (P1)**: Critical issues with token migration for specific wallet users. High impact on affected users' ability to migrate tokens. 4. **PR #6135: (Ongoing work) (P1)**: While details are limited, this appears to be a complex and important implementation that Stan has prioritized. 5. **Issue #6161: Add Farcaster + Base app support (P2)**: Strategic integration with popular decentralized social platforms that would enhance the ecosystem. 6. **Issue #6160: Addresses as hyperlinks (P2)**: UX improvement that would enhance usability for all users interacting with blockchain addresses. 7. **Plugin-twitter functionality issues (P2)**: Integration with a major social platform is broken, affecting users who rely on Twitter integration. 8. **Browser-based TEEs for iOS Implementation (P2)**: Strategic feature that would expand platform reach to iOS ecosystem. 9. **EIP-8004 Support in Babylon (P2)**: Important cross-chain capability that enhances interoperability. 10. **PR #6159: Fix markdown spacing (P3)**: Minor documentation improvement with low impact. ## Patterns and Themes 1. **Migration and Wallet Integration Challenges**: Multiple issues revolve around token migration and wallet compatibility, suggesting this area needs architectural review and improved testing. 2. **Cross-Platform Support Gap**: Issues related to iOS support and plugin browser compatibility indicate the need for a more comprehensive cross-platform strategy. 3. **Integration Ecosystem Expansion**: Many feature requests involve integrating with external platforms (Farcaster, Twitter, Babylon), showing demand for a broader ecosystem. 4. **Database Flexibility**: The work on MySQL support indicates a need for greater database flexibility beyond the current PostgreSQL focus. 5. **Documentation and UX Refinement**: Several issues address the need for improved user experience and documentation, suggesting these areas need ongoing attention. ## Process Improvement Recommendations 1. **Formalized Migration Testing Protocol**: Implement a comprehensive testing protocol specifically for wallet integrations and token migrations, including a diverse range of wallet types and transaction scenarios. 2. **Issue Template for Integration Requests**: Create a standardized template for external integration requests that captures API requirements, authentication needs, and expected user flows. 3. **Cross-Platform Compatibility Checklist**: Develop a checklist for ensuring new features maintain compatibility across all supported platforms. 4. **Consolidated Migration Support**: Create a dedicated support channel and knowledge base specifically for token migration issues to streamline user assistance. 5. **Browser Compatibility Matrix**: Maintain a matrix of plugin compatibility with browser-based runtime to highlight which plugins need updates for cross-platform support. 6. **Database Strategy Documentation**: Clarify the project's approach to supporting multiple database backends and document the necessary abstractions for plugin developers.