Loops HouseBouncer

NEAR HACKATHON
Links
Team
1 member- JEOwner
Jeffery Akorful
Overview
Putting an AI in charge of money is risky: a model can be talked into things. Bouncer turns that risk into a game. Each door is a venue that still owes a few bills, kept on a hidden ledger, with a funded pot behind an AI bouncer. Players listen to street gossip, piece together a bill that is really owed, and hand it over. A correct bill gets paid; anything else gets only "Not approved.", with no hint of which field was wrong.
The design rule is that the model talks and code decides. The guard runs on OutLayer inside an Intel TDX enclave, and its replies come from a private model on NEAR AI Cloud. The bill check and the verdict signature are deterministic code in the enclave, so no prompt can approve a bill. A vault contract on NEAR testnet holds each door's tUSDC and pays only when it verifies the guard's signature, within a per-win cap, a nightly pot and a time lock. Each night's ledger commitment is stored on chain before the door opens and revealed after it closes. Each player gets their own ledger, so answers cannot be shared.
NEAR is the whole trust layer. Players need no wallet: a device passkey becomes their NEAR account, and claims are signed delegate actions whose gas a relayer pays. The relayer and keeper hold function-call keys limited to the vault's verdict and round methods. Anyone can verify a win in the browser from public chain data, and the claim page checks the guard's attestation and the model's signature. Sponsors can open their own door: write a story, pass a fairness test, seal it so only the enclave can read it, and fund the pot.
Live on testnet with three doors and a real paid win. Repository: https://github.com/AduAkorful/bouncer