Set the rule
Sponsor links the GitHub issue, sets the reward and writes acceptance criteria.
Sponsors fund GitHub issues upfront. Builders claim only paid bounties with clear rules. LockBounty keeps the money, the PR, and the review evidence together—then the payout is released only to the claim accepted by the sponsor.
No builder fee. No GitHub-comment claim. No payout without linked proof.
Issue #82 · Node · Hono · high-impact security fix
Sponsor payment is secured before builders claim. AI reports inform the decision; the sponsor remains accountable for acceptance.
€1,200 secured before the bounty opens
Up to three builders can compete with visible terms
PR, CI, scope and security evidence stay linked
Sponsor accepts one claim and triggers payout
A bounty cannot open to builders until sponsor payment is confirmed.
Each bounty supports up to three active LockBounty claims.
The selected claim carries a linked PR and review evidence.
LockBounty does not ask either side to trust a comment thread. The bounty moves only when the payment, claim, pull request and review state say it can.
Sponsor links the GitHub issue, sets the reward and writes acceptance criteria.
Payment confirmation unlocks the bounty for builders—never before.
Builders claim through LockBounty and submit one linked pull request.
Evidence and AI review make the sponsor decision auditable; acceptance releases payout.
Both sides see the same decision path. That is what removes the usual ambiguity around open-source bounties, agency work and AI-assisted delivery.
Turn an issue into a funded brief that makes the success condition, competition and final decision explicit.
Know the reward, sponsor reliability, claim capacity, AI policy and acceptance rule before committing your time.
Viktor and Kael attach advisory evidence to the claim: scope, risk, dependencies and execution signals. The sponsor or maintainer retains the final acceptance decision and the responsibility that comes with it.
Open AI gateroutekit/api · PR #418 · submitted through LockBounty
Does the diff solve the funded issue?
What needs sponsor or maintainer attention?
Are checks green and the production diff understood?
AI advises; the sponsor decides whether to accept.
The accepted LockBounty claim is the only payout path.
Builders do not pay to claim. Sponsors pay service and verification fees on top, before the bounty opens, so the workflow has a real payment and evidence trail behind it.
The displayed reward is the payout target for the sponsor-accepted LockBounty claim.
Funds claim tracking, sponsor reputation, dispute evidence and marketplace operations.
Funds scope, security, dependency and execution evidence reports.
Example total before payment-provider fees: 115 €
See the complete fee modelStart with a funded issue and a clear acceptance rule. LockBounty gives sponsors and builders one workflow they can both inspect.