Loops HouseHorkos

NEAR HACKATHON
Team
1 member- SEOwner
SERHAT Özen
Overview
Horkos is an escrow contract on NEAR for purchases made by AI agents. We don't resolve disputes; we prevent them.
Problem: an agent's payment can't be reversed. If it overspends, follows a prompt injection, or pays for missing or garbage data, the money is gone. Buyer approval fails too: a buyer holding the data can claim it was bad.
How it works: the owner deposits a tUSDC budget and sets an on-chain mandate (total and per-order caps, allowed sellers, expiry). The agent signs with a function-call key that can only call create_order and cancel_order, and the contract rejects any order outside the mandate. Each order locks its price and is an NEP-171 NFT receipt. The seller uploads encrypted data and calls submit_delivery; the contract asks NEAR OutLayer to run our verifier (WASM pinned by sha256, version fixed per order) in its TEE. The verifier checks the data against the listing's JSON Schema and re-seals the key to the buyer. Valid: the seller is paid and the buyer gets the key in the same callback. Invalid or no result: the seller can resubmit; after the deadline anyone can call refund_expired.
On testnet (tx ids in the README): good deliveries settled through OutLayer; a bad delivery refunded; a prompt-injected 500 tUSDC order rejected on chain. An MCP server lets Claude buy within the mandate, a faucet gives 20 tUSDC, a hosted seller serves judges, and npm run sandbox runs all demos locally with no keys.
Status: live verification depends on OutLayer testnet. When it times out, the order refunds in full. Settled examples: orders 9, 15, 18 (txs in docs/testnet.md).
Seller A's price data comes from public APIs (CoinGecko, Coinbase); neither is a partner.
Site: https://horkos-escrow.netlify.app
Limits: testnet only; the contract trusts OutLayer's operator and does not verify the TEE attestation on chain; conditions are JSON Schema only; receipts are not transferable yet.