teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 35 Projects Releases Packages Wiki Activity Actions 912
teleo-codex/domains/internet-finance/git3-vampire-attack-uses-github-actions-to-capture-developer-workflow-without-platform-migration.md
Teleo Agents 1e83c62129 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 07:28:21 +00:00

3.4 KiB
Raw Blame History

type domain description confidence source created
claim internet-finance Git3's GitHub Actions integration enables blockchain benefits without forcing developers to abandon existing tools, reducing adoption friction compared to platform replacement strategies speculative Git3 project description, futard.io launch 2026-03-11 2026-03-11

Git3 uses GitHub Actions integration as vampire attack to add blockchain benefits without platform migration friction

Git3's go-to-market strategy runs blockchain integration invisibly through GitHub Actions rather than competing directly with GitHub as a platform. Developers maintain their existing GitHub workflows while a background action automatically brings code on-chain, eliminating the adoption friction that killed previous decentralized code hosting attempts (Gitcoin, Radicle, etc.).

This vampire attack architecture exploits GitHub's extensibility to add blockchain benefits (permanent storage, cryptographic verification, monetization rails) without requiring developers to learn new tools, migrate repositories, or change collaboration patterns. The strategy acknowledges that developer workflow inertia is the primary barrier to adoption, not lack of blockchain features.

The approach mirrors successful platform extensions rather than platform replacements: MetaMask didn't replace browsers, it extended them. Git3 doesn't replace GitHub, it extends it with ownership and monetization layers. The MVP implements this through GitHub OAuth integration for seamless repository access and automated on-chain deployment via Actions.

Evidence

  • GitHub Actions integration enables automated on-chain deployment without workflow changes (Phase 1 complete, MVP live)
  • Developers continue using GitHub interface while Git3 runs in background (stated strategy: "runs invisibly through a GitHub Action")
  • No repository migration required — existing repos can be brought on-chain via action (Phase 1 deliverable: "GitHub Actions integration for automated on-chain deployment")
  • Strategy explicitly framed as "vampire attack" that extends rather than replaces GitHub (stated in project description)
  • MVP includes GitHub OAuth integration for seamless repository access (Phase 1 complete)
  • File explorer and commit browsing maintain familiar Git interface patterns (Phase 1 deliverable)
  • Project acknowledges developer workflow inertia as primary barrier: "Instead of asking developers to switch tools, Git3 runs invisibly"

Unproven Assumptions

  1. Blockchain benefits justify added complexity — Assumes developers value permanence, ownership, and revenue enough to accept on-chain storage costs and potential GitHub Actions latency/failures. No user research provided.

  2. GitHub Actions reliability — Strategy depends on Actions remaining reliable and performant at scale. Failures in background automation could damage developer trust.

  3. GitHub platform tolerance — GitHub could view this as competitive threat and block or rate-limit the integration. No contractual protection mentioned.

  4. Cost-benefit clarity — Developers must understand why on-chain storage costs are worth paying versus GitHub's free tier. Value proposition remains unclear for most use cases.

Relevant Notes:

Topics: