# Fact Briefing: 2025-11-20

## Overall Summary
The elizaOS platform is currently focused on token migration from ai16z to elizaOS with a 6:1 conversion ratio, while addressing technical challenges in migration portal functionality and continuing development on core features including browser compatibility and Entity/server isolation.

## Categories

### GitHub Updates

#### New Issues/PRs
- [Issue #6161: Add Farcaster + Base app support](https://github.com/elizaOS/eliza/issues/6161) by borisudovicic - Status: open - Significance: Feature request for integrating with Farcaster and Base applications
- [Issue #6160: Addresses (account + transaction) should be hyperlinks](https://github.com/elizaOS/eliza/issues/6160) by borisudovicic - Status: open - Significance: UI improvement request for better user experience
- [Issue #6158: Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised)](https://github.com/elizaOS/eliza/issues/6158) by TommyVeit - Status: open - Significance: Critical token migration issue affecting user access
- [Pull_request #6159: fix: markdown spacing compact](https://github.com/elizaOS/eliza/pull/6159) by LinuxIsCool - Status: open - Significance: Minor documentation improvement

#### Overall Focus
- Development is focused on technical debt reduction with the migration from deprecated LangChain v0.3 to @langchain/textsplitters v1.0, alongside addressing user-reported issues and feature requests.
- The month's development has balanced immediate fixes with new features, including entity-level security enhancements and core runtime improvements.

### Discord Updates
- **#💬-discussion:** The channel is dominated by token migration issues from ai16z to elizaOS. Users are reporting problems with the migration portal, including tokens not showing up and indefinite loading screens. The migration process involves a 6:1 token ratio with eligibility based on a snapshot from November 11, 2023. Manual migration through support tickets is available for users with technical difficulties. (Key Participants: jasyn_bjorn, hns71, Odilitime, Toni, Borko)
- **#💬-coders:** Discussions focused on ElizaOS technical capabilities including the possibility of running in browser-based TEEs on iOS, EIP-8004 support in Babylon's implementation, and developer onboarding requirements. TypeScript was highlighted as essential for development, while React/Solidity knowledge isn't initially required. (Key Participants: DorianD, cjft, vaipraonde, amnesia)
- **#core-devs:** Stan provided updates on E2E authentication tests for Entity/server isolation, adding Postgres in CI, and requested reviews for several PRs. Stan is continuing work on PR #6135 that Odilitime started but hadn't completed. Issues with plugin-twitter functionality were also mentioned. (Key Participants: Stan, Odilitime, Borko)
- **#🥇-partners:** Brief discussion mentioning that the team is prioritizing security measures due to increased scammer activity. (Key Participants: Kenk)

### User Feedback
- Users are experiencing significant issues with the token migration portal, including tokens not showing up after wallet connection and indefinite loading screens. (Sentiment: negative)
- Some users are concerned about the legitimacy of the manual migration process, fearing potential scams. (Sentiment: negative)
- New developers are requesting clearer documentation about prerequisites for ElizaOS development and onboarding processes. (Sentiment: neutral)

### Strategic Insights

#### Token Migration Security Concerns
The increased scammer activity targeting the token migration process poses a significant risk to user trust and project reputation, necessitating clear documentation and communication about legitimate migration channels.

*Implications/Questions:*
  - How can the official migration process be made more transparent and secure?
  - Should additional verification methods be implemented for manual migrations?

#### Technical Debt Management
The focus on migrating away from deprecated dependencies (LangChain v0.3) while maintaining feature development shows a balanced approach to technical sustainability.

*Implications/Questions:*
  - Is the current balance between technical debt reduction and new feature development optimal?
  - What other critical dependencies might need updates in the near future?

#### Cross-Platform Compatibility
The discussions about browser-based TEE implementation for iOS suggest strategic focus on expanding platform reach beyond traditional environments.

*Implications/Questions:*
  - How should resources be allocated between core platform stability and cross-platform expansion?
  - What security implications arise from browser-based TEE implementation?

### Market Analysis
- The migration from ai16z to elizaOS tokens due to trademark conflicts with a16z corporation indicates potential legal and branding challenges in the AI space. (Relevance: Trademark issues could impact other projects in the space and suggests the need for thorough legal review of branding strategy.)
- Token migration has caused significant price volatility, with some users noting a 98% price drop. (Relevance: Price instability during token transitions could affect investor confidence and project funding capabilities.)