# Fact Briefing: 2026-02-27

## Overall Summary
ElizaOS is managing a significant repository restructuring following an accidental push of v2.0.0 code to the develop branch, while simultaneously expanding its ecosystem through new plugins and decentralized identity protocols.

## Key Facts

- A v2-develop branch was created to recover 1.x code after the main develop branch was found to contain unfixable 2.0.0 code commits.
- The SAID Protocol was integrated to provide agents with on-chain Solana identities via Ed25519 keypair generation during project creation.
- GitHub and Linear bidirectional synchronization was identified as causing issue tracking inconsistencies that require manual cleanup.
- A new ActionFilterService using vector search and BM25 reranking was proposed to reduce prompt bloat by filtering relevant actions.
- A major database refactor (PR #6509) was initiated to improve architecture for the upcoming beta launch.
- Users reported multiple instances of duplicate LLM calls triggered by URLs in the webapp in issue #6486.
- The team analyzed the Hermes Agent framework, identifying trajectory compression as its primary feature of interest.
- An authentication retry loop in the Twitter plugin was resolved and media upload capabilities were implemented per PR #48.

## Open Questions

- For what version of which product? (regarding Twitter input issue)
- Does the code bot follow your org if you use it?
- When does Babylon launch, and milady.ai?
- How much of Roperito's life engine is in the Hermes agent framework?
- Was putting 2.0.0 code in develop intentional?
- When will new AI news be released?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6510: feat: add SAID Protocol on-chain Solana identity](https://github.com/elizaos/eliza/pull/6510) by kaiclawd - Status: open - Significance: Introduces verifiable on-chain identity for all agents created via CLI.
- [Pull_request #6519: refactor(core): strict typing for logger runtime](https://github.com/elizaos/eliza/pull/6519) by Fankouzu - Status: open - Significance: Improves code quality and type safety in core logging modules.
- [Issue #6486: [Bug] URL in message triggers duplicate LLM calls](https://github.com/elizaos/eliza/issues/6486) by thewoweffect - Status: open - Significance: Critical bug doubling token costs for messages containing links.

#### Overall Focus
- Consolidating the v2.0.0 codebase while maintaining backwards compatibility for 1.x users through branch isolation.

### Discord Updates
- **#💬-coders:** Discussions focused on troubleshooting Twitter input functionality and resolving versioning confusion. (Key Participants: Jamie, Odilitime)
- **#xfn-framework:** Technical inquiry into bot organizational behavior and repository management in organizational contexts. (Key Participants: Odilitime, Shawmakesmagic)
- **#💬-discussion:** Legal concerns raised regarding the Hyperscape project and potential Jagex IP infringement; community reassurance regarding the ELIZAOS token price decline. (Key Participants: Error P015-A, Odilitime, Amit gupta)

### User Feedback
- Concerns about potential project stalling due to stagnant token price action and bear market conditions. (Sentiment: negative)
- Beginners requesting more structured onboarding documentation and dedicated help channels for initial agent setup. (Sentiment: neutral)

### Strategic Insights

#### Version Control Fragmentation
The accidental push of v2.0.0 to develop suggests a need for stricter branch protections or a review of CI/CD workflows to prevent future deployment contamination.

*Implications/Questions:*
  - How will the team maintain feature parity between the v2 branch and the legacy-recovery branches?

#### Legal Vulnerability in Ecosystem Projects
The Hyperscape/RuneScape discussion highlights potential liability for the framework if hosted agents or plugins infringe on major gaming IPs.

*Implications/Questions:*
  - Should a formal legal disclaimer or content policy be established for developers using the framework?

### Market Analysis
- Introduction of 'fomolt', an agentic trading platform for Eliza agents on Base, utilizing USDC for gas via paymasters. (Relevance: Improves liquidity and provides testing utility for developer-led trading agents.)