--- type: claim domain: internet-finance description: "Git3 uses GitHub Actions to bring code on-chain without requiring developers to change tools or workflows" confidence: experimental source: "Git3 project description via Futardio launch, 2026-03-11" created: 2026-03-11 --- # Git3 demonstrates vampire attack strategy through GitHub Actions integration enabling blockchain benefits without workflow disruption Git3's core go-to-market strategy is a vampire attack on centralized code hosting that runs invisibly through GitHub Actions rather than forcing developers to migrate platforms. The integration allows developers to maintain existing workflows while gaining blockchain benefits (permanent storage, NFT ownership, monetization capabilities) automatically. This approach addresses the primary adoption barrier for blockchain-based developer tools: the switching cost of changing established workflows. By making the blockchain layer invisible and automatic, Git3 eliminates the need for developers to learn new tools or change their daily practices. The project explicitly frames this as "Git3 doesn't compete with GitHub—it extends it" and positions the GitHub Action as running "invisibly" and "effortlessly." This is structurally similar to vampire attacks in DeFi, where new protocols attract liquidity by offering superior economics without requiring users to abandon familiar interfaces. ## Evidence - Git3 GitHub Actions integration is listed as completed MVP deliverable (Phase 1, Q1 2025) - Project description states: "Instead of asking developers to switch tools, Git3 runs invisibly through a GitHub Action that brings code on-chain instantly and effortlessly" - MVP is live at https://git3.io with GitHub OAuth integration functional - Strategy explicitly frames positioning as extending rather than competing with GitHub - However: No adoption metrics provided. No evidence that developers have actually enabled the GitHub Action or that the "invisible" integration drives usage ## Challenges to the claim The vampire attack framing assumes developers will adopt blockchain features simply because they're frictionless. This remains unproven—developers may not value permanent on-chain storage, NFT ownership, or monetization enough to enable even a zero-friction integration. The analogy to DeFi vampire attacks (which succeeded by offering superior yield) breaks down if the blockchain benefits don't provide measurable value to developers. The MVP being "live" does not indicate product-market fit or meaningful adoption. --- Relevant Notes: - [[futarchy-governed-meme-coins-attract-speculative-capital-at-scale.md]] — Git3's failed fundraise suggests futarchy launches need more than mechanism credibility - [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale.md]] — Futardio context Topics: - internet-finance - developer-tools - blockchain-adoption