74b204d830
- Source: inbox/archive/2026-03-05-futardio-launch-git3.md - Domain: internet-finance - Extracted by: headless extraction cron (worker 3) Pentagon-Agent: Rio <HEADLESS>
57 lines
3.2 KiB
Markdown
57 lines
3.2 KiB
Markdown
---
|
|
type: claim
|
|
domain: internet-finance
|
|
description: "Git3's go-to-market strategy uses GitHub Actions integration as a vampire attack to bring code on-chain without requiring developer workflow disruption"
|
|
confidence: experimental
|
|
source: "Git3 project description, Futardio launch 2026-03-05"
|
|
created: 2026-03-11
|
|
---
|
|
|
|
# Git3 positions GitHub Actions integration as vampire attack on centralized code hosting
|
|
|
|
Git3's go-to-market strategy explicitly frames itself as a "vampire attack" on GitHub, using seamless integration rather than platform displacement. The project implements a GitHub Action that automatically brings code on-chain while developers maintain existing workflows.
|
|
|
|
The strategy states: "Git3 doesn't compete with GitHub—it extends it. Instead of asking developers to switch tools, Git3 runs invisibly through a GitHub Action that brings code on-chain instantly and effortlessly."
|
|
|
|
This approach attempts to solve the adoption friction problem endemic to infrastructure projects by:
|
|
- **Eliminating workflow disruption**: Developers continue using GitHub as primary interface
|
|
- **One-click deployment**: GitHub Actions workflow handles on-chain deployment automatically
|
|
- **Opt-in benefits**: Blockchain permanence, ownership, and monetization added as optional features
|
|
- **Avoiding direct competition**: Extends GitHub's network rather than competing with it
|
|
|
|
The vampire attack framing is analogous to SushiSwap's strategy against Uniswap—extracting value from an incumbent's user base without requiring migration, using interface compatibility and additional incentives to drive adoption.
|
|
|
|
## Evidence
|
|
|
|
**Explicit Strategy Statement:**
|
|
- "The Vampire Attack Strategy: Git3 doesn't compete with GitHub—it extends it"
|
|
- "Instead of asking developers to switch tools, Git3 runs invisibly through a GitHub Action that brings code on-chain instantly and effortlessly"
|
|
|
|
**Technical Implementation (Phase 1, marked complete):**
|
|
- GitHub OAuth integration for repository access
|
|
- GitHub Actions integration for automated on-chain deployment
|
|
- Complete Git history import to Irys blockchain
|
|
- File explorer and commit browsing interface
|
|
|
|
**Go-To-Market Execution:**
|
|
- "One-click on-chain deployment through GitHub Actions workflow" listed as primary adoption channel
|
|
- GitHub Actions hosting and execution budgeted at ~$2,000/month in infrastructure costs
|
|
- "GitHub Actions Integration: One-click on-chain deployment through GitHub Actions workflow" as first developer adoption channel
|
|
|
|
## Challenges to Adoption
|
|
|
|
The strategy assumes developers value on-chain permanence and monetization enough to add a deployment step, even if "invisible." The failed fundraise ($28,266 of $100k target) suggests either:
|
|
- Market does not value the proposition sufficiently to fund development
|
|
- Vampire attack framing is marketing rhetoric without product-market fit evidence
|
|
- Execution risk perceived as too high for infrastructure play
|
|
- GitHub's network effects and switching costs are stronger than vampire attack strategy can overcome
|
|
|
|
---
|
|
|
|
Relevant Notes:
|
|
- [[git3-raised-28k-of-100k-target-through-futarchy-governed-fundraise-before-refunding]]
|
|
- [[internet-capital-markets-compress-fundraising-timelines]]
|
|
|
|
Topics:
|
|
- [[domains/internet-finance/_map]]
|
|
- [[foundations/cultural-dynamics/_map]]
|