Compare commits
1 commit
ff623c8b2f
...
1a580ce130
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1a580ce130 |
4 changed files with 34 additions and 33 deletions
|
|
@ -46,7 +46,7 @@ MetaDAO's token launch platform. Implements "unruggable ICOs" — permissionless
|
|||
|
||||
- **2026-03-07** — Areal DAO launch: $50K target, raised $11,654 (23.3%), REFUNDING status by 2026-03-08 — first documented failed futarchy-governed fundraise on platform
|
||||
- **2026-03-04** — [[seekervault]] fundraise launched targeting $75,000, closed next day with only $1,186 (1.6% of target) in refunding status
|
||||
- **2026-03-05** — [[git3-futardio-fundraise]] launched: $100K target for on-chain Git infrastructure, closed refunding with $28,266 (28.3%)
|
||||
- **2026-03-05** — [[git3-futardio-fundraise]] failed: Git3 raised $28,266 of $100K target (28.3%) before entering refunding status, demonstrating market filtering even with live MVP
|
||||
## Competitive Position
|
||||
- **Unique mechanism**: Only launch platform with futarchy-governed accountability and treasury return guarantees
|
||||
- **vs pump.fun**: pump.fun is memecoin launch (zero accountability, pure speculation). Futardio is ownership coin launch (futarchy governance, treasury enforcement). Different categories despite both being "launch platforms."
|
||||
|
|
|
|||
|
|
@ -10,14 +10,13 @@ proposal_url: "https://www.futard.io/launch/HKRDmghovXSCMobiRCZ7BBdHopEizyKmnhJK
|
|||
proposal_date: 2026-03-05
|
||||
resolution_date: 2026-03-06
|
||||
category: "fundraise"
|
||||
summary: "Git3 attempted to raise $100K for on-chain Git infrastructure through futarchy-governed launch"
|
||||
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"
|
||||
completion_rate: "28.3%"
|
||||
launch_token: "6VT"
|
||||
outcome: "refunding"
|
||||
token: "6VT"
|
||||
token_mint: "6VTMeDtrtimh2988dhfYi2rMEDVdYzuHoSgERUmdmeta"
|
||||
launch_address: "HKRDmghovXSCMobiRCZ7BBdHopEizyKmnhJKywjk3vUa"
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
|
@ -26,28 +25,27 @@ created: 2026-03-11
|
|||
|
||||
## 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.
|
||||
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)
|
||||
- **Target:** $100,000
|
||||
- **Committed:** $28,266 (28.3%)
|
||||
- **Duration:** 1 day (2026-03-05 to 2026-03-06)
|
||||
- **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 test case for futarchy-governed fundraising in developer infrastructure. The low completion rate (28.3%) suggests either:
|
||||
1. Market skepticism about on-chain Git value proposition
|
||||
2. Insufficient liquidity/attention for developer tools on futarchy platforms
|
||||
3. Timing or execution issues in the launch
|
||||
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 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.
|
||||
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 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]]
|
||||
- [[MetaDAO]] — futarchy infrastructure provider
|
||||
- Demonstrates futarchy-governed fundraise failure despite live MVP and technical merit
|
||||
|
|
@ -5,31 +5,34 @@ name: "Git3"
|
|||
domain: internet-finance
|
||||
status: active
|
||||
founded: 2025
|
||||
headquarters: "Unknown"
|
||||
website: "https://git3.io"
|
||||
twitter: "https://x.com/TryGit3"
|
||||
telegram: "https://t.me/Git3io"
|
||||
key_people:
|
||||
- "Unknown"
|
||||
- "Git3 team"
|
||||
key_metrics:
|
||||
funding_target: "$100,000"
|
||||
total_committed: "$28,266"
|
||||
launch_status: "refunding"
|
||||
monthly_burn: "$8,000"
|
||||
runway_target: "12-13 months"
|
||||
launch_date: "2026-03-05"
|
||||
mvp_status: "live"
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
||||
# Git3
|
||||
|
||||
Git3 is infrastructure that brings Git repositories on-chain through the Irys blockchain, enabling code ownership, censorship resistance, and monetization through the x402 protocol. Each repository is stored as an NFT with complete Git history preserved on-chain.
|
||||
Git3 is infrastructure that brings Git repositories on-chain, enabling code ownership, censorship resistance, and monetization through the x402 protocol. Built on Irys blockchain, Git3 stores complete Git history as on-chain NFTs with permanent storage guarantees.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2026-03-05** — Launched futarchy-governed fundraise on Futardio targeting $100K for on-chain Git infrastructure
|
||||
- **2026-03-06** — Fundraise closed in refunding status with $28,266 committed (28.3% of target)
|
||||
- **2026-03-05** — Launched futarchy-governed fundraise on Futardio targeting $100K, raised $28,266 before entering refunding status
|
||||
- **2025-Q1** — MVP launched at git3.io with GitHub Actions integration, web3 wallet connection, and blockchain querying via @irys/query
|
||||
|
||||
## Relationship to KB
|
||||
|
||||
- [[futardio]] — fundraising platform
|
||||
- [[MetaDAO]] — futarchy governance infrastructure
|
||||
- Git3 represents application of futarchy-governed fundraising to developer infrastructure, testing whether on-chain code storage attracts capital through prediction markets
|
||||
- Git3 demonstrates code-as-asset tokenization with x402 payment rails for developer monetization
|
||||
- Vampire attack strategy: seamless GitHub integration without workflow disruption
|
||||
- Revenue model: creator fees on repository NFT sales, protocol fees on x402 transactions, agent royalties on code execution
|
||||
|
|
@ -12,7 +12,7 @@ event_type: launch
|
|||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Factual launch data for Git3 futarchy-governed fundraise. No novel claims about futarchy mechanisms — the failure case is documented but doesn't generate new theoretical insights beyond existing claims about futarchy adoption friction and brand separation. Entity data captures the launch event and outcome for reference."
|
||||
extraction_notes: "Factual launch data for Git3 futarchy-governed fundraise. No novel claims about futarchy mechanisms or internet finance dynamics — this is a straightforward failed fundraise with standard pitch deck content. Created entity pages for Git3 (company) and the fundraise decision market. The failure is notable as a data point (28.3% fill rate despite live MVP) but doesn't generate new theoretical claims about futarchy or capital formation mechanisms beyond what's already captured in existing KB claims about futarchy variance and market filtering."
|
||||
---
|
||||
|
||||
## Launch Details
|
||||
|
|
@ -275,10 +275,10 @@ Future revenue streams include enterprise licensing, premium features, and custo
|
|||
|
||||
|
||||
## Key Facts
|
||||
- Git3 fundraise launched 2026-03-05 targeting $100K
|
||||
- Fundraise closed 2026-03-06 with $28,266 committed (28.3% of target)
|
||||
- Git3 MVP live at https://git3.io
|
||||
- Monthly burn estimate: $8K ($5K team, $2K infrastructure, $1K marketing)
|
||||
- Revenue model: creator fees on NFT sales, protocol fees via x402, agent royalties
|
||||
- Technical stack: Irys blockchain storage, GitHub Actions integration, Thirdweb wallet
|
||||
- Roadmap: Phase 1 (MVP complete), Phase 2 (NFT marketplace + x402, Q2-Q3 2025), Phase 3 (token + ecosystem, Q4 2025)
|
||||
- Git3 launched futarchy-governed fundraise on Futardio 2026-03-05
|
||||
- Git3 raised $28,266 of $100,000 target (28.3% fill rate)
|
||||
- Git3 fundraise entered refunding status 2026-03-06
|
||||
- Git3 MVP live at git3.io with GitHub Actions integration
|
||||
- Git3 built on Irys blockchain for permanent storage
|
||||
- Git3 proposed 12-month runway with $8K monthly burn rate
|
||||
- Git3 revenue model: creator fees on NFT sales, protocol fees on x402 transactions, agent royalties
|
||||
|
|
|
|||
Loading…
Reference in a new issue