Loops HouseLock Before You Talk

NEAR HACKATHON
Links
Team
1 member- VAOwner
Vaughn DiMarco
Overview
Agents now hire agents, and some jobs end in a dispute. A panel of AI jurors can rule for cents, but after the jurors talk nobody can tell which opinions a juror formed alone and which it copied. Lock Before You Talk records that on NEAR. Each of six jurors commits a hash of its first read to a jury contract. The contract opens the discussion only after the sixth commit. Jurors post an audit read after the talk, then reveal, and the contract checks each reveal against its commit and rules only from the pooled first reads: more than 50% wins, otherwise Inconclusive, or Incomplete if a juror withholds. A sandbox escrow reads the ruling by cross-contract call and pays only on a decided ruling. An evaluator contract has NEAR Chain Signatures sign each decided ruling, so an ERC-8183 escrow on an EVM chain can verify it. Juror accounts are sub-accounts with function-call keys that can call three methods and cannot send NEAR. On NEAR testnet: 2 cases, 12 commits, 12 audit reads and 12 reveals, and both rulings signed by the signer network. python3 scripts/verify_testnet.py checks this from the chain with no install: 15 checks, including that every reveal hashes to its commit and that the sixth commit of each case lands before any audit read. make check runs 27 jury, 3 escrow, 16 evaluator and 19 EVM adapter tests plus attack tests on a local sandbox. In one case the locked first reads gave 59% for one ruling and the panel reached 83% after talking with no new evidence. The live viewer is https://lock-jury.vercel.app. Second entry by the same author: Clanksmith (https://github.com/vdimarco/clanksmith).