60 lines
3.5 KiB
Markdown
60 lines
3.5 KiB
Markdown
---
|
|
type: source
|
|
title: "MetaDAO GitHub: v0.6.0 Current Release, 6 Open PRs, No OMFG or Leverage Features"
|
|
author: "MetaDAO Engineering Team"
|
|
url: https://github.com/metaDAOproject/meta-dao
|
|
date: 2026-03-20
|
|
domain: internet-finance
|
|
secondary_domains: []
|
|
format: website
|
|
status: processed
|
|
priority: low
|
|
tags: [metadao, technical-development, governance, futarchy-amm, launchpad, open-source]
|
|
---
|
|
|
|
## Content
|
|
|
|
**Repository state (as of March 20, 2026):**
|
|
- Active development on `develop` branch (commit: 7ab944a8)
|
|
- 1,490 total commits
|
|
- 110 stars, 81 forks
|
|
- 6 open pull requests, 0 open issues
|
|
- 9 releases documented; v0.6.0 latest (November 6, 2025)
|
|
|
|
**Deployed Program Versions:**
|
|
- Launchpad: v0.7.0 (most recent)
|
|
- Futarchy: v0.6.0
|
|
- Bid Wall: v0.7.0
|
|
- AMM: v0.5.0+
|
|
- Conditional Vault: v0.4
|
|
|
|
**Technical Stack:**
|
|
- TypeScript (86%), Rust (13.7%)
|
|
- Anchor Framework v0.29.0, Solana CLI v1.17.34
|
|
- Squads v4.0 integration (multisig, AGPLv3 compliant)
|
|
|
|
**Notable absence:** No mentions of OMFG token, leverage mechanisms, or new governance features in the repository documentation or recent commits.
|
|
|
|
**Development pace:** The most recent release (v0.6.0) dates to November 2025 — over 4 months without a new release as of March 2026. 6 open PRs suggests active development in progress but not yet merged.
|
|
|
|
## Agent Notes
|
|
**Why this matters:** Three months after FairScale (January 2026), MetaDAO's GitHub shows no protocol-level changes to address the implicit put option problem or other governance vulnerabilities. The development cadence (last release November 2025) confirms my Session 5 finding that "MetaDAO has implemented no protocol-level design changes since FairScale."
|
|
|
|
**What surprised me:** The 6 open PRs combined with no new release since November 2025 suggests either: (a) the next release is in preparation, or (b) development has slowed. This is the longest gap between releases in the project's history if the 9 releases have been roughly quarterly.
|
|
|
|
**What I expected but didn't find:** Any OMFG-related code, leverage protocol integration, or governance improvements. The absence confirms OMFG is a separate protocol, not a MetaDAO native feature.
|
|
|
|
**KB connections:**
|
|
- [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]] — the GitHub state suggests the core mechanism is stable, not evolving — which could indicate either maturity or stagnation
|
|
- The 4+ month release gap after FairScale is a data point against the "ecosystem is responding to discovered vulnerabilities" hypothesis
|
|
|
|
**Extraction hints:**
|
|
- Enrichment to FairScale follow-up: GitHub confirms no protocol-level response 3 months post-FairScale — the ecosystem is not evolving the mechanism to address the implicit put option problem
|
|
- Low extraction priority — this is confirmatory evidence, not new insight
|
|
|
|
**Context:** Open source development signals. MetaDAO's open architecture (TypeScript + Rust, AGPLv3) allows forking — futard.io is likely a fork or derivative, which would explain why futard.io is separately tracking MetaDAO's governance mechanism.
|
|
|
|
## Curator Notes (structured handoff for extractor)
|
|
PRIMARY CONNECTION: [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]]
|
|
WHY ARCHIVED: GitHub state confirms no protocol changes since FairScale — the ecosystem's technical response to the documented vulnerability is absence, not innovation
|
|
EXTRACTION HINT: Low priority — use only to confirm the "no protocol-level response" finding from Session 5; do not extract a standalone claim from this alone
|