ff623c8b2f
- Source: inbox/archive/2026-03-05-futardio-launch-git3.md - Domain: internet-finance - Extracted by: headless extraction cron (worker 2) Pentagon-Agent: Rio <HEADLESS>
2.1 KiB
2.1 KiB
| type | entity_type | name | domain | status | parent_entity | platform | proposal_url | proposal_date | resolution_date | category | summary | key_metrics | tracked_by | created | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| entity | decision_market | Git3: Futardio Fundraise | internet-finance | failed | git3 | futardio | https://www.futard.io/launch/HKRDmghovXSCMobiRCZ7BBdHopEizyKmnhJKywjk3vUa | 2026-03-05 | 2026-03-06 | fundraise | Git3 attempted to raise $100K for on-chain Git infrastructure through futarchy-governed launch |
|
rio | 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, repository NFTs, and x402 protocol monetization. The raise closed in refunding status after one day with only 28.3% of target committed.
Market Data
- Outcome: Failed (refunding)
- Target: $100,000
- Committed: $28,266 (28.3%)
- Duration: 1 day (2026-03-05 to 2026-03-06)
- Token: 6VT
Significance
This represents a test case for futarchy-governed fundraising in developer infrastructure. The low completion rate (28.3%) suggests either:
- Market skepticism about on-chain Git value proposition
- Insufficient liquidity/attention for developer tools on futarchy platforms
- Timing or execution issues in the launch
The project had a complete technical roadmap (MVP live, 3-phase development plan) and clear revenue model (creator fees, protocol fees, agent royalties), but failed to attract sufficient capital commitment through the futarchy mechanism.
Relationship to KB
- git3 — parent entity
- futardio — fundraising platform
- MetaDAO — futarchy governance infrastructure
- Relevant to futarchy-governed-permissionless-launches-require-brand-separation-to-manage-reputational-liability-because-failed-projects-on-a-curated-platform-damage-the-platforms-credibility