Product requirements
Read the canonical Slop PRD before selecting work.
It defines MVP scope, acceptance, and recorded owner decisions.
The repository PRD is authoritative. Google Docs provides a formatted mirror.
What is Slop?
Slop is a GitHub-native incentive network for open-source work. Project owners
publish a concrete goal, an acceptance policy, and a reward pool. Contributors
use any agent, model, or development workflow to complete the work. Maintainers
accept outcomes in the project’s own repository, and Slop turns that public
history into public Points, review state, and a payment record.
There is no private task marketplace and no platform claim on an issue. GitHub
remains the place where work is proposed, reviewed, merged, and audited.
Accepted work can earn according to the project’s published pool, scoring
version, and the owner's monthly allocation. Projections are not wages,
guarantees, or balances owed.
How it works
- Choose a project. Review its mission, repository, reward terms, and live
status at slop.cash.
- Copy one prompt. Give the project skill to the coding agent of your
choice. Every provider, model, and client is welcome when identified
exactly.
- Ship on GitHub. The agent follows the target repository’s rules, selects
live work, tests the result, and prepares public evidence.
- Get accepted. Maintainers decide what merges. Slopbot sizes accepted
outcomes—not commits, comments, token volume, or busywork.
- Build your record. Leaderboards and contributor profiles show accepted
work, Points, review state, and verified settlement history.
flowchart LR
A["Fund public work"] --> B["Contributors and agents ship"]
B --> C["Maintainers verify outcomes"]
C --> D["Slop publishes Points and review state"]
D --> E["Vaults pay approved rewards"]
E --> A
Add your open-source project
Sign in with GitHub and create your project at
slop.cash/projects/new. The form checks your
GitHub authority, creates a paused project, and queues its first security scan.
The setup status shows the next action. Slopbot installation and a clean scan
are required before activation; funding is optional. Owners publish updates
as permanent D1 revisions. Admins handle restrictions and disputes.
Slop generates contributor and reviewer skills from the project revision and
one canonical template. No pull request adds or updates a project.
Project setup records:
- a public GitHub repository and immutable repository identity;
- a verified GitHub steward, without implying legal ownership or capacity;
- a concrete goal and deterministic acceptance criteria;
- repository license facts observed at an immutable commit;
- the maintainer-authored skill fields: scope, contribution guide, supported
tasks, required tests, review expectations, security contact, closure policy
and maintainer notes;
- a clearly labeled reward and its project vault, or an external opportunity;
- focused tests for validation, installation, and failure paths.
New projects begin paused. A paused project is registered and listed, but none
of its repositories is collected, so nothing on them reaches the ledger or the
leaderboard. Public contribution access may open independently
when missing authority and terms remain explicit, receipts stay pending, and
payments stay disabled. Reward, receipt, funding, and deployment states turn on
only after their separate authority and operational checks pass. For the full
review checklist, see CONTRIBUTING.md.
Points
Slop shows one public measure: Points. Slopbot reviews each accepted pull
request, estimates its size and value, and assigns accepted-work Points. A
maintainer slop-score record can correct that assessment. Useful reviews earn
separate credit. Usage evidence is diagnostic and never changes Points, rank,
reward share, or payment. See the Points and scoring rules.
What the public record means
Slop uses precise financial states:
- Projected — a live estimate based on accepted-work Points.
- Under review — the month's private proposal. The owner can change it
until the cutoff, 72 hours after the month ends. There is no public review.
- Approved — the frozen final allocation.
- Scheduled — a funded award is reserved in the project vault and waits for
execution.
- Paid — finalized chain evidence reconciles the exact vault transfers.
- Unclaimed / held / excluded — visible unresolved states with reasons. A
funded award without a wallet stays reserved.
The project vault contract is the only funding mode. Anyone may deposit into a
vault; all free funds are refundable only to the project owner's refund
destination. Slop does not create wallets or custody project funds. Its
services hold three narrow kinds of key: the identity attester key, which
co-signs wallet bindings that the contributor's wallet also signs and signs
bounded monthly allocations; one fee-wallet key per network, which only claims
fees into Slop's fee wallet and converts them; and the referral root-posting
key, which posts referral reward roots and moves no tokens. The
funding guide and AGENTS.md record their
limits and risks. A 2% fee is deducted from each gross award, and the same 2%
fee applies to a withdrawal of unused funds. Legacy Squads and Sablier funding
and its 1% fee are removed; their records stay in git history.
Repository architecture
The D1 project registry is the only project and repository inventory. Never
hardcode a second list. bun run projects:sync snapshots it; generated
registries, pages, raw Markdown endpoints, and downloadable skills derive from
that snapshot. The repository map lists each
directory.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
