teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 18 Projects Releases Packages Wiki Activity Actions 1
teleo-codex/decisions/internet-finance/metadao-migrate-autocrat-v01.md
Teleo Agents 0da42ebbf1 schema: move 68 decision_market entities to decisions/internet-finance/ 
Separates governance decisions from entities. decision_market type replaced
by type: decision in new decisions/ directory. Entities (companies, people,
protocols) remain in entities/{domain}/.

Architecture: Leo (schema), Rio (taxonomy), Ganymede (migration), Rhea (ops)
Implemented by: Epimetheus

Pentagon-Agent: Epimetheus <968B2991-E2DF-4006-B962-F5B0A0CC8ACA>
2026-03-16 17:31:07 +00:00

2.6 KiB
Raw Blame History

type entity_type name domain status parent_entity platform proposer proposal_url proposal_date resolution_date category summary tracked_by created
decision 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 durations (default 3 days) 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, introducing configurable proposal slot durations with a new 3-day default (down from an unspecified longer period) to enable faster governance iteration. The migration transferred 990,000 META, 10,025 USDC, and 5.5 SOL from the v0.0 treasury to the v0.1 program's treasury.

Market Data

  • Outcome: Passed
  • Proposer: HfFi634cyurmVVDr9frwu4MjGLJzz9XbAJz981HdVaNz
  • Proposal Account: AkLsnieYpCU2UsSqUNrbMrQNi9bvdnjxx75mZbJns9zi
  • DAO Account: 3wDJ5g73ABaDsL1qofF5jJqEJU4RnRQrvzRLkSnFc5di
  • Completed: 2023-12-13

Significance

This was MetaDAO's first major governance mechanism upgrade, establishing the pattern of iterative futarchy refinement. The shift to configurable and shorter proposal durations reflected a production learning: faster feedback loops matter more than theoretical purity in early-stage futarchy adoption.

The proposal also highlighted a key production tradeoff: the upgrade was deployed without verifiable builds due to unspecified constraints, accepting counterparty trust risk to ship the improvement faster. The proposer acknowledged this as temporary, noting future versions would use verifiable builds.

Key Risks Acknowledged

  • Smart contract risk: Potential bugs in v0.1 not present in v0.0 (assessed as low given limited code changes)
  • Counterparty risk: Non-verifiable build required trust in proposer not introducing backdoors

Relationship to KB