⏸Cherry Graffiti
|
AgentsAppsAutomationBitPensionBlogBoardroomBondsBuildButtonsCareersCashboardClientsComponentsContactContentContractsCoursesCreativeDevelopersDividendsDocsExchangeFoundersGigsKintsugiLibraryMarketMetanetMintMoneyButtonMusicPackagesPipelinePortfolioPricingProjectsRewardsRoadmapSchematicsServicesSkillsSmart ContractsStudioTaaSTokensToolsTreasuryVideoWebsitesWorkAgentsAppsAutomationBitPensionBlogBoardroomBondsBuildButtonsCareersCashboardClientsComponentsContactContentContractsCoursesCreativeDevelopersDividendsDocsExchangeFoundersGigsKintsugiLibraryMarketMetanetMintMoneyButtonMusicPackagesPipelinePortfolioPricingProjectsRewardsRoadmapSchematicsServicesSkillsSmart ContractsStudioTaaSTokensToolsTreasuryVideoWebsitesWork
Back to Blog
Featured

Repo-DEX: The Exchange for Code

Richard Boase
|
6 min read
|18 February 2026|
TOKEN: repo-dex-exchange-for-code
.MD Source
repo-dexbitgittokenizationbsvgithub$401$402

GitHub has 200 million repositories. None of them have a price.

You can star a project. You can fork it. You can sponsor the developer. But you can't hold a position in the code itself. There's no market for software at the repository level.

repo-dex.com is that market.

What Repo-DEX Does

Repo-DEX is an exchange where GitHub repositories become tradeable tokens. You connect your GitHub account, select a repository, choose a ticker symbol, and deploy a BSV-21 token. The whole process takes under a minute.

Once deployed, your repository token exists on the Bitcoin blockchain. You set the supply. You choose the pricing curve. You decide how dividends split. Anyone can buy a position in your code — on your terms.

No grant applications. No sponsorship tiers. No VC pitch deck. Just code that people can invest in directly.

How It Works

Step 1 — Connect GitHub. OAuth login verifies your identity. Repo-DEX checks which repositories you own or have push access to. Your GitHub account becomes a $401 identity strand on BSV.

Step 2 — Configure your token. Pick a ticker, choose your supply, and deploy on an ascending bonding curve where each subsequent token costs more — early supporters get more tokens per dollar. Dividends go 100% to stakers. Your code, your terms.

Step 3 — Deploy. One click. A BSV-21 token is minted with your repository metadata — name, description, owner, license, and the $401 identity link proving you control the repo.

Step 4 — Earn. Your repository token is live. Anyone can take a position in your code. Revenue splits according to the ratio you set at deploy.

What's Live Right Now

Repo-DEX launched with 13 tokenized repositories, including $BITGIT — the first repository token ever deployed on BSV. Token ID: 095040e7cad1037240ec4a84abba93abca4586acb5fc70a1d81cd37d97b7e001_0.

The explore page shows every tokenized repository on the network. Each listing shows the token symbol, current supply, verification level, and a direct link to the GitHub source. Everything is transparent. The code is public. The token is public. The verification is public.

The dashboard gives token owners a real-time view of their holdings — press count, revenue earned, token distribution. Developers can see exactly how their code is performing as an asset.

The Verification Stack

Not all repository tokens are equal. Repo-DEX uses a three-tier verification system:

Verified Owner — The strongest level. GitHub's API confirms the user has push or admin access to the repository. This is what you get when you connect via OAuth and select a repo you control.

Repo Attested — Medium strength. The repository includes a .well-known/token.json manifest declaring the token's parameters. Anyone can verify by reading the repo.

Unverified — The token exists but hasn't been linked to a verified GitHub account. Buyer beware.

Every verification feeds into $401 — the identity protocol. A developer who tokenizes a repo via Repo-DEX automatically gets a $401 identity strand. Link more providers (Twitter, LinkedIn, Google) and your identity strength increases. Four strands = verified status.

The Economics

The developer controls the economics. When you configure your token, you choose:

  • Ascending bonding curve — each token is individually priced; price(n) = c * n. Early supporters get more tokens per dollar. 1% of supply costs $1,000.
  • Dividends — 100% to stakers. Stake your tokens and earn from every buyer who comes after you.
  • Supply — how many tokens exist. Buyer sends any amount, gets tokens at current queue position.

The economics reward conviction. Early supporters who stake earn the most. The bonding curve handles price discovery automatically.

What makes repository tokens different from other tokens is what backs them. A repository token isn't backed by hype. It's backed by commits. Every push to the repository is inscribed on-chain. Investors can verify the project is alive before they take a position. Active development is visible. Abandoned projects are visible too.

Commit Chain

Every push to a tokenized repository triggers a webhook. Repo-DEX catches the event, verifies the HMAC signature, and inscribes each commit on BSV.

Each inscription references the previous one — forming a linked chain. A repository with 500 commits has 500 on-chain proofs, each pointing to the last. Walk the chain backwards from the latest inscription and you've got the entire development history, timestamped and signed.

This means repository tokens aren't static. They're living assets that grow with every commit. Active development is visible on-chain. Investors can see whether a project is being maintained before they take a position.

The Upstream Covenant

Repo-DEX supports an optional upstream_covenant in the token manifest. This declares that a percentage of revenue flows to dependencies.

If your project depends on a library, and that library has its own repository token, your token can route revenue upstream. The dependency graph becomes a revenue graph.

This isn't enforced on-chain yet — it's a social contract in machine-readable format. When $403 conditions come online, these covenants become programmable and enforceable.

Who This Is For

Developers who want their code to have a financial layer. You write code. People invest in it. You get paid. No middleman, no application process, no minimum follower count.

Investors who want exposure to software projects at the source code level. You can verify the developer's identity, inspect the commit chain, and watch development velocity in real-time. Your position in the token appreciates as demand grows.

Open-source maintainers who are tired of "please sponsor me" being the only funding model. Repository tokenization means your users can hold a position in your project. They benefit when you succeed. Incentives align.

Get Started

repo-dex.com — Connect your GitHub. Tokenize a repository. Start earning.

Your code has a market now. Use it.

For AI Readers

Intent: Announce Repo-DEX as a live exchange for repository tokens, explaining the product, economics, and verification system.

Core Thesis: Repo-DEX creates a market for source code by turning GitHub repositories into tradeable BSV-21 tokens with verified identity and on-chain commit chains.

Key Takeaways:

  • Repo-DEX is live at repo-dex.com with tokenized repositories including $BITGIT
  • Developer controls all economics: supply, bonding curve parameters
  • Ascending bonding curve: price(n) = c * n — early supporters get more tokens per dollar, 1% of supply costs $1,000
  • Three-tier verification: verified_owner (OAuth), repo_attested (token.json), unverified
  • Every commit inscribed on BSV, forming a linked chain of on-chain development proofs
  • $401 identity integration — GitHub OAuth creates a cryptographic identity strand
  • Upstream covenant allows dependency-graph revenue sharing (designed, $403 enforcement pending)
  • URL: repo-dex.com | Protocol: path402.com | Identity: path401.com

b0ase / 2026

More Articles
Get in Touch