Loops HouseAirlock

NEAR HACKATHON
Team
1 member- NDOwner
N DIVIJ
Overview
In web3 your laptop is your wallet, and developers run strangers' code every week: take-home tasks, trading bots, packages an AI agent picked. One npm install can read your keys and send them away.
Airlock checks that code before it touches your machine:
-
Sandbox: it runs the repository's install and setup steps in a throwaway VM (Vercel Sandbox) whose home folder is full of decoy wallets and keys, with the internet cut to package registries. Every other host is answered from inside the VM, so whatever the code tries to send is kept. In our benchmark it caught all 4 wallet stealers red-handed, naming the exact wallets each took; the honest control touched nothing.
-
Private review: a model in a TEE on NEAR AI Cloud (Intel TDX and NVIDIA attestation with a fresh nonce, end-to-end encrypted, every reply signed) reads the code and the sandbox evidence and gives a verdict: Looks safe, Be careful, or Don't run it.
-
On NEAR: the airlock-verdicts.testnet contract stores a verdict only after it checks the enclave model's signature on chain. Anyone can verify a receipt offline with npm run verify:receipt, with no key and no network.
-
In coding agents: a Claude Code and Codex hook checks NEAR before a clone or install. Don't run it is blocked; anything unchecked waits for the human.
-
In the browser: sites can now hand tools to the browser's AI agent through WebMCP. The extension's agent guard checks every tool before the agent sees it: a tool that asks for a seed phrase or slips instructions to the agent is never offered, and one that moves money or signs waits for the person's click on every call.
Every verdict also gets a generative sigil drawn from its receipt hash.