# Council Briefing: 2026-04-20

## Monthly Goal

December 2025: Execution excellence—complete token migration with high success rate, launch ElizaOS Cloud, stabilize flagship agents, and build developer trust through reliability and clear documentation.

## Daily Focus

- Transitioning from experimental Labs-led R&D to a high-velocity, community-driven open contribution model focused on framework reliability and agent-to-agent commerce.

## Key Points for Deliberation

### 1. Topic: Organizational Restructuring & Contributor Risk

**Summary of Topic:** The dissolution of Eliza Labs marks a return to open-source roots to accelerate the core framework, but introduces risks regarding ownership concentration and long-term maintenance of complex sub-systems.

#### Deliberation Items (Questions):

**Question 1:** How should the Council mitigate the high 'Bus Factor' associated with the current distribution of core runtime maintenance?

  **Context:**
  - `lalalune: Executed 117 commits across 13,940 files in a single period (2026-04-14).`
  - `Review dependency: Significant portion of core changes reviewed primarily by odilitime.`

  **Multiple Choice Answers:**
    a) Implement mandatory peer-review rotations for all core PRs.
        *Implication:* Ensures knowledge transfer but may slightly decelerate short-term shipping velocity.
    b) Formalize 'Working Groups' with dedicated leads for Runtime, Plugins, and Cloud.
        *Implication:* Distributes authority and reduces single-point-of-failure risks in the developer ecosystem.
    c) Incentivize top community contributors through a structured Bounty/Grant program.
        *Implication:* Attracts new talent to offload maintenance burden from the core duo.
    d) Other / More discussion needed / None of the above.

---


### 2. Topic: Security Gating & Community Trust

**Summary of Topic:** Repeated phishing incidents and the discovery of structural vulnerabilities (like the 'Virus' package) highlight the urgent need for codified security protocols and vulnerability disclosure guidelines.

#### Deliberation Items (Questions):

**Question 1:** What is the optimal strategy for balancing the 'Open & Composable' principle with the need to protect the community from malicious agents and phishing?

  **Context:**
  - `Kullai discovered security vulnerabilities in the open-source app and privately disclosed them to odilitime.`
  - `Scam incident (2026-04-19): Scammers impersonated community member 'kenk' with fake airdrop links.`

  **Multiple Choice Answers:**
    a) Establish a formal Bug Bounty program and official Security Disclosure Policy.
        *Implication:* Professionalizes the security posture and encourages ethical research over public leaks.
    b) Introduce a 'Verified Plugin' registry tier with strict code-review requirements.
        *Implication:* Maximizes safety for end-users while retaining an 'unverified' playground for experimentation.
    c) Automate security scanning and dependency auditing for all ecosystem PRs.
        *Implication:* Scales trust through technical guardrails without increasing manual review overhead.
    d) Other / More discussion needed / None of the above.

---


### 3. Topic: Agent-Native Economy Infrastructure

**Summary of Topic:** Recent proposals for 'AgentID' and prediction market plugins indicate a shift toward autonomous agent commerce, requiring robust identity and trust layers.

#### Deliberation Items (Questions):

**Question 1:** Should ElizaOS prioritize the integration of a native cryptographic identity layer to facilitate secure agent-to-agent transactions?

  **Context:**
  - `Plugin Proposal 6688: AgentID — Cryptographic Identity & Trust Layer for ElizaOS Agents.`
  - `Plugin: plugin-hiveexchange introduced to enable agent-native prediction markets (2026-04-19).`

  **Multiple Choice Answers:**
    a) Directly integrate AgentID into the Eliza Core runtime.
        *Implication:* Establishes a unified trust standard but ties the framework to a specific identity protocol.
    b) Maintain identity as an optional plugin while standardized through the Registry.
        *Implication:* Preserves modularity while allowing market competition to decide the best identity provider.
    c) Focus on cross-chain infrastructure first (Jeju/x402) before finalizing identity standards.
        *Implication:* Ensures technical interoperability remains the priority over social/identity layers.
    d) Other / More discussion needed / None of the above.