---
type: claim
domain: internet-finance
description: "Git3 relies on Irys Chain's claimed 100K+ TPS throughput to store Git repositories, but performance at scale and cost scaling remain unproven"
confidence: experimental
source: "Git3 project description, futard.io launch 2026-01-01"
created: 2026-03-11
---

# Irys blockchain provides 100K+ TPS permanent storage for Git repositories

Git3 stores Git repositories permanently on Irys blockchain, which claims 100K+ transactions per second throughput. This performance level is critical for Git operations because:

**Git generates high transaction volume:** Each commit, branch, and file change creates blockchain transactions. A typical repository import involves hundreds to thousands of transactions. The MVP demonstrates this works for individual repositories, but no data is disclosed on transaction volume or costs at scale.

**Query performance matters:** Developers expect instant file browsing and commit history. Git3 uses @irys/query for direct blockchain querying with repository tagging for efficient data retrieval. The MVP includes a file explorer and commit browsing interface, suggesting query latency is acceptable for small repositories.

**Permanence is the value proposition:** Unlike Arweave or Filecoin (which provide storage but not Git logic), Irys combines permanent storage (data cannot be removed), cryptographic verification (integrity guarantees), high throughput (supports Git workflow speeds), and complete Git history preservation.

**Why this is experimental rather than proven:**

1. **No data on performance at scale** — The MVP is live but adoption metrics are not disclosed. No evidence that Irys maintains 100K+ TPS with thousands of repositories and millions of commits.

2. **Infrastructure costs suggest limited current usage** — Git3's burn estimate is $2K/month for infrastructure (Irys storage, cloud compute, node providers). This is extremely low for a blockchain-based Git service, suggesting either minimal usage or heavily subsidized costs. At scale, infrastructure costs would spike dramatically if Irys charges per transaction.

3. **Competing with GitHub's performance requires proving Irys can match centralized database speeds** — GitHub serves millions of repositories with sub-100ms latency. Blockchain queries are inherently slower than centralized databases. No evidence that Irys query performance is competitive.

4. **Cost scaling is the hidden risk** — If Irys charges per transaction and Git operations generate thousands of transactions per repository, the cost per repository could exceed GitHub's zero-price model. The source does not disclose Irys pricing or cost projections.

Git3's competitive edge depends entirely on Irys performance claims being accurate at scale. If throughput degrades, query latency increases, or costs spike with usage, the vampire attack strategy fails because developers won't tolerate slower or more expensive workflows than GitHub.

---

Relevant Notes:
- [[domains/internet-finance/_map]]

Topics:
- [[domains/internet-finance/_map]]
