Loops HouseTEE Receipts

NEAR HACKATHON
Links
Team
1 member- CHOwner
chamdom
Overview
TEE Receipts: private AI answers you can prove later.
Problem: NEAR AI Cloud runs inference inside a TEE and signs each reply, but the signature is only fetchable for a while, and the enclave signing key rotates. An old reply can't be matched to an attested key anymore, and an auditor can't check which TEE answered without trusting you.
What it does: the client asks NEAR AI Cloud, checks a fresh attestation with its own nonce (Intel TDX quote, TCB, report data, NVIDIA GPU via NRAS), then registers the attested signing key in our Rust contract on NEAR testnet together with the attestation-report hash. It anchors a content-free receipt (model, request hash, response hash, signer, attestation hash). The contract runs env::ecrecover on the TEE signature and rejects unknown or expired signers. The prompt and reply never go on-chain; the user keeps them in a local bundle.
Anyone with the bundle can verify it in a static browser page (no backend, no key): it re-hashes the bytes, recovers the signer with ecrecover, and calls the contract views (verify_receipt, check_response_signature, signer history). Flip one byte of the reply and it turns NOT VERIFIED. Every signer registration stays on-chain, so receipts keep verifying after the key rotates or expires.
NEAR features: NEAR AI Cloud private inference + TEE attestation, own Rust contract (tee-receipts-chamdom.testnet) with on-chain ecrecover and signer history, testnet receipts.
Tracks: privacy, open.
Independence: the same author also submitted agent-pay (github.com/tmdry4530/agent-pay-public, tracks security + agents). The projects share no code and solve different problems; no money moves here.