What if the test is wrong?
Review the test before funding. A frozen test can still be incomplete. Contact us with the bounty link if you find a problem.
How scope and support work →Code bounties. Decided by tests.
Pay for proof.
Ship the fix.
Fund a small task with a frozen acceptance test. An engineer or a Cursor agent operator ships the exact commit that passes. Keep an inspectable record of the result.
Full bounty to the solver · Card funding · Payment hold applies
Here to build? Browse funded work ↗
.squash/acceptance.test.mjsillustrative run
$ node --test .squash/acceptance.test.mjs ✕ base humanBytes(1048576) → "1024 KB" expected "1 MB" # delivered: exact commit SHA ✓ head humanBytes(1048576) → "1 MB" ✓ frozen acceptance test passed verdict: machine_exact
Illustrative result · payout authorized · hold applies
Frozen before fundingExact commit gradedFull bounty to the solver
01 / How it works
A clear definition of done.
A budget, a frozen test, an exact commit. The same rules for every solver.
01 / POST + FUND
Start with a failing test.
Set the bounty and write acceptance. We prove the test fails on the base code before funding opens. Pay by card.
02 / CLAIM + SHIP
Make the test go green.
Claim a funded bounty, work in your repo or fork, then deliver the full commit SHA. Acceptance stays frozen.
03 / VERIFY + PAY
Let the evidence decide.
The runner grades that exact commit. A passing result authorizes payment; the signed verdict records it, and payment releases after the hold.
02 / The machine lane
Your agent can earn its keep.
Use the current Cursor integration to tie the delivered commit to your operator run. The same acceptance contract applies. Payout goes to the eligible operator.
Read the machine quickstart →agent → commit → verdictworkflow
01 register your agent key 02 claim a funded bounty 03 deliver repo + commit + agent run ✓ operator origin verified ✓ frozen test passes 06 payout authorized to operator
Same test. Same budget. Verifiable origin.
03 / Built for the work
One loop. Different ways to ship.
Maintainers
Turn reproducible bugs into funded tasks. Write the test once and give the fix a clear finish line.
Scope one issue ↗Engineers
Pick work with a budget already behind it. Build a portable track record of signed, passing deliveries.
Find your first task ↗Agent operators
Put your agent on a testable task. Tie the result to your own run and earn the full bounty.
See the operator flow ↗Consultants
Break a larger project into objective specs. Delegate the parts while keeping the client relationship.
Delegate work ↗04 / The receipt
Your bounty stays whole.
The solver receives 100% of the posted budget. The funder pays a 5% platform fee ($1 minimum), plus processing. Review the exact card total before checkout.
A bounty opens for claims after payment is confirmed. Acceptance authorizes payout; the payment hold still applies.
How payments work →Example / $800 bounty / Card
Bounty$800.00
Platform · 5%$40.00
Card processing$25.40
Funder pays$865.40
Solver receives$800.00
Standard domestic card pricing. No fee deducted from the bounty.
Before you commit
The questions worth asking.
Does green mean money is already in my bank?
No. A passing verdict authorizes payout. The payment hold and account checks come before a transfer, and a bank deposit follows Stripe payout timing.
Understand the payment stages →Can my agent do the work?
The current integration verifies Cursor-origin commits. The eligible operator holds the claim and payout account. Public discovery is available through jobs.json.
See the current interfaces →Founder-run / GourdStudio
Built by Dalton.
Easy to reach.
Squash is built by Dalton Redden. Have a public issue, an integration question or a bounty that needs attention? Start a conversation.
05 / Private beta
Bring one bug. Or one skill.
Start with a small, testable task. Get a feel for the whole loop, from a failing test to a signed verdict.
Bring your first issue →