Incentivize open source contributions.
Gittensor is a Bittensor subnet (SN74) that accelerates open source software development by rewarding meaningful contributions. Miners earn TAO by making real, merged pull requests to recognized open source repositories.
Miners register with a fine-grained GitHub personal access token (PAT) and contribute to whitelisted open source repositories. When their pull requests get merged, validators authenticate account ownership via the PAT, verify the merged contributions, and score them based on code quality, repository allocation, and programming language factors. Rewards are distributed within each repository's configured emission share.
Open source powers the modern world, yet most contributors work for free. Gittensor solves this by creating a decentralized marketplace where:
- Real work gets rewarded — Only merged PRs to legitimate repositories earn emissions
- Quality over quantity — Semantic code analysis evaluates actual contribution value
- Sybil-resistant — GitHub account verification and merge requirements prevent gaming
The result: a sustainable incentive layer that channels resources toward building and maintaining the software we all depend on.
No miner neuron required — just register your GitHub PAT with validators using the CLI.
# Install
git clone https://github.com/entrius/gittensor.git
cd gittensor
uv sync
# Set your GitHub PAT
export GITTENSOR_MINER_PAT=ghp_your_token_here
# Broadcast PAT to validators
gitt miner post --wallet <name> --hotkey <hotkey>
# Check which validators have your PAT stored
gitt miner check --wallet <name> --hotkey <hotkey>See full guide here
Gittensor also pays GPU time. A compute miner runs one command on a GPU box; the agent it starts is the whole miner, and the subnet's controller checks the cards, leases them out and pays per card.
# Needs Docker with the NVIDIA runtime and a registered hotkey
gitt up --wallet <name> --hotkey <hotkey>
# Leave cleanly: drain and stop the workloads placed here, then the agent and its runner
gitt downgitt up --help lists every option.
Recommended: Deploy with Docker and Docker Watchtower for automatic updates
# Quick start
git clone https://github.com/entrius/gittensor.git
cd gittensor
cp .env.example .env
# Edit .env with proper values
nano .env
docker-compose -f docker-compose.vali.yml up -dSee full guide here
- Master Repositories & Emission Shares
A list of repositories pulled from GitHub that have been deemed valid for scoring. They each have a configured emission share that bounds how much of the scoring pool the repository can receive in a round.
NOTE: this list will be dynamic. It will see various audits, additions, deletions, emission-share changes, and shuffles as the subnet matures.
NOTE: don’t be afraid to provide recommendations for your favorite open source repositories and the team will review it as a possible addition. A repo is more likely to be included if: they provide contributing guidelines, are active/community driven, provide value/have users
- Programming Language Weights
A list of major file types/extensions, mostly related to programming languages, but also plenty of markdown, documentation, and other common files are included. Each extension has a weight for scoring. If the extension has a language full name then code in those languages will be evaluated using token-based scoring.
NOTE: this list will also be dynamic. Additions, and weight changes will occur as the subnet matures.
- Token Weights
Weights assigned to AST (Abstract Syntax Tree) node types for token-based scoring, including structural elements (functions, classes) and leaf tokens (identifiers, literals), enabling semantic evaluation of code changes.
See full guide here
MIT - See LICENSE for details.