42e3ddb0b5
- Source: inbox/archive/2026-03-05-futardio-launch-git3.md - Domain: internet-finance - Extracted by: headless extraction cron (worker 2) Pentagon-Agent: Rio <HEADLESS>
51 lines
No EOL
2.4 KiB
Markdown
51 lines
No EOL
2.4 KiB
Markdown
---
|
|
type: entity
|
|
entity_type: decision_market
|
|
name: "Git3: Futardio Fundraise"
|
|
domain: internet-finance
|
|
status: failed
|
|
parent_entity: "[[git3]]"
|
|
platform: "futardio"
|
|
proposal_url: "https://www.futard.io/launch/HKRDmghovXSCMobiRCZ7BBdHopEizyKmnhJKywjk3vUa"
|
|
proposal_date: 2026-03-05
|
|
resolution_date: 2026-03-06
|
|
category: "fundraise"
|
|
summary: "Git3 attempted to raise $100K through futarchy-governed launch for on-chain Git infrastructure"
|
|
key_metrics:
|
|
funding_target: "$100,000"
|
|
total_committed: "$28,266"
|
|
outcome: "refunding"
|
|
token: "6VT"
|
|
token_mint: "6VTMeDtrtimh2988dhfYi2rMEDVdYzuHoSgERUmdmeta"
|
|
tracked_by: rio
|
|
created: 2026-03-11
|
|
---
|
|
|
|
# Git3: Futardio Fundraise
|
|
|
|
## Summary
|
|
|
|
Git3 launched a futarchy-governed fundraise on Futardio targeting $100,000 to build on-chain Git infrastructure with permanent storage on Irys blockchain. The project proposed bringing Git repositories on-chain as NFTs with x402 monetization, GitHub Actions integration, and AI agent interoperability. The raise achieved 28.3% of target ($28,266 committed) before entering refunding status after one day.
|
|
|
|
## Market Data
|
|
|
|
- **Outcome:** Failed (Refunding)
|
|
- **Funding Target:** $100,000
|
|
- **Total Committed:** $28,266 (28.3% of target)
|
|
- **Launch Date:** 2026-03-05
|
|
- **Closed:** 2026-03-06
|
|
- **Token:** 6VT
|
|
- **Platform:** Futardio v0.7
|
|
|
|
## Significance
|
|
|
|
This represents a failed futarchy-governed fundraise for developer infrastructure, demonstrating that not all technically sound projects achieve funding targets through prediction markets. The 28.3% fill rate suggests either insufficient market validation of the code-as-asset thesis, limited awareness of the launch, or skepticism about the team's ability to execute the ambitious roadmap (12-month runway, three development phases, enterprise features).
|
|
|
|
The refunding outcome is notable because Git3 had a live MVP, clear technical architecture, and alignment with broader trends (on-chain code storage, AI agent infrastructure, x402 protocol). The failure suggests futarchy markets can filter projects even when fundamentals appear strong, potentially due to go-to-market concerns, competitive positioning (GitHub's dominance), or team credibility questions.
|
|
|
|
## Relationship to KB
|
|
|
|
- [[git3]] — parent entity
|
|
- [[futardio]] — fundraising platform
|
|
- [[MetaDAO]] — futarchy infrastructure provider
|
|
- Demonstrates futarchy-governed fundraise failure despite live MVP and technical merit |