Skip to content
Contribute & earn

Get paid for the code the network doesn't have yet.

The mesh gets more valuable with every new, verified solution in it. Rewards go to original work — code that isn't already in the mesh and isn't already public on GitHub — so your private, hard-won solutions earn, while re-uploads and public copies don't. We run the tests to prove it works, then reward it. Free to use, today and at launch.

Get started freeConnect your agent

We never reveal your entire codebase

Contribution is strictly opt-in, and the privacy bar is the whole point of PatchMesh.

What we do

  • • Scan locally — your folders and, with your token, your private GitHub repos.
  • • Share only small capsules you approve — the function, its tests, metadata.
  • • Keep your GitHub token on your machine — it never reaches PatchMesh.
  • • Exclude secrets and anything in .patchmeshignore before anything leaves.
  • • Ask before looking at anything, and confirm every contribution.

What we never do

  • • Never upload or expose your entire codebase — not now, not ever.
  • • Never publish anything automatically or without your confirmation.
  • • Never share secrets, credentials or ignored paths.
  • • Never use your private code to train models.

The first time you run the contributor agent it asks before looking at anything — it stays off until you say yes, and you can revoke any time.

How to start contributing

A tiny npx agent runs locally. On first login it asks the one privacy question, then you pick what to share — from your machine or a private GitHub repo.

# 1. Log in — first run asks: scan local folders and/or private GitHub repos?
npx @patchmesh/agent login --api-key pmk_your_key_here

# 2. Contribute from your machine (scan, pick, earn points)
npx @patchmesh/agent contribute

# 3. Or contribute from a private GitHub repo (token stays local)
npx @patchmesh/agent github scan --repo you/your-repo

Live The agent is published on npm — run it with no install. Create an account to get your key and start earning points.

What actually gets shared: a capsule

Not your repo — a single, self-contained, verified unit. The same structure the rest of the network uses.

anatomy of a capsulecontent-addressed · signed provenance · trust-rated

Identity

  • Canonical task
    The normalised problem the capsule solves.
  • Language & runtime
    Where it applies — versions and ecosystem.
  • Dependencies
    What it needs to compile and run.

Code

  • Reusable artifacts
    The implementation, ready to adapt.
  • Tests
    Executable proof of behaviour.
  • Content hashes
    Content-addressed so reuse is verifiable.

Evidence

  • Validation results
    Did the tests actually pass?
  • Security scan
    Known-issue check before reuse.
  • Reuse outcomes
    How it performed for others — ranking signal.

Trust

  • Licence (SPDX)
    Clear, preserved licensing.
  • Provenance
    Where it came from, pinned to a commit.
  • Trust level
    Verified, approved, or unverified candidate.

A snippet search returns text. A capsule returns a decision: reuse this, adapt that, or generate because nothing here fits.

How points are earned

Every contribution is scored automatically on objective signals — no popularity contest. First we check it's novel (not already in the mesh, not already public on GitHub); then we run its tests in an isolated sandbox and weigh quality, security and licence. Novel, proven code scores high and earns points; a re-upload, a public copy, or a high-severity security finding earns nothing.

Novel — not already known

30 pts

The network doesn't already have this, and it isn't a copy of public GitHub code. Re-uploads and public copies earn nothing.

Tests present & passing

20 pts

We run the tests in an isolated sandbox — executable proof it works, not just that tests exist.

Code quality

15 pts

Structure, documentation and readability of the unit.

Security clean

15 pts

Secret & dependency scans clear. High-severity findings block approval outright.

Licence clarity

10 pts

A clear, reusable licence (MIT, Apache-2.0, BSD…).

Validation passed

5 pts

The capsule's sandbox validation run succeeded.

Proven reuse

5 pts

It actually helped on real reuse outcomes.

Contributor tiers

Newcomer
0+ lifetime pts
Contributor
50+ lifetime pts
Builder
400+ lifetime pts
Core
1,500+ lifetime pts
Luminary
5,000+ lifetime pts

Where this is heading: a token on Solana

Once the network is deep and high-quality, the roadmap envisages a token on Solana that points may convert into — usable to pay for the system (which is free to use to begin with). To be completely clear about today:

Roadmap · plannedNo token exists yetTarget network: Solana
  1. 1Now

    Earn points

    Contribute verified solutions and earn points from automated quality scoring. Free to use.

  2. 2Next

    Grow the network

    Build a deep, high-quality verified mesh across the community.

  3. 3Planned

    Token on Solana

    Subject to legal review, launch a token; points may convert into it to pay for usage.

Important: Points are a loyalty balance with no monetary value today. A token on Solana is planned but does not exist yet; conversion terms are not set. This is not an offer, solicitation, or guarantee of any asset or future value, and any launch is subject to legal review and may change.

Start contributing. Start earning.

Free to use. Private by default. You approve every contribution.

Get started freeRead the docs