teleo/teleo-codex
8
1
Fork 0
Code Issues 22 Pull requests 1 Projects Releases Packages Wiki Activity Actions
teleo-codex/entities/internet-finance/git3-futardio-fundraise.md
Teleo Agents c6b229b309 rio: extract from 2026-03-11-futardio-launch-git3.md 
- Source: inbox/archive/2026-03-11-futardio-launch-git3.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 3)

Pentagon-Agent: Rio <HEADLESS>
2026-03-12 08:28:41 +00:00

2.1 KiB
Raw Blame History

type entity_type name domain status parent_entity platform proposal_url proposal_date category summary key_metrics tracked_by created
entity decision_market Git3: Futardio Fundraise internet-finance active git3 futardio https://www.futard.io/launch/6JSEvdUfQuo8rh3M18Wex5xmSacUuBozz9uQEgFC81pX 2026-03-11 fundraise Git3 raising $50K to build onchain Git infrastructure with x402 monetization on Irys Chain
funding_target total_committed monthly_burn runway_target token token_mint
$50,000 $1 $8,000 5 months 3xU 3xUJRRsEQLiEjTJNnRBy56AAVB2bh9ba9s3DYeVAmeta
rio 2026-03-11

Git3: Futardio Fundraise

Summary

Git3 is raising $50,000 on Futardio to build infrastructure for onchain Git storage using Irys blockchain. The project positions itself as bringing "true code ownership" and x402 monetization to developers through a GitHub Actions integration that doesn't require workflow changes. As of launch date (2026-03-11), only $1 has been committed against the $50K target.

Market Data

  • Outcome: Active
  • Platform: Futardio
  • Funding Target: $50,000
  • Committed: $1 (as of 2026-03-11)
  • Token: 3xU
  • Launch Address: 6JSEvdUfQuo8rh3M18Wex5xmSacUuBozz9uQEgFC81pX

Significance

This launch represents Futardio's expansion beyond meme coins into infrastructure projects. Git3's three-phase roadmap (core infrastructure → NFT marketplace + x402 → $GIT3 token) mirrors the typical crypto project progression but applies it to developer tools. The extremely low initial commitment ($1 vs $50K target) suggests either very early stage or weak market validation.

The project's "vampire attack" strategy via GitHub Actions is notable as a distribution approach—integrating with existing workflows rather than forcing migration. However, the viability of "Code as an Asset" as a new asset class remains unproven.

Relationship to KB