Loops HouseAinek

NEAR HACKATHON
Team
1 member- DAOwner
Dastanbek Samatov
Overview
A TEE proves that the hardware is genuine. It does not tell you that the code reading your prompts has changed. On NEAR AI Cloud it did: one signing key, five builds of the proxy behind it, three weeks, by the attested record of the enclave that answered us. That is normal deployment, but a client that checks the key sees no change at all.
Ainek is Certificate Transparency for private AI. Verifiers you choose check the hardware evidence and record each key and deployment they see in an append-only, hash-chained log in a NEAR contract. If the one answering you is not there, your message never leaves the browser. Verifiers also trace the release behind the key to a source commit, and one switch makes the client refuse a release they have not recorded. Every attested answer comes with a proof: the enclave's signature and the hashes are re-checked in your browser, a salted hash can be committed on NEAR, and an auditor can check one answer without its text.
The same rule governs agents: the agent's key can propose a payment, not make one. A private policy (a whitelist, caps, a threshold above which a person decides) runs inside Intel TDX on OutLayer and signs its decision; the NEAR contract checks that signature, then pays, refuses or waits for the owner, and a stop button deletes the agent's key.
Reproduce from a clean clone: pnpm i && pnpm demo replays the checks offline with no API key; pnpm demo:controls makes 15 changes to recorded evidence and each is refused for its own reason; pnpm demo:log recomputes the log's hash chain from entry #0. Hosted: https://ainek.vercel.app.
Limits, stated in the README: testnet and not audited; the contract is locked, but its build cannot be repeated; two of the three verifiers are ours and the third is run by a friend; refusing a release is off by default; the deployment is attested, the model's weights are not verified.