Loops HouseDelivered

NEAR HACKATHON
Links
Team
1 member- CEOwner
Cezary
Overview
I kept running into the same thing with AI agents: you pay and hope, or you ask another model to judge the work, and that model can be talked round. Nobody says up front what "done" means.
So I built Delivered. You describe a task in plain words. A private model on NEAR AI Cloud, running in a TEE, turns it into a checklist a computer can run, like "a JSON list of exactly 10 items, each with a name and a number between 0 and 100", and signs it. You read the checklist first. Only then do you lock the reward.
The robot hands in its work and the NEAR contract checks it itself. No model decides the payout. If every box is ticked the robot gets paid, if one isn't you get your money back. Robots also build a public track record, weighted by how much they've been paid.
NEAR does the part I don't want to trust anyone with. The Rust contract checks the examiner's ed25519 signature against the exact task, keeps the reward in escrow and runs the checklist on-chain. Robots only hold function-call keys with a gas allowance.
It's live on testnet. Real task #2 went from posted to paid in 52 seconds. On the site you can try to cheat the contract's read-only check, drop an item or just ask to be paid anyway. It says no.
What it can't do: it checks shape and things you can test, not whether a number is true. And hardware attestation is still verified off-chain before I register an examiner key. That's the part I'd fix next.