Gittensor
SN74AI agents that write software autonomously through decentralised code generation
Gittensor is one of the cleaner ideas on Bittensor: reward merged open source work, not vibes about autonomous coding.
// Merged PRs become subnet signal.
Gittensor tackles a specific problem inside the Bittensor ecosystem: Open source runs the internet, but a lot of real maintenance and feature work still goes unpaid or underpaid. Official sources describe it as a subnet where miners contribute to whitelisted open source repositories and submit proof through their GitHub identity, while validators verify merged pull requests, confirm account ownership, and score contributions by quality, repository weight, and language factors.
The simple version: It is like turning open source contribution history into a live rewards market.
Centralized equivalent: Think GitHub Sponsors crossed with a code quality scoreboard, but decentralized.
How it works:
- Miners do contribute to whitelisted open source repositories and submit proof through their GitHub identity
- Validators check verify merged pull requests, confirm account ownership, and score contributions by quality, repository weight, and language factors
- The problem it solves: Open source runs the internet, but a lot of real maintenance and feature work still goes unpaid or underpaid.
- The opportunity: If incentives line up with merged work instead of vague promises, subnet rewards can flow toward software that already matters in production.
- The Bittensor advantage: Bittensor lets the reward market stay open and competitive. Anyone who can ship useful code can try to earn, without waiting for a platform grant committee.
- Traction signals: Gittensor has a live docs stack, active repo, and strong recent development velocity. The subnet sits near 0.00821, with a market cap around 33,698 TAO, pool depth near 8,898 TAO, and 269 commits from 39 contributors in the latest GitHub snapshot.
Category: Code Generation and Development Tools | Centralized Competitor: GitHub Sponsors, bounty platforms, Sourcegraph
There is no shortage of chatter about autonomous software development. Gittensor takes the less theatrical route and anchors incentives to merged pull requests in recognized repositories. That is a much better starting point than hand-wavy benchmark claims.
Mechanism:
The official README says miners contribute to whitelisted repositories using a fine-grained GitHub personal access token. Validators authenticate account ownership, verify merged pull requests, then score the work based on code quality, repository weight, and programming language factors. In other words, the subnet tries to pay for accepted contribution, not just generated code.
TAO.app and Supabase snapshot data show current pricing and demand conditions, but the mechanism and product-status claims above were kept anchored to official repos, docs, and websites. On the market side, Gittensor trades around 0.00821 TAO with roughly 33,698 TAO in market cap and about 8,898 TAO in pool depth. Seven day net flow sits near 1,139 TAO, which suggests recent demand has been constructive.
- Execution: Merged pull requests are a strong anchor, but contribution scoring can still be gamed around easier repos or lower impact tasks.
- Competition: The repo whitelist and scoring weights matter a lot. If the curation quality slips, the subnet risks rewarding activity that looks busy without being important.
- Market: Net flow over 7 days is positive, but sustained demand depends on whether the subnet becomes a real distribution channel for open source work, not just a neat idea.
