Claim work
Claim funded GitHub work only when reward, rules, and sponsor trust are visible.
Builders do not fund bounties. Before you spend time, LockBounty shows whether sponsor payment is secured, how many claim slots are open, what acceptance means, and how payout works. Only the claim accepted by the sponsor is paid.
Sponsor paid first
Visible
Stripe setup lets builders receive money; it never charges builders to claim work.
Sponsor trust
Checked
Reliability signals protect builders from unclear acceptance or unpaid work.
Three slots
Capped
A bounty can host up to three competing builders; only the sponsor-accepted claim is paid by default.
PR evidence
Scored
Each claim is designed to connect to a pull request, CI, review evidence, and audit scores.
Builder path
The claim flow is not hidden behind a decorative modal anymore.
Create the builder profile with email or GitHub.
Connect Stripe once to receive accepted payouts; this is not a payment to work.
Use the bounty discovery page to understand reward, risk, stack, policy, and available claim slots.
Submit the PR evidence so the audit agent can score security, code cleanliness, tests, maintainability, and performance.
Viktor and Kael may recommend a merge candidate, but the sponsor or maintainer keeps the final decision.
If another claim is accepted, non-selected builders are not compensated by LockBounty unless a separate agreement exists.