Loops HousePA
PatchBond

Event
NEAR HACKATHON
Links
Team
1 member- OLOwner
Oluwagbemiga Gbangbola
Overview
THE PROBLEM AI made sending a pull request free, but a maintainer still pays in time to review it. Open-source repos are filling with AI slop: PRs that claim fixes they don't contain.
WHAT PATCHBOND DOES A stranger opening a PR pays a small refundable bond in USDC or NEAR.
- The price is set on-chain by the repo's open review queue, like EIP-1559's base fee, so a flood raises the flooder's own price.
- After CI, a verifiable model on NEAR AI Cloud judges the PR from facts we compute: CI result, code that doesn't exist, claims missing from the diff.
- The judge can also run in an OutLayer Intel TDX enclave called from our NEAR contract, which checks NEAR AI's signature on-chain before money moves.
WHERE THE MONEY GOES
- Real work gets every cent back.
- A forfeited bond pays 90% to the repo's vault and 10% to PatchBond.
- Slop that claimed to fix an issue funds a bounty for the real fix.
FAIR BY DESIGN
- The judge is cautious: doubtful cases go to the maintainer. On held-out sets it forfeited 0 of 95 good PRs (and 5 of 99 slop), so the bond and deadline are meant to do the filtering.
- Every verdict is public and checkable in the browser.
- Either side can stake to have a stronger model re-judge a verdict, and a maintainer's own forfeit gives the contributor 48 h to dispute it for free.
FOR AGENTS AND SECURITY
- Coding agents pay from capped budgets with NEAR function-call keys the contract enforces, via an MCP server, so an agent gets money without the keys.
- Security reports can be sealed in the browser and judged inside the enclave.
STATUS Live on NEAR testnet with a GitHub App. Invited outside testers have paid bonds, and one dispute on another maintainer's repo was settled by the enclave re-judge.
NEAR FEATURES NEAR AI Cloud verifiable inference, OutLayer, function-call keys, NEP-141 USDC, NEP-366 meta transactions, NEP-413, NEP-297.