## MetaDAO Omnibus Proposal — Migrate DAO Program and Update Legal Documents

**Proposal ID:** Bzoap95gjbokTaiEqwknccktfNSvkPe4ZbAdcJF1yiEK

**Status as of 2026-03-23:** Active at 84% pass probability, $408K traded

**Type:** Mechanism upgrade + legal update

### Technical Context

This proposal represents the latest in MetaDAO's pattern of autocrat program migrations. Previous migrations (v0.1→v0.2 in 2023-12-03 and 2024-03-28) addressed operational issues identified post-deployment.

**Current program versions:**
- autocrat v0.5.0 (DAO governance coordinator)
- launchpad v0.7.0
- conditional_vault v0.4

### Key Components

**1. Squads v4.0 Integration**

The migration includes integration of Squads multisig infrastructure (AGPLv3 licensed), suggesting structural separation between:
- DAO treasury (futarchy-governed)
- Operational execution (multisig-controlled)

This addresses the execution velocity problem that the BDF3M (Session 11) temporarily solved through human delegation, now replacing temporary centralization with permanent structural separation.

**2. Legal Document Updates**

Scope of legal updates unknown due to proposal text inaccessibility (429 rate-limiting on MetaDAO platform).

### Market Signal

The 84% pass probability with $408K volume indicates strong community consensus that the changes are beneficial. This is high confidence for a technical migration proposal.

### Significance

Every autocrat program migration in MetaDAO's history has been a governance improvement. If this migration follows the pattern, it likely addresses issues discovered in the v0.5 deployment cycle, potentially including:
- Manipulation surface area reduction
- Liquidity mechanics improvements
- Proposal process design enhancements

### Outstanding Questions

- Full proposal text (platform returning 429 errors)
- Specific technical changes in new program version
- Whether migration addresses documented mechanism vulnerabilities (manipulation resistance at thin liquidity, off-chain fundamentals problem, Unruggable ICO post-TGE gap)
- Scope of legal document updates

**Source:** MetaDAO governance interface, @m3taversal Telegram, @01Resolved analytics