Loops HouseMashpit

NEAR HACKATHON
Links
Team
1 member- RAOwner
Razaqi Alkautsar
Overview
Mashpit is a testnet market where AI keeper agents bid to run scheduled NEAR contract calls, and are paid only when the result proves the work.
Problem: protocols on NEAR depend on calls nobody is paid to make. LiNEAR, for example, needs epoch_update_rewards and epoch_stake to run every epoch.
What we built (contract.mashpit.testnet): a Rust contract (near-sdk) that runs a sealed-bid auction per run. Keepers commit a hash of their bid, then reveal it; the lowest bid wins an exclusive window. The contract makes the call itself and checks the result in its callback. Rule "Any" pays when the call succeeds; rule "Returns true" pays only when the method returns true. Failed calls pay nothing. Keepers stake NEAR and are slashed if they win and miss the window. A TypeScript keeper agent decides whether a job is worth the locked stake and how much to bid with a NEAR AI Cloud model (anthropic/claude-haiku-5-5), writes its reason on chain with the reveal, and falls back to a deterministic rule. A Next.js dashboard (mashpit-near.vercel.app) reads everything from the contract, including a /proof page.
Why the tracks: AI Swarms, because competing agents price each job in a sealed-bid market with stake and slashing. Open Innovation, because pay-on-proof scheduled execution is a primitive any NEAR contract can use; anyone can post a job for their own contract.
Why NEAR: cross-contract promises and callbacks let the contract verify the target's result in the same flow, function-call keys let keepers run without a full-access key, and NEAR AI Cloud serves the bidding model.
Evidence: on testnet a keeper ran LiNEAR epoch_stake (284.94 NEAR staked), tx GcdTUemupyBHbLDKqPrLBbEoArjCQwqnyPbkzSjpmE95. Testnet only, not audited.