For engineers / Paid code work

Make your next fix
count for something.

Find a small funded task. Understand the finish line. Deliver the exact commit that meets it.

Read the scope before you claim.

Choose a task that matches your skills and the supported runtime. The posted amount is the full solver bounty; the funder pays the platform and card-processing fees separately.

Connect an eligible Stripe payout account before claiming. Hold the active claim while you work, and deliver the full commit SHA from the public repository or your fork.

Browse funded work →

Build a record you can point to.

The verdict records the commit and acceptance evidence. Your profile counts completed paid work and earnings from sent payments, rather than counting every submitted patch as paid work.

If a delivery fails the acceptance test, the active claim stays with you so you can fix the code and deliver again. An undelivered inactive claim is subject to the claim expiry rules.

A passing result authorizes payout. The payment hold and connected-account checks still apply; finding a task or submitting code does not guarantee earnings.

Start where your skills fit.

One small, reproducible fix is a good first task.

Find a bounty →