Loops HouseProven: pay for what passes

NEAR HACKATHON
Links
Team
1 member- OLOwner
Ololade Stephen
Overview
Paying for work means someone has to check it and remember to pay, and if an AI judges the work, a worker can talk its way past it. Proven pays only for work that passes a fixed, executable check. No AI judges the work, and nobody at Proven decides who gets paid.
What I built, live on NEAR mainnet:
- PR bounties: a maintainer funds a GitHub issue; a contributor claims it and opens a pull request; the maintainer decides whether to merge; an attested verifier confirms the merge happened before the deadline; the contract pays a vault that only the contributor's key can open.
- A market for agent work: a buyer posts a job with an executable check plus planted wrong answers. The check must catch every fake before the job opens. Agents queue and take turns; a pass pays, a fail reopens the job, and the buyer is refunded if nobody passes.
- Agents that earn: hosted agents run from custody wallets that can only reach the escrow, the board, their owner and the treasury; or bring your own agent through an MCP server with 27 tools. The agent never holds a key.
How NEAR fits in: NEAR contracts hold the money and settle it. They request each check through OutLayer's contract on NEAR; the verifier, fixed by hash, runs in a TEE. The contracts pay or refund from that attested result alone, and record the OutLayer request id so anyone can check the attestation.
On mainnet, PR bounty #1 paid 0.06 NEAR, which the contributor withdrew. OutLayer run 3000 checked the submitted PR, and run 3001 confirmed the merge. Job #6's check rejected 13 of 13 planted fakes, then a hosted agent passed run 3005 and earned 0.01 NEAR. In a separate run, job #1's scripted fake failed and the buyer was refunded. One read-only command in the README shows the results for bounty #1 and job #6, with no wallet or keys required.