rio: extract claims from 2025-02-24-futardio-proposal-mtn-meets-meta-hackathon #329

Closed
rio wants to merge 1 commit from extract/2025-02-24-futardio-proposal-mtn-meets-meta-hackathon into main
2 changed files with 20 additions and 1 deletions

View file

@ -17,6 +17,12 @@ In uncontested decisions -- where the community broadly agrees on the right outc
This evidence has direct implications for governance design. It suggests that [[optimal governance requires mixing mechanisms because different decisions have different manipulation risk profiles]] -- futarchy excels precisely where disagreement and manipulation risk are high, but it wastes its protective power on consensual decisions. The MetaDAO experience validates the mixed-mechanism thesis: use simpler mechanisms for uncontested decisions and reserve futarchy's complexity for decisions where its manipulation resistance actually matters. The participation challenge also highlights a design tension: the mechanism that is most resistant to manipulation is also the one that demands the most sophistication from participants. This evidence has direct implications for governance design. It suggests that [[optimal governance requires mixing mechanisms because different decisions have different manipulation risk profiles]] -- futarchy excels precisely where disagreement and manipulation risk are high, but it wastes its protective power on consensual decisions. The MetaDAO experience validates the mixed-mechanism thesis: use simpler mechanisms for uncontested decisions and reserve futarchy's complexity for decisions where its manipulation resistance actually matters. The participation challenge also highlights a design tension: the mechanism that is most resistant to manipulation is also the one that demands the most sophistication from participants.
### Additional Evidence (confirm)
*Source: [[2025-02-24-futardio-proposal-mtn-meets-meta-hackathon]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
Test DAO proposal #17 (mtn Meets META Hackathon) failed after 3 days (2025-02-24 to 2025-02-27) with apparent low engagement. Source explicitly notes 'This DAO is hidden so the proposal isn't easy to find' and risk analysis identifies 'low participation or engagement, which could undermine the effectiveness and outcomes.' The proposal's failure combined with documented discoverability and participation barriers provides concrete evidence of limited trading volume in routine (non-controversial) futarchy decisions.
--- ---
Relevant Notes: Relevant Notes:

View file

@ -6,9 +6,14 @@ url: "https://www.futard.io/proposal/9ZYMaLKWn9PSLTX1entmqJUYBiCkZbRxeRz1tVvYwqy
date: 2025-02-24 date: 2025-02-24
domain: internet-finance domain: internet-finance
format: data format: data
status: unprocessed status: enrichment
tags: [futardio, metadao, futarchy, solana, governance] tags: [futardio, metadao, futarchy, solana, governance]
event_type: proposal event_type: proposal
processed_by: rio
processed_date: 2025-02-24
enrichments_applied: ["MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions.md"]
extraction_model: "anthropic/claude-sonnet-4.5"
extraction_notes: "Single failed proposal data point. No novel claims extractable - this is a factual record of one governance event. The failure and noted low participation risk confirms existing claim about limited trading volume in uncontested futarchy decisions. No evidence of actual trading volume data, market depth, or comparative analysis that would support new claims about futarchy mechanics."
--- ---
## Proposal Details ## Proposal Details
@ -50,3 +55,11 @@ But you have access to the data via API so here you are!
- Autocrat version: 0.3 - Autocrat version: 0.3
- Completed: 2025-02-27 - Completed: 2025-02-27
- Ended: 2025-02-27 - Ended: 2025-02-27
## Key Facts
- Test DAO proposal #17 (mtn Meets META Hackathon) created 2025-02-24, failed 2025-02-27
- Proposal account: 9ZYMaLKWn9PSLTX1entmqJUYBiCkZbRxeRz1tVvYwqy6
- DAO account: GWywkp2mY2vzAaLydR2MBXRCqk2NgGHxCk1gJrtSTxJoyqVonqndhq
- Autocrat version: 0.3
- Test DAO is configured as hidden/not easily discoverable