teleo-codex/entities/internet-finance/metadao-migrate-autocrat-v01.md
Teleo Pipeline 983c9595b3 extract: 2023-12-03-futardio-proposal-migrate-autocrat-program-to-v01
Pentagon-Agent: Ganymede <F99EBFA6-547B-4096-BEEA-1D59C3E4028A>
2026-03-15 15:18:57 +00:00

2.5 KiB

type entity_type name domain status parent_entity platform proposer proposal_url proposal_date resolution_date category summary tracked_by created
entity decision_market MetaDAO: Migrate Autocrat Program to v0.1 internet-finance passed metadao futardio HfFi634cyurmVVDr9frwu4MjGLJzz9XbAJz981HdVaNz https://www.futard.io/proposal/AkLsnieYpCU2UsSqUNrbMrQNi9bvdnjxx75mZbJns9zi 2023-12-03 2023-12-13 mechanism Upgrade Autocrat program to v0.1 with configurable proposal duration (3-day default) and migrate 990K META + 10K USDC + 5.5 SOL to new treasury rio 2026-03-11

MetaDAO: Migrate Autocrat Program to v0.1

Summary

This proposal upgraded MetaDAO's Autocrat futarchy implementation to v0.1, making proposal duration configurable with a new 3-day default (down from a longer implied period) to enable faster feedback loops. The migration required moving the entire treasury (990,000 META, 10,025 USDC, and 5.5 SOL) from the first program to the second program.

Market Data

  • Outcome: Passed
  • Proposer: HfFi634cyurmVVDr9frwu4MjGLJzz9XbAJz981HdVaNz
  • Completed: 2023-12-13
  • Proposal account: AkLsnieYpCU2UsSqUNrbMrQNi9bvdnjxx75mZbJns9zi

Key Risks Disclosed

  1. Smart contract risk: Potential for new bugs in upgraded program (assessed as small by proposer)
  2. Counterparty risk: Build was not verifiable due to technical constraints, requiring trust in proposer that no backdoor was introduced. Proposer committed to using verifiable builds for future versions.

Significance

This was MetaDAO's first major mechanism upgrade, demonstrating:

  • Willingness to iterate on futarchy parameters based on user experience (faster feedback)
  • The operational friction of treasury migrations when upgrading program architecture
  • Trust dynamics in early-stage futarchy implementations (non-verifiable build accepted by community)
  • Evolution from hardcoded to configurable governance parameters

Relationship to KB