teleo-codex/decisions/internet-finance/metadao-omnibus-migration-proposal.md
Teleo Agents 96324d04fd extract: 2026-03-25-metadao-omnibus-migration-proposal
Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>
2026-03-26 04:32:34 +00:00

52 lines
No EOL
2.1 KiB
Markdown

## MetaDAO Omnibus Proposal — Migrate DAO Program and Update Legal Documents
**Proposal ID:** Bzoap95gjbokTaiEqwknccktfNSvkPe4ZbAdcJF1yiEK
**Status:** Active (as of 2026-03-23)
**Market Activity:** 84% pass probability, $408K traded volume
### Technical Components
**Program Migration:**
- Migrate from autocrat v0.5.0 to new version (specific version TBD)
- Continues pattern where every autocrat migration addresses operational issues discovered post-deployment
- Previous migrations: v0.1 → v0.2 (2023-12-03), v0.2 update (2024-03-28)
**Squads Integration:**
- Integrate Squads v4.0 (AGPLv3) multisig infrastructure
- Creates structural separation between:
- DAO treasury (futarchy-governed)
- Operational execution (multisig-controlled)
- Addresses execution velocity problem that BDF3M temporarily solved through human delegation
**Legal Document Updates:**
- Scope not specified in available materials
- May relate to entity structuring or Howey test considerations
### Context
**Current Program Versions (GitHub, 2026-03-18):**
- autocrat v0.5.0
- launchpad v0.7.0
- conditional_vault v0.4
**Significance:**
The Squads multisig integration represents a structural complement to futarchy governance, replacing the temporary centralization of BDF3M with permanent infrastructure that separates market-based decision-making from operational security requirements.
**Market Confidence:**
The 84% pass probability with $408K volume indicates strong community consensus that the changes are beneficial, consistent with historical pattern of successful autocrat migrations.
### Unknown Elements
- Full proposal text (MetaDAO governance interface returning 429 errors)
- Specific technical changes in new autocrat version
- Whether migration addresses mechanism vulnerabilities documented in Sessions 4-8
- Complete scope of legal document updates
### Sources
- MetaDAO governance interface: metadao.fi/projects/metadao/proposal/Bzoap95gjbokTaiEqwknccktfNSvkPe4ZbAdcJF1yiEK
- @m3taversal Telegram conversation (2026-03-23)
- MetaDAO GitHub repository (commit activity 2026-03-18)
- @01Resolved analytics platform coverage